Enable a proposer

Danger

Do NOT start up your proposer without setting up a prover first with a fully synced node. You WILL lose your tokens and there is no way to recover them without proving the proposed block.

Prerequisites

• You are already running a Taiko node with Docker or from source.
• You have set up a prover or configured a ProverSet with a third-party partner.

Using simple-taiko-node

Caution

You can choose to either use a ProverSet, or leave the PROVER_SET variable blank. If you leave it blank, you will eventually run into some nonce issues as the proposer and prover will be using the same address. This may be sufficient for testing, but for a longer term proposer / prover setup, we recommend utilizing a ProverSet.

1. First, you will need to set up a prover.

2. If you are using a ProverSet, set the ProverSet contract address in the PROVER_SET env variable from the previous guide. Otherwise, leave it blank.

3. Next, set the L1_PROPOSER_PRIVATE_KEY to an L1 account’s private key which will send the Propose Block transactions. If you are not using a ProverSet, this must be the same private key as your prover.

4. Then, set the L2_SUGGESTED_FEE_RECIPIENT to an L2 account’s public key that will receive the fee.

5. Finally set ENABLE_PROPOSER to true in simple-taiko-node .env.

6. Set COMPOSE_PROFILES=proposer or add proposer to the list.

7. Now that the proposer is configured properly, you can run it with docker compose up -d! Please use docker compose -f docker-compose-hekla.yml up -d if you are running on Hekla.

Troubleshooting

If you run into any problems, please visit the node troubleshooting page for help. If you run into an error that isn’t yet listed, please reach out in our Discord!