Skip to content

Latest commit

 

History

History
96 lines (63 loc) · 4.68 KB

sequencer.md

File metadata and controls

96 lines (63 loc) · 4.68 KB

ethrex L2 Sequencer

ToC

Components

The L2 Proposer is composed of the following components:

Block Producer

Creates Blocks with a connection to the auth.rpc port.

L1 Watcher

This component handles the L1->L2 messages. Without rest, it is always watching the L1 for new deposit events defined as DepositInitiated() that contain the deposit transaction to be executed on the L2. Once a new deposit event is detected, it will insert the deposit transaction into the L2.

In the future, it will also be watching for other L1->L2 messages.

L1 Transaction Sender (a.k.a. L1 Committer)

As the name suggests, this component sends transactions to the L1. But not any transaction, only commit and verify transactions.

Commit transactions are sent when the Proposer wants to commit to a new block. These transactions contain the block data to be committed in the L1.

Verify transactions are sent by the Proposer after the prover has successfully generated a proof of block execution to verify it. These transactions contain the proof to be verified in the L1.

Prover Server

The Prover Server is a simple TCP server that manages communication with a component called the Prover Client. The Prover Client acts as a simple TCP client, handling incoming requests to prove a block. It then "calls" a zkVM, generates the Groth16 proof, and sends it back to the Server. In this setup, the state is managed solely by the Prover Server, which, in theory, makes it less error-prone than the zkVMs.

For more information about the Prover Server, the Prover Docs provides more insight.

Configuration

Configuration is done through environment variables. The easiest way to configure the Sequencer is by creating a sequencer_config.toml file and setting the variables there. Then, at start, it will read the file and set the variables.

Note

The deployer.rs is in charge of parsing the .toml and creating/updating the .env If you don't deploy files, the .toml will not be parsed.

The following environment variables are available to configure the Proposer consider looking at the provided sequencer_config_example.toml:

  • Under the [deployer] section:

    • l1_address: L1 account which will deploy the common bridge contracts in L1.
    • l1_private key: Its private key.
    • pico_contract_verifier: Address which will verify the pico proofs.
    • pico_deploy_verifier: Whether to deploy the pico verifier contract or not.
    • risc0_contract_verifier: Address which will verify the risc0 proofs.
    • sp1_contract_verifier: Address which will verify the sp1 proofs.
    • sp1_deploy_verifier: Whether to deploy the sp1 verifier contract or not.
    • salt_is_zero: Whether a 0 value salt will be used. Keep as true for deterministic create2 operations.

  • Under the [watcher] section:

    • bridge_address: Address of the bridge contract on L1.
    • check_interval_ms: Interval in milliseconds to check for new events.
    • max_block_step: Maximum number of blocks to look for when checking for new events.
    • l2_proposer_private_key: Private key of the L2 proposer.

  • Under the [proposer] section:

    • interval_ms: Interval in milliseconds to produce new blocks for the proposer.
    • coinbase address: Address which will receive the execution fees.

  • Under the [committer] section:

    • l1_address: Address of the L1 committer.
    • l1_private_key: Its private key.
    • commit_time_ms: Sleep time after sending the commit transaction.
    • on_chain_proposer_address: Address of the on-chain committer.

  • Under the [prover_server] section:

    • l1_address: Address of the account that sends verify transaction to L1.
      • Must be different than the committer.l1_address, there might be conflicts with the transactions' nonce.
    • l1_private_key: Its private key.
    • listen_ip: IP to listen for proof data requests.
    • listen_port: Port to listen for proof data requests.
    • dev_mode: Whether dev_mode is activated or not.

If you want to use a different configuration file, you can set the:

  • CONFIGS_PATH: The path where the SEQUENCER_CONFIG_FILE is located at.
  • SEQUENCER_CONFIG_FILE: The .toml that contains the config for the sequencer.