[go: up one dir, main page]
Closed
Milestone Jan 23, 2025–Mar 19, 2025

Tezlink: empty Tezos blocks

Context

The goal of this milestone is to bootstrap the work on Tezos compatibility in Tezlink by building the infrastructure on which we will iterate in the next milestones. The focus is on turning the (multichain) EVM node into a generic L2 node which can handle both Ethereum and Tezos RPC calls depending on the chain family of the targeted L2 chain.

In order to keep the current rollup tests passing, the RPC server of the Michelson chain family will start as a clone of the EVM one from which the JSON RPCs will be progressively replaced by Tezos ones. The goal of this milestone is to have one such RPC replaced.

Work breakdown

Configuration

When executing the kernel, we want the following logic:

  • first read the feature flag from durable storage,
  • if it's enabled then:
    • for each chain_id from /evm/chain_ids read the chain_family and the chain config from /evm/chain_configurations/<chain_id>,
  • else:
    • read the chain_id from /evm/chain_id and the chain config from /evm.

In the L2 node however, which chain_id the node follows is not an information which comes from the durable storage so we want something like:

  • read the list of chain ids and the mode from the config file,
  • read the feature flag from durable storage,
  • if it's enabled then:
    • in sequencer mode:
      • check that the list of chain ids is identical to the one stored in /evm/chain_ids
      • launch restricted RPC server
    • in non-sequencer mode:
      • check that the list of chain ids from config is a singleton,
      • get the chain family for this chain_id,
      • launch RPC server for this family
  • else:
    • check that the "l2_chains" experimental feature is disabled
    • check that /evm/chain_id has the expected chain_id
    • launch an RPC server for the EVM family.

L2 node (formerly known as EVM node)

Renaming

  • The octez-evm-node binary is renamed into octez-l2-node. To avoid breaking existing scripts, the old name is kept and links to the new one. @rafoo_

Sequencer

The notion of chain family does not make sense in the case of the sequencer because the sequencer will eventually have to run both chains. When the multichain feature flag is enabled, we want the sequencer to only answer to very few RPCs but we can run L2 nodes in RPC mode to provide a RPC view of a specific chain family (on a specific chain).

First Tezos RPCs

Initially, the RPC service will be the same for EVM and Michelson. As the project progresses, JSON RPCs will be dropped in favor of native tezos RPCs for the Michelson family. The goal of this milestone is do complete this replacement for one RPC: eth_blockNumber replaced by /chain/main/blocks/head/context/helpers/current_level.

Kernel