Taiko Devs

After a lengthy period of testing on the Taiko Hekla testnet, we are excited to announce that Based Preconfirmations are coming soon to the Taiko Alethia Mainnet! In preparation for this upgrade, we strongly recommend that you upgrade your node software to the listed versions by August 11th UTC. If you fail to upgrade, you will not be able follow the chain in real time as blocks are preconfed, but you will still be able to sync once they are proposed to the L1. This upgrade requires some configuration changes, which will be outlined in this guide on the docs site: - docs.taiko.xyz/guides/node-op… With this upgrade, it will unfortunately mean that community proposers will no longer be able to arbitrarily propose blocks. Since we are starting in starting in the Whitelisted Preconfirmations stage, only our partnered whitelisted preconfirmers will be able to propose. However, if you wish to continue operating a L2 node and stay connected to the chain, please update to the following software versions. You may continue to run a prover, but will only be able to prove unassigned blocks: please have PROVE_UNASSIGNED_BLOCKS=true set in your .env if you plan to do so. If you previously ran a prover, your previous prover config will still function. Mandatory update for Taiko Alethia Node operators: - taiko-geth v1.17.0 - taiko-alethia-client v1.9.0 - simple-taiko-node v1.18.0 Read more about the Based Preconfirmations stages here: - #what-are-based-preconfirmations" target="_blank" rel="nofollow noopener">docs.taiko.xyz/taiko-alethia-…

Attention all Taiko Alethia Node Runners! We’ve released a client hotfix for mainnet to address some stability issues that we’ve encountered since the last upgrade. We highly recommend all node operators upgrade their client versions to taiko-alethia-client-v2.3.0 for the smoothest experience possible! Update to stay connected: taiko-alethia-client v2.3.0 simple-taiko-node v2.2.2 You can find the client release notes here: github.com/taikoxyz/taiko…

Attention all Taiko Alethia Node Runners! After a lengthy period of testing on our testnet, we are excited to announce that the Shasta fork is coming to Taiko Alethia! Shasta is a complete redesign of the Taiko core protocol with two objectives: simplicity, and efficiency. Benchmarks have already shown more than a 20x reduction in gas fees when proposing and an 8x reduction in proving compared to Pacaya! This upgrade also advances Taiko toward Stage 1 classification; read more about the specifics here: @taiko-labs/achieving-stage-1-shasta-is-almost-here" target="_blank" rel="nofollow noopener">paragraph.com/@taiko-labs/ac… The Shasta fork is rolling out to Taiko Alethia on 2026-04-02 13:15:00 UTC at timestamp 1_775_135_700. All Taiko Alethia node operators must update their node to the following software versions before this time to stay connected. Please note that the client has breaking command-line flag changes documented in the v2.2.0 client release notes. Breaking Command-Line Flags Changes: Renamed Flags: --taikoInbox has been renamed to --pacayaInbox. For mainnet, the value is 0x06a9Ab27c7e2255df1815E6CC0168d7755Feb19a. New Driver Flags: --shastaInbox: Required config. Inbox contract address for the Shasta protocol. For mainnet, the value is 0x6f21C543a4aF5189eBdb0723827577e1EF57ef1f. --shasta.time: Required config. Shasta hardfork activation timestamp (Unix seconds). For mainnet, the value is 1775135700. Software Versions: taiko-alethia-client: taiko-alethia-client-v2.2.0 taiko-geth: v2.4.0 simple-taiko-node: v2.2.0

