Stats
Actions
Tags
From taiko
Set up, run, and manage Taiko nodes on Hoodi testnet or mainnet using Docker or from source. Use when "run node", "node operator", "simple-taiko-node", "taiko-geth", "taiko-client", or "sync" is mentioned.
How this skill is triggered — by the user, by Claude, or both
Slash command
/taiko:taiko-nodeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run Taiko nodes. A node = `taiko-geth` (execution) + `taiko-client` (consensus).
Run Taiko nodes. A node = taiko-geth (execution) + taiko-client (consensus).
Network Selection: Always ask which network if user hasn't specified "hoodi" or "mainnet".
| Task | Resource |
|---|---|
| Network config, chain IDs, RPCs | Networks Reference |
| Run node (Docker, recommended) | Docker setup |
| Build from source | Source build |
| Run Ethereum Hoodi L1 | eth-docker |
| Debug issues | Troubleshooting |
^24.0, git ^2 (source: also Go ^1.21, make ^4)git clone https://github.com/taikoxyz/simple-taiko-node.git && cd simple-taiko-node
cp .env.sample .env # mainnet (.env.sample.hoodi for testnet)
# Edit .env: set L1_ENDPOINT_WS, L1_BEACON_HTTP, COMPOSE_PROFILES
docker compose up -d # mainnet
docker compose -f docker-compose-hoodi.yml up -d # testnet
L1 endpoints: Use host.docker.internal or machine's private IP, not 127.0.0.1.
Use taiko --json for structured output:
taiko node status --json # health: block, peers, sync %, L1 anchor
taiko node logs --service taiko_client_driver --tail 50 # taiko-client logs
taiko node logs --service l2_execution_engine --tail 50 # taiko-geth logs
taiko node restart --json # restart with structured confirmation
All commands return: { schema_version, command, status, network, data, errors, warnings, metrics }
npx claudepluginhub taikoxyz/taiko-ai --plugin taiko-x402Installs and runs Lightning Terminal (litd) — a Docker bundle of lnd, loop, pool, tapd, and faraday. Supports watch-only with remote signer, standalone mode, and regtest. Use for Lightning payments, channel/liquidity management, or taproot assets.
This skill should be used when the user asks about the Midnight local development network, including "start the devnet", "stop the devnet", "restart the network", "local development network", "midnight node", "midnight indexer", "network status", "network health", "devnet config", "network endpoints", "port 9944", "port 8088", "port 6300", "Docker Compose", "devnet not starting", "local blockchain", "devnet logs", "network ID", "generate devnet", "devnet versions", "update devnet", "devnet stale", "proof server", "devnet volumes", "clean slate", "docker containers", "devnet compose file", "devnet endpoints"
Tracks Ethereum protocol evolution, EIP lifecycle, fork schedules via forkcast.org and EIPs repo. Use for checking feature status, upcoming changes, or proposing EIPs.