Complete guide for integrating The Open Network into your Bicrypto Ecosystem
This guide shows you how to integrate TON (The Open Network) into your Bicrypto Ecosystem. TON differs from EVM-based chains in its address formats and transaction methods, but Bicrypto handles it using a similar workflow.
TON mainnet and testnet are supported. Toncoin (TON) is used for transaction fees. Future support for Jetton-based tokens may be available.
Add the following TON-specific variables to your .env file:
# TON Networks (mainnet, testnet)
TON_NETWORK="testnet" # or "mainnet"
TON_MAINNET_RPC="https://YOUR_MAINNET_RPC_URL"
TON_MAINNET_RPC_API_KEY="YOUR_MAINNET_API_KEY"
TON_TESTNET_RPC="https://YOUR_TESTNET_RPC_URL"
TON_TESTNET_RPC_API_KEY="YOUR_TESTNET_API_KEY"
• TON_NETWORK: Active network (mainnet or testnet)
• RPC URLs: Endpoint URLs for each network
• API Keys: Authentication keys for RPC providers (if required)
If you host your own TON node or use a different provider, replace the placeholder URLs with your custom endpoints.
YOUR_MAINNET_RPC_URL
Currently, enable Toncoin for your TON network. Future updates may include Jetton-based tokens if Bicrypto adds support for them.
TON transaction fees are typically low but can vary based on network usage. Adjust your minimum fees accordingly.
TON uses a different address format than EVM chains. Bicrypto handles this automatically, but ensure you're using the correct network settings.