DecentralChain (DCC) icon

DecentralChain (DCC)

Create, sign and broadcast DecentralChain transactions, plus query blockchain data

Actions25

Overview

This node interacts with the DecentralChain (DCC) blockchain to retrieve detailed information about a specific token or asset. The "Get Token Details" operation fetches comprehensive metadata and status for a given token/asset identifier from a DCC node API.

Typical use cases include:

  • Displaying token details such as name, description, total supply, decimals, and other metadata in dashboards.
  • Verifying token existence and properties before performing transactions.
  • Integrating token data into DeFi applications or wallets that support DCC tokens.

For example, a user can input an Asset ID to get its current details like issuance info, reissuability, and other on-chain attributes.

Properties

Name Meaning
Base URL The base URL of the DecentralChain node API to query. Used if no credential is supplied. Default: https://nodes.decentralchain.io
Asset ID The unique identifier of the token or asset whose details are to be retrieved.

Output

The output JSON contains the full response from the DCC node API endpoint /assets/details/{assetId}. This typically includes:

  • Token/Asset metadata such as name, description, issuer, decimals, total supply.
  • Status flags like whether the token is reissuable.
  • Blockchain-specific identifiers and timestamps.
  • Other relevant on-chain data related to the token.

No binary data is output by this operation.

Example output snippet (simplified):

{
  "id": "assetId",
  "name": "TokenName",
  "description": "Token description",
  "decimals": 8,
  "reissuable": true,
  "totalSupply": 1000000000,
  "issuer": "address",
  ...
}

Dependencies

  • Requires access to a DecentralChain node API endpoint, either via a configured credential or the provided Base URL.
  • Uses HTTP GET requests to fetch token details.
  • No additional external libraries are required specifically for this operation beyond standard HTTP request capabilities.

Troubleshooting

  • Invalid Asset ID: If the Asset ID does not exist or is malformed, the API may return an error or empty result. Verify the Asset ID correctness.
  • Network Issues: Failure to connect to the Base URL or credential endpoint will cause errors. Ensure network connectivity and correct Base URL.
  • API Rate Limits: Excessive requests might be throttled by the node API. Implement retries or backoff if needed.
  • Credential Missing or Invalid: If credentials are expected but missing or invalid, authentication errors may occur.
  • Unexpected API Response: Changes in the DCC node API could affect the returned data structure. Check API documentation for updates.

Links and References

This summary is based solely on static analysis of the provided source code and property definitions.

Discussion