Attention all Taiko Hoodi Node Runners! We are excited to announce that the Shasta fork is coming to Taiko Hoodi! Shasta is a complete redesign of the Taiko core protocol with two objectives: simplicity, and efficiency. Preliminary benchmarks have already shown more than a 20x reduction in gas fees when proposing and an 8x reduction in proving compared to Pacaya! This upgrade also advances Taiko toward Stage 1 classification, and establishes the foundation for permissionless preconfirmations; read more about the specifics here: @taiko-labs/achieving-stage-1-shasta-is-almost-here" target="_blank" rel="nofollow noopener">paragraph.com/@taiko-labs/ac… The Shasta fork is rolling out to Taiko Hoodi on Feb 5, 2026, 01:00 PM (UTC) at timestamp 1_770_296_400. All Taiko Hoodi node operators must update their node to the following software versions before this time to stay connected. Please note that the client has breaking command-line flag changes documented in the v2.1.1 release notes: github.com/taikoxyz/taiko… Software Versions: - taiko-alethia-client: taiko-alethia-client-v2.1.1 - taiko-geth: v2.2.1 - simple-taiko-node: v2.1.0

Attention all Taiko Alethia and Taiko Hoodi Node Runners! We’ve released an execution client hotfix for both networks that contains upstream security fixes that address p2p vulnerabilities from go-ethereum v1.16.8. We highly recommend all node operators upgrade their client versions to taiko-geth-v1.17.4 for the smoothest experience possible! Update to stay connected: - taiko-geth: v1.17.4 - simple-taiko-node: v1.23.0

We've identified and fixed a bug in TaikoInbox that could have corrupted batch verification tracking. The issue caused the system to incorrectly mark transitions as verified when they hadn't passed all checks yet. No user funds were at risk, but this could have affected chain state integrity. The fix ensures verification status is only updated after all checks pass. Patch is live. More information here: dao.taiko.xyz/plugins/commun…

Attention all Taiko Alethia Node Runners! The Fusaka upgrade is rolling out to Ethereum on December 3, 2025, at 21:49:11 UTC. With this upgrade comes EIP-7594, which introduces data sampling instead of full downloads; this means that if you are not running an Ethereum semi-supernode or supernode beacon client, your L2 node will not function as intended. Please configure your beacon client with the respective flags (detailed below) before the Fusaka hard fork date to avoid interruptions. - Lighthouse: --semi-supernode or --supernode - Teku: --p2p-subscribe-all-custody-subnets-enabled - Grandine: --subscribe-all-data-column-subnets - Lodestar: --supernode - Nimbus: --debug-peerdas-supernode Alternatively, you may set a --blob.server url if you wish to use a a thirdparty or self hosted blob indexer service. This can be done with BLOB_SERVER_URL in simple-taiko-node's .env. We’ve also released some mandatory upgrades to taiko-client and taiko-geth. If you are running an L2 node, please upgrade to the following versions as soon as possible: Software Versions: - taiko-alethia-client v1.11.0 - taiko-geth v1.17.3 - simple-taiko-node v1.22.0

⚠️Attention all Taiko Hoodi Node Runners! The Fusaka upgrade is rolling out to Ethereum Hoodi October 28, 2025, at slot 1,622,016. With this upgrade comes EIP-7594, which introduces data sampling instead of full downloads; this means that if you are not running an Etherum Hoodi semi-supernode or supernode beacon client, you L2 node may experience blob unavailability or chain divergence. Please configure your beacon client with the respective flags (detailed below) before the Fusaka hard fork date to avoid interruptions! Lighthouse: --semi-supernode or --supernode Teku: --p2p-subscribe-all-custody-subnets-enabled Grandine: --subscribe-all-data-column-subnets Lodestar: --supernode Nimbus: --debug-peerdas-supernode Alternatively, you may set a --blob.server url if you wish to use a a thirdparty or self hosted blob indexer service. This can be done with $BLOB_SERVER_URL in simple-taiko-node's .env.

Attention all Taiko Hoodi Node Runners! We’ve recently reset the Taiko Hoodi network due to a chain ID conflict causing issues for the network’s functionality. As a result, we’ve switched the chain ID from 167012 to 167013, and the chain is fully online and functional now. This switch requires some chain config changes in our client and execution engine; if you are running a node please swap to the versions listed below! Updated versions: simple-taiko-node v1.21.0 taiko-geth:sha-73d4688 taiko-alethia-client:sha-153e66e Find the release notes for simple-taiko-node here: github.com/taikoxyz/simpl…

