Skip to main content

Enable a proposer

This guide will help you enable your Taiko node as a proposer.

Prerequisites

You have already setup a node (see: Run a node)

Grimsvotn L2 :

  • Must have a balance of ETH and TTKO on Sepolia L1 (see: Receive tokens).

Eldfell L3 :

  • Must have a balance of ETH and TTKOe on Grimsvotn L2 (see: Receive tokens).

Steps

Visit the TaikoL1 contract on block explorer

First, you need to visit the TaikoL1 proxy contract:

  • If you are depositing TTKO, you can visit it here.
  • If you are depositing TTKOe, you can visit it here.

Click the write proxy tab

Then, visit the "Write proxy" (Blockscout) or "Write as proxy" (Etherscan) tab.

Click the wallet connect button on the explorer.

Enter deposit amount

Click the text field for depositTaikoToken and enter the amount of TTKO or TTKOe you would like to deposit followed by 8 zeroes.

info

Make sure to click the plus sign and click 10^8 decimals to add 8 zeroes, or add 8 zeroes manually.

For example if you want to deposit 81 TTKO/TTKOe, you would enter 8100000000.

Deposit your TTKO/TTKOe

Click Write and confirm the transaction in your wallet.

Open .env file in simple-taiko-node

Open the .env file in the simple-taiko-node directory.

Set environment variables to enable a proposer

caution

Do not use a private key that is valuable to you. The private key will be stored in plain text in the .env file, and this is not secure. There is a real risk of losing your assets. You should only use a test account.

Set the following environment variables to enable your node as a proposer:

  • Set ENABLE_PROPOSER to true (replacing the default false with true).
  • Set L1_PROPOSER_PRIVATE_KEY to that of your wallet's private key; it will need some TTKO/TTKOe on Sepolia/Grimsvotn to propose blocks (if using MetaMask, follow these directions to retrieve the private key).
  • Set L2_SUGGESTED_FEE_RECIPIENT to the recipient of L2/L3 ETH rewards.

Verify proposer logs

You should see a log if you have proposed a block: 📝 Propose transactions succeeded.

If you are running a node in the background, you can view the logs with docker compose logs -f.