Baike.dev
All toolsOnline toolsAI codingTrendingOpen sourceNewsSubmit
Log in
< Back to tools
R

rainbow-bridge

> 编程语言
Open source

NEAR <> Ethereum Decentralized Bridge

328 stars0 likes0 views
WebsiteGitHub

About

NEAR <> Ethereum Decentralized Bridge

Table of Contents

  • Pre-requisites
  • Usage
  • Security
  • Gas costs
  • Using Bridge on Testnet
  • Deploying and Using Locally
  • Contract Development Workflow

Pre-requisites

The current version of CLI is all-in-one package -- it is used both for production and testing. As a result, even if you need CLI only for the token transfer you need to install all testing dependencies. This will be changed in the future.

  • Install golang, see.
  • Make sure you are using Node with version >=12 and NEAR transfer of ERC20 token is 1 USD. The cost of NEAR->ETH transfer of ERC20 token is 2 USD.

Using Bridge on Testnet

PoA vs PoW Ethereum networks

Rainbow bridge can be deployed either on PoW or PoA networks. However, the main use case of the bridge is Ethereum Mainnet, which makes its design very PoW-centric and it is only trustless and decentralized for PoW networks. Unfortunately, the only popular PoW testnet is Ropsten, which frequently undergoes huge reorgs of more than 16k blocks, because people test 51% attacks on it. 16k reorgs can wipe out entire contracts and revert days of computations. Overall, Ropsten has the following unfortunate specifics that does not exist with Ethereum Mainnet:

  • Extremely long re-orgs;
  • Gas price volatility -- Ropsten blocks might have orders of magnitude different median gas price;
  • Slow block production -- sometimes Ropsten blocks are produced once per several minutes;
  • Infura is unreliable on Ropsten

Therefore we advise users to not use Ropsten for bridge testing. Instead, we recommend using one of Ethereum's PoA testnet. Unfortunately, PoA networks have a differen header format and are also centralized by nature. Therefore when deploying bridge on PoA network please use --near-client-trusted-signer parameter. This will force EthOnNearClient to not validate Ethereum headers (since PoA headers are not valid PoW headers) and accept them only from the provided authority.

The documenation below assumes Rinkeby testnet.

Using existing bridge on Rinkeby

This section explains how to use existing bridge with mock ERC20 token that was already deployed. You would need to have some amount of this token on Rinkeby, so reach out to [email protected] if you want to give it a try.

We assume you have two accounts:

  • One NEAR account on NEAR testnet with at least 1 NEAR token. We denote it as and its secret key as;
  • One Ethereum account on Rinkeby testnet with at least 1 ETH and 100 ERC20 tokens (this example uses ERC20 deployed to 0x8151a8F90267bFf183E06921841C5dE774499388 as an example. If you want some of these ERC20 tokens please contact [email protected]). We denote it as and its private key as;

Make sure you have rainbow cli installed:

bash
yarn install

If you have already used the bridge on this machine run a cleanup:

bash
cli/index.js clean

If you're using rainbow-bridge-cli 1.x, create ~/.rainbow/config.json file with the following content:

…

If you are using rainbow-bridge-cli 2.x, create ~/.rainbow/config.json file with the following content:

…

You can get infura project id, by registering at infura.io.

To transfer ERC20 from ETH to NEAR run:

bash
cli/index.js TESTING transfer-eth-erc20-to-near --amount 10 --eth-sender-sk  --near-receiver-account 

(If the command interrupts in the middle re-run it and it will resume the transfer. PoA RPC sometimes has issues) Wait for the transfer to finish. You should see:

Transferred
Balance of  after the transfer is 10

To transfer ERC20 back from NEAR to ETH run:

bash
cli/index.js TESTING transfer-eth-erc20-from-near --amount 1 --near-sender-account  --near-sender-sk  --eth-receiver-address 

You should see:

ERC20 balance of  after the transfer: 91

Congratulations, you have achieved a roundtrip of ERC20 token through the bridge!

Deploying and Using Locally

To locally test the bridge run:

bash
cli/index.js clean
cli/index.js prepare
cli/index.js start near-node
cli/index.js start ganache

Initializing the contracts

First let's initialize the contracts that bridge needs to function:

bash
cli/index.js init-near-contracts
cli/index.js init-eth-ed25519
cli/index.js init-eth-client --eth-client-lock-eth-amount 1000 --eth-client-lock-duration 10
cli/index.js init-eth-prover

Now, let's set up token on Ethereum blockchain that we can transfer to NEAR blockchain (this can be your own token).

