DecentralChain (DCC)Install

Overview

This node interacts with the DecentralChain (DCC) blockchain network to perform various operations related to accounts, tokens/assets, transactions, utilities, and matcher services. Specifically for the Token/Asset resource with the Get NFTs operation, it retrieves a list of NFTs owned by a specified address on the DCC blockchain.

Typical use cases include:

• Fetching all NFTs owned by a user’s wallet address for display or further processing.
• Integrating NFT ownership verification into workflows.
• Building dashboards or reports that show NFT holdings on the DecentralChain network.

Example: Given a wallet address, this node can query the blockchain and return detailed information about all NFTs owned by that address, up to a specified limit.

Properties

Note: For the "Get NFTs" operation, additional parameters used internally but not listed in your provided properties include:

• address (string): The wallet address whose NFTs will be fetched.
• limit (number, default 100): Maximum number of NFTs to retrieve.

These are required inputs for the operation but were not included in your JSON snippet.

Output

The output JSON contains the response from the DecentralChain API endpoint /assets/nft/{address}/limit/{limit}. It includes:

• An array or object listing NFTs owned by the specified address.
• Each NFT entry typically contains metadata such as token ID, name, description, and other asset details as returned by the blockchain node.
• A debug field may be present containing request metadata like operation name, endpoint URL, base URL, parameters used, and timestamp for traceability.

No binary data output is produced by this operation.

Dependencies

• Requires access to a DecentralChain node API endpoint, either via supplied credentials or the fallback base URL.
• Optional credentials for API authentication can be configured in n8n to override the base URL.
• Uses HTTP requests to communicate with the blockchain node.
• No external libraries beyond standard n8n helpers and optional Waves transactions library (not directly relevant for this read-only operation).

Troubleshooting

• Common issues:

  • Invalid or malformed wallet address input will cause the API call to fail.
  • Network connectivity problems or incorrect base URL will prevent successful API calls.
  • Exceeding the maximum allowed limit for NFTs might result in truncated results or errors.

• Error messages:

  • "Invalid JSON in Order JSON" — unrelated to this operation, but indicates malformed JSON input in other operations.
  • HTTP errors from the blockchain node (e.g., 404 Not Found, 400 Bad Request) indicate invalid parameters or unavailable resources.

• Resolutions:

  • Verify the wallet address format before running the node.
  • Ensure the base URL or credentials point to a valid and accessible DecentralChain node.
  • Adjust the limit parameter within acceptable bounds.

Links and References

• DecentralChain Official Node API Documentation (for detailed API endpoints and parameters)
• n8n Documentation (for general usage of HTTP Request nodes and custom nodes)
• Waves Transactions Library (related library used in other operations)

If you want me to extract details for other operations or resources, or provide more property descriptions, just let me know!