Practical overview
When it fits
Use Tokenbridge when the task is to transfer ERC-20 tokens between Ethereum and Rootstock, or to work with the bridge's contracts and federator components.
Who it is for
- Token holders seeking to move ERC-20 tokens between Ethereum and Rootstock using the documented bridge flow.
- Developers deploying or integrating bridge contracts and federators on configured networks.
Documented uses
- Move ERC-20 tokens across Ethereum and Rootstock through a lock-and-mint bridge flow.
- Relay and validate bridge events through a federation of oracles.
- Deploy bridge contracts and prepare contract-and-federator integration tests for configured networks.
Requirements & limits
The repository is public and identifies its license as MIT. Its README describes a Dapp flow using Nifty Wallet or MetaMask configured for RSK, as well as contract interaction through a wallet and ABI.
- Transfers rely on federation-based event relaying; the README says a majority of federators must vote for an event to be accepted.
- The documented Dapp flow calls for Nifty Wallet or MetaMask configured for RSK; contract interaction through a wallet and ABI is also described.
- Integration tests require network-specific configuration and the listed bridge key files.
- The README describes the bridge contracts as upgradeable and frames a move toward a more decentralized bridge as a future possibility.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare an integration test for configured chains
Configure the repository's bridge and federator integration test for test chains.
Before you start
- The repository and its bridge and federator components.
- Test-chain settings for the bridge's Truffle configuration and package.json.
- bridge/mnemonic.key and bridge/infura.key, with the Infura project ID in plain text.
- A network name in bridge/migrations/4_deploy_erc1820.js if the test network lacks the ERC1820 pseudo-introspection registry.
Steps
Check the network configuration in truffle-config.js and package.json in the bridge folder.
Check mnemonic.key and infura.key in bridge.
If the test chain lacks the ERC1820 registry, check networkName in bridge/migrations/4_deploy_erc1820.js.
Run npm run deployIntegrationTest in bridge, then npm run integrationTest in federator.
Expected outcome
The repository's documented integration-test deployment and test sequence is configured for the selected test chains.
Guide limitations
- The README requires configuration for the test chains; it does not document one universal network setup.
- An empty FEDERATOR_KEY and federator/config/test.local.config.js are described for testing purposes only.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- rsksmart/tokenbridge · Official homepage title · retained in its source language

