Multi-Chain Support
HashNut supports 164+ blockchain networks, enabling merchants to accept payments across the entire Web3 ecosystem through a unified API.
Supported Networks
EVM-Compatible Chains (150+)
Popular EVM Chains:
- Ethereum (Mainnet & Testnets)
- Polygon (Mainnet & Mumbai)
- Binance Smart Chain (BSC)
- Arbitrum One
- Optimism
- Base
- Avalanche C-Chain
- Fantom
- And 140+ more...
TRON Network
TRON Support:
- TRON Mainnet
- TRON Testnet (Shasta)
- TRC-20 tokens (USDT, USDC, etc.)
Other Networks (12+)
Unified API Interface
Key Benefit: Use the same API for all chains - no chain-specific code needed!
Chain Codes
Each chain is identified by a unique chainCode:
| Chain Type | chainCode Format | Examples |
|---|---|---|
| EVM ERC-20 | erc20, {chain}-erc20 | erc20, polygon-erc20, bsc-erc20 |
| TRON TRC-20 | tron-trc20 | tron-trc20 |
Common Chain Codes
// Ethereum
chainCode: "erc20"
// Polygon
chainCode: "polygon-erc20"
// Binance Smart Chain
chainCode: "bsc-erc20"
// TRON
chainCode: "tron-trc20"
Chain Selection
Querying Supported Chains
// Query all supported chains
const response = await fetch(
'https://testnet.hashnut.io/api/v2.0.0/config/queryAllChainInfo',
{ method: 'POST' }
);
const chains = await response.json();
// Returns array of all supported chains with details
Response includes:
- Chain name and code
- Network ID (chainId)
- Confirmation requirements
- WalletConnect support
- Bridge server addresses
Querying Supported Tokens
// Query tokens for a specific chain
const response = await fetch(
'https://testnet.hashnut.io/api/v2.0.0/config/querySupportCoinsByChainCode',
{
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ chainCode: 'erc20' })
}
);
const tokens = await response.json();
// Returns all supported tokens for that chain
Multi-Chain Payment Flow
Chain-Specific Features
EVM Chains
Features:
- ERC-20 token support
- WalletConnect protocol
- EIP-712 signature support
- EIP-1559 fee support
- MetaMask integration
Wallet Support:
- MetaMask
- WalletConnect
- imToken
- Trust Wallet
- Token Pocket
TRON Network
Features:
- TRC-20 token support
- TronLink integration
- Native TRX support
- TRON-specific optimizations
Wallet Support:
- TronLink (Extension & Mobile)
- TronLink Pro
Network Configuration
Chain-Specific Settings
Each chain has configurable settings:
Configurable Per Chain:
- Confirmation Requirements: Number of block confirmations needed
- Gas Settings: EIP-1559 support, gas limits
- WalletConnect: Bridge server addresses
- EIP-712: Chain ID for signature verification
Cross-Chain Considerations
Separate Accounts Per Chain
Important: Each chain requires a separate account/smart contract deployment.
Unified Reporting
Despite separate accounts, HashNut provides:
- Unified Dashboard: View all chains in one place
- Cross-Chain Analytics: Aggregate reporting across chains
- Unified API: Same API for all chains
Token Support
Standard Tokens
All Chains Support:
- USDT (Tether)
- USDC (USD Coin)
Chain-Specific:
- Ethereum: Native ETH + ERC-20 tokens
- Polygon: Native MATIC + ERC-20 tokens
- BSC: Native BNB + BEP-20 tokens
- TRON: Native TRX + TRC-20 tokens
Adding New Tokens
Best Practices
Choosing the Right Chain
-
Consider Transaction Costs:
- Polygon: Low fees, fast confirmations
- Ethereum: Higher fees, maximum security
- BSC: Moderate fees, good performance
- TRON: Very low fees, fast confirmations
-
Consider User Base:
- Which chains do your customers use?
- Which wallets are most common?
- Regional preferences
-
Consider Token Availability:
- USDT/USDC available on all chains
- Some tokens chain-specific
Multi-Chain Strategy
Recommended Approach:
- Choose a primary chain for most transactions
- Add secondary chains based on user demand
- Monitor performance across chains
- Optimize based on fees and speed
Network Status
HashNut monitors all supported chains for:
- Network uptime
- Transaction confirmation times
- Gas price trends
- Token availability
Next Steps
- Learn about Smart Contracts architecture
- Understand Payment Flow across chains
- Explore API Reference for chain-specific endpoints
Ready to accept payments on multiple chains? Check out Getting Started →