bash
cli/index.js init-eth-erc20
cli/index.js init-eth-locker

Now, let's initialize token factory on NEAR blockchain.

bash
cli/index.js init-near-token-factory

Starting the services

Now start the services that will relay the information between the chains:

bash
cli/index.js start eth2near-relay
cli/index.js start near2eth-relay --eth-master-sk 0x2bdd21761a483f71054e14f5b827213567971c676928d9a1808cbfa4b7501201
cli/index.js start bridge-watchdog --eth-master-sk 0x2bdd21761a483f71054e14f5b827213567971c676928d9a1808cbfa4b7501202

Note, you can observe the logs of the relays by running:

bash
pm2 logs

Transferring tokens

Let's check the balance of bridged tokens from ETH to NEAR before starting the transfer. To this end let's use node0 account, which is automatically created and funded on startup when localnet is started.

bash
cli/index.js TESTING get-bridge-on-near-balance --near-receiver-account node0

Then transfer some tokens with:

bash
cli/index.js TESTING transfer-eth-erc20-to-near --amount 1000 --eth-sender-sk 0x2bdd21761a483f71054e14f5b827213567971c676928d9a1808cbfa4b7501200 --near-receiver-account node0 --near-master-account neartokenfactory

Now you check the balance of node0 again. You should notice the balance was changed.

Note, when we deployed ERC20 to the Ethereum blockchain we have minted a large number of tokens to the default master key of Ganache, so we have transferred ERC20 tokens from it to node0 account. Notice that we are using neartokenfactory.node0 account here to pay for the NEAR gas fees, any account for which we know a secret key would've worked too. You must observe blocks being submitted.

You can also manually check the ERC20 balance of the receiver before and after receiving the transfer back from the NEAR side

bash
cli/index.js TESTING get-erc20-balance 0xEC8bE1A5630364292E56D01129E8ee8A9578d7D8

Now let's try to transfer one token back to Ethereum

bash
cli/index.js TESTING transfer-eth-erc20-from-near --amount 1 --near-sender-account node0 --near-sender-sk ed25519:3D4YudUQRE39Lc4JHghuB5WM8kbgDDa34mnrEP5DdTApVH81af7e2dWgNPEaiQfdJnZq1CNPp5im4Rg5b733oiMP --eth-receiver-address 0xEC8bE1A5630364292E56D01129E8ee8A9578d7D8

You should observe the change of the ERC20 balance as reported by the CLI.

Stopping the services

To stop relay services and node clients execute the following command:

bash
cli/index.js stop all

Or you can stop them one by one using these commands:

bash
cli/index.js stop near-node
cli/index.js stop ganache
cli/index.js stop eth2near-relay
cli/index.js stop near2eth-relay
cli/index.js stop bridge-watchdog

Contract Development Workflow

Above steps are ways to run a local bridge and development workflows you need if make any changes to rainbow-bridge-cli. If you want to update any of solidity or rust contracts, they're not in this repo now and workflow is as following.

  • Install dependencies:
bash
cli/index.js clean
cli/index.js prepare
  • Start local NEAR network and Ganache
bash
cli/index.js near-node
cli/index.js ganache
  • If you want to modify solidity contracts, go to node_modules/rainbow-bridge-sol, make changes there and run ./build_all.sh to recompile solidity contracts.
  • If you want to modify rust contracts, go to node_modules/ranbow-bridge-rs, make changes there and run ./build_all.sh to recompile rust contracts.
  • If you want to modify rainbow bridge lib, go to node_modules/rainbow-bridge-lib and make changes there
  • Follow instructions above to init eth contracts and near contracts, start services and start testing with bridge
  • For changes to Solidity contract, Rust contract, and rainbow-bridge-lib, please submit PRs to: https://github.com/near/rainbow-bridge-sol , https://github.com/near/rainbow-bridge-rs , and https://github.com/near/rainbow-bridge-lib respectively.
  • After PR merged in contract repos and rainbow-bridge-lib repo, we will periodically publish them as new version of npm packages. And rainbow-bridge-cli will adopt new version of them.

Issues· 0 open

View all issuesOpen on GitHub

No open issues yet, or sync has not completed.

> Tags

Rust

No comments yet. Be the first to share.

> Details

PublishedAug 1, 2026
UpdatedSep 18, 2026
Category编程语言
PricingOpen source

> Related tools

T
TypeScript
JavaScript 的超集,为前端与全栈提供静态类型
P
Python
通用编程语言,广泛用于 Web、数据与 AI
G
Go
Google 推出的简洁高效系统语言