Fix for e2e setup

[yrong]

No description provided.

[claravanstaden]

Works for me! There was a problem with geth but --state.scheme=hash fixes it, thanks!

I did notice that the beacon relayer restarts with write to parachain: parachain write status was dropped, invalid, usurped or finality timed out, but when I look at Polkadot JS, the beacon headers are imported. I wonder if it is a problem with the Go substrate client. Did you see the same thing?

[yrong]

Did you see the same thing?

Yeah, same issue from my side. Still investigating and guess something related to the fast slot hack?

Updates:
Change the fast slot time from 1s to 6s and it work as expected but will slow the e2e setup. Or maybe we can increase the interval here.

snowbridge/relayer/relays/beacon/header/header.go

Line 76 in cff505d

ticker := time.NewTicker(time.Second * 10)

{"@timestamp":"2024-06-04T17:51:22.204227+08:00","blockRoot":"0xdfa79630efa7a41c10f4710a5870bc0b2f158ec0dd6fcebb77ec7398e3a1eab0","level":"info","message":"syncing finalized header from Ethereum beacon client","slot":288}
{"@timestamp":"2024-06-04T17:52:22.242619+08:00","block":"0x5afc53a57f2fe6984a26383add8706be1708f3b0971bfdbee3304fbb1dd2ab3e","extrinsic":"EthereumBeaconClient.submit","level":"debug","message":"extrinsic finalized"}
{"@timestamp":"2024-06-04T17:52:27.549197+08:00","blockRoot":"0x9900c996d25bd4a889871ae423f1325e762f0b903bfa88fddbbbd926026358d3","level":"info","message":"syncing finalized header from Ethereum beacon client","slot":320}
{"@timestamp":"2024-06-04T17:53:22.481526+08:00","block":"0xebe2c316785a757763163b0fc9658c356fbd18d811f099b5e89396dc8f2d72a5","extrinsic":"EthereumBeaconClient.submit","level":"debug","message":"extrinsic finalized"}
{"@timestamp":"2024-06-04T17:53:27.284686+08:00","blockRoot":"0xe9cece6b3831a0d4eb6b5a69c531a4561f469ad1d7377240654b6958a61e2e71","level":"info","message":"syncing finalized header from Ethereum beacon client","slot":352}
{"@timestamp":"2024-06-04T17:54:46.816956+08:00","block":"0xd873e3b04b0b6c8a168d9d54334486440757aa271eb595c6df70d40e5cac3e4d","extrinsic":"EthereumBeaconClient.submit","level":"debug","message":"extrinsic finalized"}
{"@timestamp":"2024-06-04T17:54:46.925848+08:00","blockRoot":"0x6f9b7b38e54d7174ce4122cac236c00a8385b958c2cdbf762164f2352779b5ff","level":"info","message":"syncing finalized header from Ethereum beacon client","slot":384}
{"@timestamp":"2024-06-04T17:55:22.967114+08:00","block":"0x5ea528923504fe7b7fa0bb5427018aa1edaf62b71aa4bd19b43e09d131d261bd","extrinsic":"EthereumBeaconClient.submit","level":"debug","message":"extrinsic finalized"}
...

Anyway, I'm not too worried about the issue seems it won't be a problem for production.

[vgeddes]

Looks great, 🚀

[claravanstaden]

Nice, thanks for looking into this!