Understanding Blockchain Assets and Their Support in CDP APIs

·

Blockchain technology has revolutionized how we define and exchange value. At the heart of this transformation are digital assets, which represent ownership or utility on decentralized networks. These assets come in various forms, including fungible tokens like cryptocurrencies and non-fungible tokens (NFTs) that signify unique digital items.

This article explores the concept of blockchain assets, focusing on how they are supported within CDP APIs, particularly across networks such as Base Mainnet, Base Sepolia, Ethereum, Polygon, and Arbitrum. Whether you're building decentralized applications (dApps), managing wallets, or integrating asset transfers, understanding how assets are identified—by symbol or contract address—is essential.

Core Blockchain Assets: Symbols vs. Contract Addresses

Digital assets on blockchain networks can be referenced in two primary ways: by symbol (e.g., ETH, USDC) or by contract address. The CDP API supports both methods, but with important distinctions.

Assets Supported by Symbol

The CDP API natively recognizes several key assets through their ticker symbols on the Base network (both Mainnet and Sepolia testnet). This simplifies integration for developers who want to interact with widely used tokens without manually inputting contract details.

Here are the major assets supported by symbol:

👉 Discover how to integrate top blockchain assets into your application effortlessly.

All of these assets are supported on Base Mainnet, while only ETH and USDC are fully available on Base Sepolia for testing purposes. This allows developers to prototype with real-world assets in a sandbox environment before going live.

Beyond Base, CDP APIs also support:

These cross-chain capabilities make the API a powerful tool for multi-network dApp development.

Assets Supported by Contract Address

For any ERC-20 token not listed by symbol, the CDP API enables support via contract address. This means developers can interact with virtually any token deployed on supported blockchains, provided they have the correct contract identifier.

For example:

This flexibility ensures future-proofing for emerging tokens and niche ecosystems.

👉 Learn how to securely manage ERC-20 tokens using contract addresses in your projects.

Fetching Asset Balances

One of the most common operations in wallet and dApp development is checking a user's balance. The CDP API provides methods to fetch balances for both symbol-based and contract-address-based assets.

Fetch Balance by Symbol

When working with supported symbols like ETH or USDC, developers can directly query balances using standardized identifiers. For instance:

const ethBalance = await wallet.getBalance(Coinbase.assets.Eth);

This returns the available amount in the wallet’s default denomination (usually ETH or Wei).

Fetch Balance by Contract Address

For custom tokens, the balance query must include the token’s contract address:

const customTokenBalance = await wallet.getBalance("0x...");

This approach supports all ERC-20 tokens deployed on compatible networks.

Denominations of Ether (ETH): Understanding Wei, Gwei, and ETH

Ether supports up to 18 decimal places. This high precision is crucial for microtransactions and accurate gas calculations.

DenominationValue in WeiUse Case
Wei1Smallest unit; used internally
Gwei1,000,000,000Commonly used for gas pricing
ETH1,000,000,000,000,000,000Standard unit for trading and transfers

The SDK allows developers to work seamlessly across these units when sending transactions or calculating fees.


Frequently Asked Questions

Q: What’s the difference between fungible tokens and NFTs?
A: Fungible tokens (like ETH or USDC) are interchangeable—each unit holds equal value. NFTs (non-fungible tokens) represent unique digital assets, such as art or collectibles, where each token is distinct.

Q: Can I use CDP APIs to support new tokens not listed by symbol?
A: Yes. Any ERC-20 token can be integrated using its contract address, even if it isn't natively supported by symbol.

Q: Why is Base Sepolia limited to only ETH and USDC?
A: Base Sepolia is a testnet designed for development and experimentation. Limiting supported assets helps maintain stability while still allowing realistic simulations with major tokens.

Q: How do I find a token’s contract address?
A: You can look it up on blockchain explorers like Basescan or Etherscan by searching the token name or symbol.

Q: Is there a risk in using contract addresses manually?
A: Yes—entering an incorrect or malicious contract address can lead to loss of funds. Always verify addresses from trusted sources.

Q: What networks does the CDP API currently support?
A: Primary support includes Base (Mainnet & Sepolia), Ethereum Mainnet, Polygon Mainnet, and Arbitrum Mainnet—with potential expansion based on ecosystem growth.


Developer Tools and SDK Integration

The Coinbase SDK streamlines interaction with digital assets through intuitive class structures. In Node.js environments:

const ethAsset = Coinbase.assets.Eth;
const usdcAsset = Coinbase.assets.Usdc;
const wethAsset = Coinbase.assets.Weth;

These predefined constants eliminate the need to hardcode values and reduce error risks during development.

For full technical specifications and method references, consult the official Asset class SDK documentation.


👉 Start building with advanced blockchain asset tools today—explore seamless integration options now.

By combining broad asset support, flexible identification methods, and precise denomination handling, CDP APIs empower developers to create robust, scalable blockchain applications. Whether you're launching a wallet service, DeFi platform, or NFT marketplace, mastering asset management is the first step toward innovation in Web3.

Keywords: blockchain assets, ERC-20 tokens, CDP APIs, Base network, ETH denominations, contract address, USDC support