Attention builders: our Hoodi Testnet is back online The new Hoodi Testnet is now open to everyone who wants to build, experiment, and test their ideas. Whether you’re deploying your first contract or pushing the limits of scalability, it’s the perfect place to start building. See our updated blog post for all the details: taiko.mirror.xyz/bmdcp5YfzInHvZ…

Important: Our Hoodi testnet will shut down this Monday. A new testnet will be made available later on, and we’ll reveal more information soon. We apologize for the inconvenience.

⚠️Taiko Hoodi Launch and Taiko Hekla Sunset Taiko Hekla, our current testnet based on Ethereum’s Holesky testnet, will sunset September 30, 2025 as Holesky will also be deprecated. In its place, we are launching Taiko Hoodi, which is already live as of September 25, 2025. Please make the necessary adjustments before the sunset date. For all the details: taiko.mirror.xyz/bmdcp5YfzInHvZ…

Attention all Taiko Alethia Node Runners! We’ve released a client hotfix for Taiko Alethia Mainnet and Taiko Hekla Testnet with some new optimizations to the client's performance. We highly recommend all node operators upgrade their client versions to taiko-alethia-client-v1.10.1 for the smoothest experience possible! Update versions: - taiko-alethia-client v1.10.1 - simple-taiko-node v1.19.0 You can find the client release notes here: github.com/taikoxyz/taiko…

Attention all Taiko Alethia Node Runners! We’ve released a client hotfix for Taiko Alethia Mainnet and Taiko Hekla Testnet to address some issues that we’ve encountered since the last upgrade. We highly recommend all node operators upgrade their client versions to taiko-alethia-client-v1.10.0 for the smoothest experience possible! Update to stay connected: - taiko-alethia-client v1.10.0 - simple-taiko-node v1.18.1 You can find the client release notes here: github.com/taikoxyz/taiko…

Attention all Taiko Hekla Node Runners! After a period of stress testing Based Preconfirmations on the Hekla network, we’ve come out with a new and improved client that addresses some reorg problems and more! This image contains non-backwards compatible changes to the p2p gossiping, so failure to update will mean your node will only update when an event is processed on chain. To successfully rejoin the p2p network, updating is mandatory, so all Taiko Hekla node operators MUST update their node to the below instances ASAP! Mandatory update to stay connected: taiko-alethia-client v1.7.0 taiko-geth v1.17.0 simple-taiko-node v1.17.4 You can find the client release notes here: github.com/taikoxyz/taiko…

Attention all Taiko Alethia Node Runners! We’ve released a client hotfix for mainnet to address several production issues that we’ve encountered since the last upgrade, as well as introduce better logging to help with debugging issues moving forward. We highly recommend all node operators upgrade their client versions to taiko-alethia-client-v1.5.2 for the smoothest experience possible! Update to stay connected: - taiko-alethia-client v1.5.2 - simple-taiko-node v1.17.3 You can find the client release notes here: github.com/taikoxyz/taiko…

Based Preconfirmations are coming to Taiko Hekla! Current proposers will be unable to propose as we transition to whitelisted preconfirmers only, but if you wish to remain a node operator please update your software versions! You may continue to run a prover, but will only be able to prove unassigned blocks: please have PROVE_UNASSIGNED_BLOCKS=true set in your .env if you plan to do so. All Hekla node operators must update their software to the new versions before June 10th UTC or risk being disconnected from the chain. taiko-geth v1.16.0 taiko-alethia-client v1.6.2 simple-taiko-node v1.17.2 raiko v1.9.0-rc.1 Read more about Stage 1 Preconfirmations here! #what-are-based-preconfirmations" target="_blank" rel="nofollow noopener">docs.taiko.xyz/taiko-alethia-…

We have just released a critical hotfix for the Taiko-Geth mainnet software. All mainnet operators must upgrade to the latest version: taiko-geth:v1.15.1-hotfix We apologize for any inconvenience this may cause and appreciate your prompt attention to this update. Thank you for your cooperation!