Token Compatibility
User guide to understand which tokens are supported by the Shibarium bridge and their specific requirements
This guide is designed for users who want to understand token compatibility for bridge operations. For technical implementation details, see the Developer Guides.
Supported Token Standards
The bridge supports different token standards depending on the bridge type and direction:PoS Bridge (Recommended)
The PoS bridge offers the widest token support and is recommended for most users:| Token Standard | Support Level | Description |
|---|---|---|
| ETH | ✅ Full Support | Native Ethereum token |
| ERC20 | ✅ Full Support | Standard fungible tokens |
| ERC721 | ✅ Full Support | Non-fungible tokens (NFTs) |
| ERC1155 | ✅ Full Support | Multi-token standard |
| Other Standards | ✅ Full Support | Additional token standards as supported |
PoS bridge provides the most flexibility and supports the widest range of token standards.
Plasma Bridge
The Plasma bridge offers enhanced security but with more limited token support:| Token Standard | Support Level | Description |
|---|---|---|
| ETH | ✅ Full Support | Native Ethereum token |
| ERC20 | ✅ Full Support | Standard fungible tokens |
| ERC721 | ✅ Full Support | Non-fungible tokens (NFTs) |
| ERC1155 | ❌ Not Supported | Not supported on Plasma bridge |
| Other Standards | ❌ Not Supported | Limited to ETH, ERC20, ERC721 only |
Plasma bridge prioritizes security over flexibility, supporting only the most established token standards.
Popular Supported Tokens
The bridge supports many popular tokens in the Shibarium ecosystem:Native Tokens
- SHIB - Shiba Inu token
- BONE - Shibarium gas token
- LEASH - Doge Killer token
Major ERC20 Tokens
- USDC - USD Coin
- USDT - Tether
- DAI - Dai Stablecoin
- WETH - Wrapped Ethereum
- WBTC - Wrapped Bitcoin
NFT Collections
- Shiboshis - Shiba Inu NFT collection
- Shiba Eternity - Gaming NFTs
- Custom NFTs - User-created NFT collections
Most major tokens in the Shibarium ecosystem are fully supported for bridging.
Token Requirements
General Requirements
All tokens must meet these basic requirements for bridge compatibility:- Valid Contract: Token must have a valid smart contract on the source network
- Sufficient Balance: User must have sufficient tokens to bridge
- Gas Fees: Sufficient gas fees for the source network
- Network Support: Token must be supported on both networks
Specific Requirements by Token Type
ETH Requirements
ETH Requirements
- Must be native ETH (not WETH unless specifically bridging WETH)
- Sufficient ETH for gas fees on source network
- Valid Ethereum address for destination
- Consider gas price optimization for large amounts
ERC20 Requirements
ERC20 Requirements
- Token contract must be verified and audited
- Token must have proper transfer functions
- Sufficient token balance for transfer
- Token must be listed on the bridge interface
ERC721 Requirements
ERC721 Requirements
- NFT must be owned by the bridging address
- NFT contract must support standard ERC721 functions
- Token ID must be valid and transferable
- Consider gas costs for individual NFT transfers
ERC1155 Requirements
ERC1155 Requirements
- Only supported on PoS bridge
- Batch transfers supported for efficiency
- Token IDs must be valid and owned
- Consider gas optimization for batch operations
Token Mapping
How Token Mapping Works
When tokens are bridged, they are mapped between networks:- Ethereum to Shibarium: Tokens are locked on Ethereum and minted on Shibarium
- Shibarium to Ethereum: Tokens are burned on Shibarium and unlocked on Ethereum
- 1:1 Ratio: All transfers maintain a 1:1 ratio to preserve circulating supply
Token mapping ensures that the total circulating supply remains constant across both networks.
Mapping Verification
To verify token mapping:- Check the official bridge interface for supported tokens
- Verify token contract addresses on both networks
- Confirm token symbols and decimals match
- Review bridge documentation for specific token requirements
Token-Specific Considerations
Stablecoins
USDC Bridging
USDC Bridging
- USDC maintains 6 decimal places on both networks
- Bridged USDC is fully redeemable for USD
- Consider network-specific USDC versions
- Monitor for any network-specific restrictions
USDT Bridging
USDT Bridging
- USDT maintains 6 decimal places on both networks
- Bridged USDT maintains full backing
- Consider regulatory implications
- Monitor for network-specific limitations
Wrapped Tokens
WETH Bridging
WETH Bridging
- WETH can be bridged as ERC20 token
- Consider unwrapping to ETH before bridging
- Monitor gas costs for wrapping/unwrapping
- Verify WETH contract addresses on both networks
WBTC Bridging
WBTC Bridging
- WBTC maintains 8 decimal places
- Verify WBTC backing and redemption
- Consider regulatory requirements
- Monitor for any network-specific restrictions
NFTs
NFT Bridging Considerations
NFT Bridging Considerations
- Each NFT requires individual bridge transaction
- Higher gas costs for NFT transfers
- Verify NFT ownership before bridging
- Consider metadata preservation across networks
NFT Metadata
NFT Metadata
- NFT metadata should be preserved during bridging
- Verify image and attribute consistency
- Check for network-specific metadata formats
- Ensure NFT remains functional on destination network
Token Limits and Restrictions
Transfer Limits
Transfer limits may apply to certain tokens for security and network stability.
| Token Type | Minimum Amount | Maximum Amount | Notes |
|---|---|---|---|
| ETH | 0.001 ETH | No limit | Gas fees apply |
| ERC20 | Token-specific | Token-specific | Check bridge interface |
| ERC721 | 1 NFT | No limit | Per transaction |
| ERC1155 | 1 token | No limit | Batch transfers supported |
Network-Specific Restrictions
Ethereum Restrictions
Ethereum Restrictions
- Higher gas fees during network congestion
- Slower processing during peak times
- Potential for failed transactions
- Consider gas price optimization
Shibarium Restrictions
Shibarium Restrictions
- Lower gas fees compared to Ethereum
- Faster processing times
- BONE required for gas fees
- Network-specific token requirements
Troubleshooting Token Issues
Token Not Supported
Token Not Supported
- Check if token is listed on bridge interface
- Verify token contract is valid and audited
- Contact support for token addition requests
- Consider using alternative bridge or method
Transfer Failed
Transfer Failed
- Verify sufficient token balance
- Check gas fees on source network
- Ensure token is not paused or restricted
- Review token-specific requirements
Token Not Received
Token Not Received
- Wait for full processing time
- Verify destination address is correct
- Check token mapping on destination network
- Monitor transaction status on both networks
Incorrect Token Amount
Incorrect Token Amount
- Verify token decimals on both networks
- Check for any transfer fees or taxes
- Review token-specific transfer logic
- Contact support for assistance
Best Practices
Token Verification
Token Verification
- Always verify token contract addresses
- Check token symbols and decimals
- Review token-specific documentation
- Test with small amounts first
Gas Optimization
Gas Optimization
- Monitor gas prices on both networks
- Consider batch transfers for multiple tokens
- Use appropriate gas limits
- Avoid bridging during peak congestion
Security Considerations
Security Considerations
- Only bridge verified and audited tokens
- Verify token contract addresses
- Check for any known vulnerabilities
- Monitor for suspicious activity
Next Steps
- Learn about Ethereum to Shibarium transfers
- Understand Shibarium to Ethereum transfers
- Explore deposit tokens procedures
- Discover withdrawal methods for different token types