Run a Taiko node
This guide will help you start up a Taiko RPC node using simple-taiko-node.
- Docker is installed and running.
- Git is installed.
- If using Windows, you should install Git BASH or WSL to use as your terminal.
- Meet the Geth minimum hardware requirements except for the storage requirement because Taiko nodes will require less storage (at the time of writing).
Run a Taiko node with
Visit stn which has a simple copy-paste command to install
2. Install a Taiko node
3. Config the Taiko node as a full node
4. Start the Taiko node
5. Verify the Taiko node is running and properly synced
To view the sync status you can execute:
You can also view the dashboard with:
Run a Taiko node with simple-taiko-node
1. Clone simple-taiko-node
2. Copy the sample .env files
3. Set the L1 archive node endpoint
First, open the
.env in your preferred text editor:
Next, you will set the L1 archive node endpoints. If you are running a local Holesky node, you cannot reference the L1 endpoints as
ws://127.0.0.1:8546 because that is local to inside the simple-taiko-node Docker networking. Instead you can try:
host.docker.internal(see: stack overflow).
- Using the private ip address of your machine (use something like
ip addr showto get this ip address).
After getting the address of the Holesky archive node, set the following L1 node endpoints in your
.env file. Here is an example:
4. Remove old testnet volumes
If you ran a testnet node previously, make sure to first remove the old volumes:
5. Start the node
Make sure Docker is running and then run the following command to start the node (you may need to use
sudo docker compose up -d if your user is not in the
6. Verify node is running
Option 1: Check with the node dashboard
A node dashboard will be running on
localhost on the
GRAFANA_PORT you set in your
.env file, which defaults to
You can verify that your node is syncing by checking that the chain head on the dashboard is increasing. Once the chain head matches what’s on the block explorer, you are fully synced.
Option 2: Check with curl commands
- Check if the Execution Layer client is connected to Taiko L2:
which should return the chainId as
- Check if the Execution Layer client is synced by requesting the latest Taiko L2 / L3 block from the Execution Layer client:
- If the blockNumber response value is
0or not growing, check the Taiko L2 logs here:
Note: You may need to use
sudo docker compose logs -fif you are not in the
See the video tutorial Run a Taiko L2 node (YouTube). It’s for a previous testnet but the overall steps are the same!
Full simple-taiko-node CLI reference
Start and remove orphan containers
This command will start and remove containers that are not part of the current docker compose file.
View grafana dashboard
View all logs
View execution logs
View client driver logs
View client proposer logs
View system resource usage stats
Compare .env and .env.sample
- Visit the Discord for help on any common error codes / issues.
- View the logs of the node (see above).