Transitioning from Polygon Mumbai to Avalanche Fuji: Seeking USDT Asset ID for Integration

I’m currently integrating USDC and USDT into an Ethereum mainnet environment using Fireblocks. Fireblocks provides a list of supported asset IDs through their API endpoint
List all assets and assets types supported by Fireblocks.

Initially, for testing purposes, we were utilizing the Polygon Mumbai network with the following asset IDs:

  • MATIC_POLYGON_MUMBAI for USDC
  • USDT_POLYGON_TEST_MUMBAI_ZU3P for USDT

However, since Polygon Mumbai is deprecated, I’m considering transitioning to Avalanche Fuji. I’ve found an asset ID for USDC (AVAXTEST), but I’m uncertain if there’s a supported asset ID for USDT on the Avalanche network.

Could someone confirm if there’s a supported asset ID for USDT on Avalanche Fuji, or suggest an alternative approach for integrating USDT in an Ethereum mainnet environment with Fireblocks? Thank you.

Hi @adityapadekar
Confirming that there is a supported asset ID for USDT on Avalanche Fuji:
{
“id”: “USDT_AVAX”,
“name”: “Tether USD (Avalanche)”,
“type”: “ERC20”,
“contractAddress”: “0xc7198437980c041c805A1EDcbA50c1Ce5db95118”,
“nativeAsset”: “AVAX”,
“decimals”: 6
},
And although you have a USDC alternative we also support USDC on the avalanche network:
{
“id”: “USDC_AVAX”,
“name”: “USD Coin (Avalanche)”,
“type”: “ERC20”,
“contractAddress”: “0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E”,
“nativeAsset”: “AVAX”,
“decimals”: 6
},
I hope this helps

When providing asset id, do we take the id or nativeAsset?

@adityapadekar , Can you please clarify your question? When using using API endpoints we use the id: eg:USDC_AVAX/USDT_AVAX”, The native Asset is normally not used. I hope this clarifies a bit.