Upgrade guide for v0.7.1

[fewensa]

We made changes to this version:

• All s2s bridges changed to use the new solution Refactor s2s bridge binary #544
• Refactor the e2e bridge ETH2 bridger refactor #538

If you already run any s2s bridges. you can upgrade to this version. this is optional. You can also choose not to upgrade. It will have no effect.

darwinia-ethereum

you should update your config.

Update general block

bridger/.maintain/config/bridge-darwinia-ethereum.toml

Lines 1 to 17 in 0f60fa2

	[general]
	# Whether to relay beacon headers from ethereum to darwinia
	header_ethereum_to_darwinia = true
	# Whether to relay sync commit from ethereum to darwinia
	sync_commit_ethereum_to_darwinia = true
	# Whether to relay execution layer state root from ethereum to darwinia
	execution_layer_ethereum_to_darwinia = true
	# Whether to sign the messages root and relay headers from darwinia to ethereum
	ecdsa_service = true
	# Whether to relay messages from ethereum to darwinia
	msg_ethereum_to_darwinia = true
	# Whether to relay messages from darwinia to ethereum
	msg_darwinia_to_ethereum = true
	# Max number of messages every delivery
	max_message_num_per_relaying = 15
	# Minimum seconds between two header relay
	header_relay_minimum_interval = 900

Chagne to

[general]
enable_beacon_header_relay = true
enable_sync_commit_relay = true
enable_execution_header_layer = true
enable_ecdsa_relay = true
enable_message_execution_to_evm = true
enable_message_evm_to_execution = true
max_message_num_per_relaying = 15
header_relay_minimum_interval = 900

old	new
header_ethereum_to_darwinia	enable_beacon_header_relay
sync_commit_ethereum_to_darwinia	enable_sync_commit_relay
execution_layer_ethereum_to_darwinia	enable_execution_header_layer
ecdsa_service	enable_ecdsa_relay
msg_ethereum_to_darwinia	enable_message_execution_to_evm
msg_darwinia_to_ethereum	enable_message_evm_to_execution

do not change the value of these keys when you upgrade.

Update index block

Change from

[index]
darwinia = { endpoint = "https://subql.darwinia.network/subql-bridger-darwinia/" }
darwinia_evm = { endpoint = "https://thegraph.darwinia.network/ethv2/subgraphs/name/bridge-darwinia" }

to

[index]
substrate_chain = { endpoint = "https://subql.darwinia.network/subql-bridger-darwinia/" }
evm_chain         = { endpoint = "https://thegraph.darwinia.network/ethv2/subgraphs/name/bridge-darwinia" }

Update ethereum block

Create new block as name [beacon]

[beacon]
# Beacon chain api endpoint and api supplier
endpoint                  = "http://unstable.mainnet.beacon-api.nimbus.team"
api_supplier              = "Nimbus"

Remove [ethereum].endpoint and rename [ethereum].execution_layer_endpoint to [ethereum].endpoint

Full config template please visit

bridge-darwinia-ethereum.toml

[furoxr]

For Darwinia<>Ethereum

Update contract address in the config:

[darwinia_evm]
contract_address = "0xD2A37C4523542F2dFD7Cb792D2aeAd5c61C1bAAE"
execution_layer_contract_address = "0xeC3c9B4d3674B3D03fdf20b082A3C2c669075990"

And there are three beacon api supplier could be used by bridger:

Nimbus:

• http://unstable.mainnet.beacon-api.nimbus.team
• https://www.lightclientdata.org

Lodestar:

• https://lodestar-mainnet.chainsafe.io/

[hackfisher]

10|v2  | 2022-11-29 05:30:58  INFO relay-e2e: [Darwinia][ECDSA][collectingMessages] Track scan block: 11336650
10|v2  | 2022-11-29 05:30:58  WARN tracker: The track key [scan.darwinia.collected-message.running] isn't running (value is not `true`), wait 3 seconds check again.
10|v2  | 2022-11-29 05:31:01  WARN tracker: The track key [scan.darwinia.collected-authorities.running] isn't running (value is not `true`), wait 3 seconds check again.
10|v2  | 2022-11-29 05:31:01  WARN tracker: The track key [scan.darwinia.collected-message.running] isn't running (value is not `true`), wait 3 seconds check again.
10|v2  | 2022-11-29 05:31:04  WARN tracker: The track key [scan.darwinia.collected-authorities.running] isn't running (value is not `true`), wait 3 seconds check again.
10|v2  | 2022-11-29 05:31:04  WARN tracker: The track key [scan.darwinia.collected-message.running] isn't running (value is not `true`), wait 3 seconds check again.
10|v2  | 2022-11-29 05:31:07  WARN tracker: The track key [scan.darwinia.collected-authorities.running] isn't running (value is not `true`), wait 3 seconds check again.
10|v2  | 2022-11-29 05:31:07  WARN tracker: The track key [scan.darwinia.collected-message.running] isn't running (value is not `true`), wait 3 seconds check again.