Enable a prover

Prerequisites

• You are already running a Taiko node with Docker or from source.
• You have an SGX v2 capable machine.

Enable a prover with simple-taiko-node

Note

These are the bare minimum required settings along with a functional Taiko node to run a prover, feel free to customize the rest of the variables in the .env file as you see fit!

1. A Taiko prover needs to be able to generate SGX proofs at the moment. To do that, you need to run raiko. Please follow the Docker setup guide here.

2. After successfully setting up raiko, set the SGX_RAIKO_HOST endpoint in your .env file.

3. Set the L1_PROVER_PRIVATE_KEY to an L1 account’s private key which will send the Prove Block transactions.

4. Finally set ENABLE_PROVER to true in simple-taiko-node .env.

5. Set COMPOSE_PROFILES=prover or add prover to the list.

6. You can then run your prover with docker compose up -d!

Note

For Step 6, please use docker compose -f docker-compose-hekla.yml up -d if you are running on Taiko Hekla, and docker compose -f docker-compose-hoodi.yml up -d if you are running on Taiko Hoodi.

Please find all relevant bond, cooldown, and proving window information here.

Approve TaikoInbox as TAIKO spender (Taiko Alethia)

1. Approve the TaikoInbox contract as a spender.

   Visit the TAIKO contract on Ethereum here.

2. Click the Connect to Web3 button.

3. Click the approve function and set the spender address to the TaikoInbox contract address: 0x06a9Ab27c7e2255df1815E6CC0168d7755Feb19a.

   Note

   Please verify contract addresses are correct before moving forward. You can check the respective ENS domains on Etherscan.

4. Set the amount to at least the minimum bond amount of 125 TAIKO.

   You will need at least 125 TAIKO for the livenessBond. After entering 125, you need to set the 18 decimals that the TAIKO contract takes, you can click the plus button and then select 10^18.

   If you have bonded TAIKO in the TaikoInbox contract, it will be used first before more is taken from your allowance.

   For an explanation on bonds, please refer to the terminology section here.

5. Finally, click the Write button.

Approve TaikoInbox as TTKOh spender (Taiko Hekla)

You will need TTKOh deposited on the TaikoInbox contract to secure the bond for the proofs you generate.

1. Approve the TaikoInbox contract as a spender.

   Visit the TTKOh contract on Holesky here.

2. Click the Connect to Web3 button.

3. Click the approve function and set the spender address to the TaikoInbox contract address: 0x79C9109b764609df928d16fC4a91e9081F7e87DB.

4. Set the amount to at least the minimum bond amount of 125 TTKOh.

   You will need at least 125 TTKOh for the livenessBond. After entering 125, you need to set the 18 decimals that the TAIKO contract takes, you can click the plus button and then select 10^18.

   If you have bonded TTKOh in the TaikoInbox contract, it will be used first before more is taken from your allowance.

   For an explanation of the difference between these bonds, please refer to the terminology section here.

5. Finally, click the Write button.

Approve TaikoInbox as TTKOh spender (Taiko Hoodi)

You will need TTKOh deposited on the TaikoInbox contract to secure the bond for the proofs you generate.

1. Approve the TaikoInbox contract as a spender.

   Visit the TTKOh contract on Hoodi here.

2. Click the Connect to Web3 button.

3. Click the approve function and set the spender address to the TaikoInbox contract address: 0x50A576435E2D9c179124D657d804eb56A10b6999.

4. Set the amount to at least the minimum bond amount of 125 TTKOh.

   You will need at least 125 TTKOh for the livenessBond. After entering 125, you need to set the 18 decimals that the TAIKO contract takes, you can click the plus button and then select 10^18.

   If you have bonded TTKOh in the TaikoInbox contract, it will be used first before more is taken from your allowance.

   For an explanation of the difference between these bonds, please refer to the terminology section here.

5. Finally, click the Write button.

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!