Appearance
IOST 3.0 L2 Mainnet Connection Guide
This guide provides all necessary configuration parameters and resources needed to connect to the IOST 3.0 Layer 2 network, helping developers quickly integrate with the ecosystem.
Official Contract Addresses
The following are the official IOST token contract addresses on various networks:
Network | Token Name | Contract Address | Token Standard | Deployment Date |
---|---|---|---|---|
BSC (BNB Smart Chain) | IOSToken (IOST) | 0xAf48B7e315a52518CfBF7d96C455D9dFAD94cB48 | BEP-20 | Mar-08-2025 |
TIP
Always verify contract addresses when integrating with IOST tokens. The addresses listed above are the only official IOST token contracts.
Network Parameters
The following are the core network parameters required to connect to IOST Layer 2:
Parameter | Value |
---|---|
Network name | IOST Mainnet |
Type | Mainnet |
Native Asset Symbol | BNB |
Decimal | 18 |
Chain-ID | 182 |
Explorer | https://l2-scan.iost.io/ |
RPC Endpoint | https://l2-mainnet.iost.io |
WebSocket | wss://l2-mainnet.iost.io/ws |
Quick Add | https://chainlist.org/?search=IOST+Mainnet |
Cross-Chain Bridge
IOST 3.0 L2 offers a dedicated bridge for transferring assets between BSC and IOST Layer 2 networks:
Parameter | Value |
---|---|
Bridge URL | https://l2-bridge.iost.io/ |
Type | Bi-directional |
Source Chain | BSC |
Destination Chain | IOST Layer 2 |
Using the Bridge
- Visit IOST L2 Bridge
- Connect your wallet (MetaMask or similar)
- Select the source and destination networks
- Choose the asset and amount to transfer
- Confirm the transaction in your wallet
- Wait for confirmation (typically 2-10 minutes depending on network congestion)
Supported Assets
The bridge currently supports the following assets:
- BNB (Native token)
Coming soon:
- USDT
- IOST
- Other community-requested assets
Safety Recommendations
- Always start with small test transactions
- Verify all transaction details before confirming
- Be aware of gas fees on both networks
- For large transfers, consider splitting into smaller amounts
Development Tool Configuration
MetaMask Configuration
- Open MetaMask, click the network dropdown menu, and select "Add Network"
- Click "Add Network Manually"
- Enter the following information:
- Network Name:
IOST Mainnet
- RPC URL: https://l2-mainnet.iost.io
- Chain ID:
182
- Currency Symbol:
BNB
- Block Explorer URL: https://l2-scan.iost.io/
- Network Name:
Hardhat Configuration
Add the following configuration to your hardhat.config.js
file:
javascript
module.exports = {
networks: {
iostl2: {
url: "https://l2-mainnet.iost.io",
chainId: 182,
accounts: [process.env.PRIVATE_KEY]
}
}
};
SDK and API Examples
Web3.js
Example Basic example of connecting to IOST Layer 2 network:
javascript
const Web3 = require('web3');
const web3 = new Web3('https://l2-mainnet.iost.io');
async function getNetworkInfo() {
const blockNumber = await web3.eth.getBlockNumber();
console.log(`Current block number: ${blockNumber}`);
const chainId = await web3.eth.getChainId();
console.log(`Chain ID: ${chainId}`);
}
getNetworkInfo();
ethers.js Example
Using ethers.js
to connect to IOST Layer 2 network:
javascript
const { ethers } = require('ethers');
const provider = new ethers.providers.JsonRpcProvider('https://l2-mainnet.iost.io');
async function getAccountBalance(address) {
const balance = await provider.getBalance(address);
console.log(`Balance: ${ethers.utils.formatEther(balance)} BNB`);
}
getAccountBalance('0xYourAddressHere');
Frequently Asked Questions
Troubleshooting Connection Issues
If you encounter connection problems, try the following steps:
- Confirm you're using the most recent RPC endpoint
- Try using an alternative RPC endpoint
- Clear browser cache or restart your development environment
Resource Limitations
- Please note that public RPC endpoints have request rate limits
- For production applications, we recommend using dedicated nodes or third-party providers like Infura, Alchemy, etc.