Home

Deployment Guide

Requirements

Let's assume there are two Ethereum-like networks:

• N1: High-cost network (e.g. Ethereum mainnet)
• N2: Low-cost network (e.g. Kovan testnet, or any other Parity PoA network)

N2 authorities need to run their Validator nodes on machines that are capable of running two instances of the Parity Ethereum client at the same time.

Steps

1. Create Bridge configuration file: Documentation is available in README.md - example configuration file can be found in examples/config.toml
2. All N2 authorities need to have the following fields specified in their configuration file. (?)
3. An Authority account used to relay messages between two networks should be permanently unlocked for IPC access. (How?)
4. There needs to be a leading authority (one of N2 authorities) that runs the very first instance of the Bridge:
   • run bridge --config <config> --database <database> \ making sure that config path leads to the configuration file, and database path leads is empty
   • after you run it for the first time, database file should be created
   • database file may look like this

      home_contract_address = "0x49edf201c1e139282643d5e7c6fb0c7219ad1db7"
      foreign_contract_address = "0x49edf201c1e139282643d5e7c6fb0c7219ad1db8"
      home_deploy = 100
      foreign_deploy = 101
      checked_deposit_relay = 120
      checked_withdraw_relay = 121
      checked_withdraw_confirm = 121
     

   • copy it
5. When other authorities start Bridge software, they should run it with both config and database options set. Database options should point to the copied database file created by the leading authority. Note: It does not matter how much time is spent between steps 5 and 6.