ETH-TON bridge allows to transfer in decentralized way TON Coins between TON Network and Ethereum Network.

It is required to run ETH-TON bridge on the mainnet. Given that bridge is an important part of the network economy, this needs to be done in several steps with sufficient testing.

Starting point

The bridge smart contract is developed (func, solidity) and documented. Test version (TON Testnet - Ethereum Ropsten) launched.

Network config -71 and 71 (config of bridge) is not installed on the mainnet.

Roadmap

Initial oracle set and stakes

• Bridge smart contract is being deployed
  Source-code - https://github.com/newton-blockchain/bridge-func/blob/master/func/bridge_code.fc
  Address - https://ton.sh/address/Ef_dJMSh8riPi3BTUTtcxsWjG8RLKnLctNjAM4rw8NN-xWdr

• Bridge collector smart contract is being deployed
  Source-code - https://github.com/newton-blockchain/bridge-func/blob/master/func/votes-collector.fc
  Address - https://ton.sh/address/EQCuzvIOXLjH2tv35gY4tzhIvXCqZWDuK9kUhFGXKLImgxT5

• The initial oracle set consists of 9 oracles. First 9 oracles should be selected from the main developers of the open-source TON community and validators who validate the network for at least six months without violations.

• Each oracle must put stake in the amount of 100 000 TON coins on a special bridge governance smart contract
  Source-code - https://github.com/newton-blockchain/bridge-func/blob/master/func/multisig-code.fc
  Address - https://ton.sh/address/kf8rV4RD7BD-j_C-Xsu8FBO9BOOOwISjNPbBC8tcq688Gcmk

• n should be 9 and k should be 6 which means that any transfer will require confirmation from at least six oracles

• get_lock_timeout of bridge governance smart contract must lock oracle stakes for a time sufficient to vote for config -71

Validators vote for the bridge config

• Validators study the governing, bridge and collector smart contracts and make sure that the code, parameters and balance are correct

• Validators examine the -71 config proposal and make sure that its data is correct and contains the same list of oracles and smart-contracts addresses

• Validators vote for config -71 (as described in https://ton.org/docs/#/howto/config-params)

The bridge starts to work

• After the config -71 is installed in the network, the Ethereum part of the bridge is deployed with the same oracles set
  Source-code https://github.com/newton-blockchain/bridge-solidity

• Bridge starts its work

Finalization

• Validators update their software to last commit of https://github.com/newton-blockchain/ton (must be commit 0d246dd or later). Validators are required to update before voting otherwise there will be network problems

• Validators examine the 71 config proposal and make sure that its data is correct and contains the valid list of oracles, valid TON bridge addresses and valid Ethereum address of bridge

• Validators vote for config 71 (as described in https://ton.org/docs/#/howto/config-params)