EVM Sequencer Support

[nicolasochem]

Attempt to move MIDL.dev etherlink observer nodes to tezos-k8s.

The values.yaml is

node_config_network:
  chain_name: ghostnet
snapshot_source: https://snapshots.tezos.marigold.dev/api/tezos-snapshots.json
images:
  octez: tezos/tezos:master_59da4165_20240521173856
smartRollupNodes:
  evm-0:
    operators:
      operating: baker-a
      cementing: baker-a
      executing_outbox: baker-a
      batching: baker-a
    rollup_address: sr18wx6ezkeRjt1SZSeZ2UQzQN3Uc3YLMLqg
    snapshot_url: https://snapshots.us.tzinit.org/etherlink-ghostnet/eth-ghostnet.snapshot
    node_rpc_url: http://rolling-node-0.rolling-node:8732
    evm_proxy:
      ingress:
        enabled: false
accounts:
  baker-a:
    key: edsk4QYG9HjNycJQcPmWWuhjTpDEFBEdPq6Kc4kwYBAyCFSNEMWybz
    is_bootstrap_baker_account: true
    bootstrap_balance: '4000000000000'

[nicolasochem]

On latest weeklynet, proto alpha, I'm seeing the following error from sequencer, after successful data import from rollup node:

│ + '[' '!' -e /var/tezos/sequencer/store/store.1.mapping ]                                                                            │
│ + CMD='/usr/local/bin/octez-evm-node run sequencer   with endpoint http://127.0.0.1:8932   signing with edsk3xxx │
│ LKP8XyMhy4c6PQGr7qQKTYa8rX   --data-dir /var/tezos/sequencer   --time-between-blocks 6   --rpc-addr 0.0.0.0'                         │
│ + exec /usr/local/bin/octez-evm-node run sequencer with endpoint http://127.0.0.1:8932 signing with edskxxxxxx │
│ XyMhy4c6PQGr7qQKTYa8rX --data-dir /var/tezos/sequencer --time-between-blocks 6 --rpc-addr 0.0.0.0                                    │
│ Feb 15 18:28:34.532: starting the EVM node (sequencer)                                                                               │
│ Fatal error: exception Json_encoding.Unexpected_field("current_block_hash")                                                          │
│ Raised at Json_encoding.Make.destruct.(fun) in file "src/json_encoding.ml", line 421, characters 48-79                               │
│ Called from Json_encoding.Make.destruct.(fun) in file "src/json_encoding.ml", line 355, characters 42-73                             │
│ Called from Evm_node_lib_prod__Evm_context.load_metadata in file "etherlink/bin_node/lib_prod/evm_context.ml", line 48, characters 6 │
│ -59                                                                                                                                  │
│ Called from Lwt.Sequential_composition.bind.create_result_promise_and_callback_if_deferred.callback in file "src/core/lwt.ml", line  │
│ 1844, characters 16-19                                                                                                               │
│ Re-raised at Lwt.Miscellaneous.poll in file "src/core/lwt.ml", line 3123, characters 20-29                                           │
│ Called from Lwt_main.run.run_loop in file "src/unix/lwt_main.ml", line 27, characters 10-20                                          │
│ Called from Lwt_main.run in file "src/unix/lwt_main.ml", line 106, characters 8-13                                                   │
│ Re-raised at Lwt_main.run in file "src/unix/lwt_main.ml", line 112, characters 4-13                                                  │
│ Called from Dune__exe__Main in file "etherlink/bin_node/main.ml", line 1033, characters 2-38   

This seems to be coming from metadata file in the sequencer data dir:

~ $ cat /var/tezos/sequencer/metadata 
{ "checkpoint": "CoVZdHuwgZXbWopSV22d4qXkHCndqEuG5eJwPgMG32fvyb6toH8s",
  "next_blueprint_number": "0x5",
  "current_block_hash":
    "0x519844fca5857977f9b6f5755c6c801d2588e2b57deb92cdc8df40f77b4a4930" }

@drchrispinnock have you seen this?