Attention all taiko-geth Node Runners! We’ve released a mandatory execution engine upgrade for taiko-geth for both networks, containing a fix to the gas limit used during L2 block building. If you are currently running alethia-reth, no changes need to be made. Please update your nodes as soon as possible to prevent unexpected issues! We’d also like to take the opportunity to strongly recommend users switch to alethia-reth as per our previous announcement. Users may speed up their sync progress upon switching with our public L2 alethia-reth snapshots at snapshots.taiko.xyz. Update to stay connected: taiko-geth: v2.8.0 simple-taiko-node: v2.6.5

Attention all Taiko Node Runners! We've released a taiko-client update for Taiko Hoodi & Taiko Mainnet. It adds support for Ethereum's upcoming Glamsterdam upgrade: once Glamsterdam activates on the underlying L1, nodes on older taiko-client versions will stop syncing. Both mainnet and testnet operators must update: Taiko Hoodi: before Glamsterdam goes live on Ethereum Hoodi (currently targeted for Oct 26) Taiko Mainnet: before Glamsterdam goes live on Ethereum mainnet (date TBA) We recommend updating now. Also make sure your L1 execution & consensus clients run Glamsterdam-ready releases. Update to stay connected: taiko-alethia-client: taiko-alethia-client-v2.8.0 simple-taiko-node: v2.6.4 alethia-reth: no change (v1.4.1)

Attention all Taiko Node Runners! We’ve released an execution engine and client update for alethia-reth and taiko-client for Hoodi & Mainnet. This release contains updates for maintainability. Please update your nodes as soon as possible to prevent unexpected issues! Update to stay connected: alethia-reth: v1.4.1 taiko-alethia-client: taiko-alethia-client-v2.7.0 simple-taiko-node: v2.6.3

Attention all taiko-geth Node Runners! We’ve released a mandatory execution engine upgrade for taiko-geth for both networks containing consensus-sensitive fixes. If you are currently running alethia-reth, no changes need to be made. Please update your nodes as soon as possible to prevent unexpected issues! We’d also like to take the opportunity to strongly recommend users switch to alethia-reth as per our previous announcement. Users may speed up their sync progress upon switching with our new public L2 alethia-reth snapshots at snapshots.taiko.xyz. Update to stay connected: taiko-geth: v2.7.0 simple-taiko-node: v2.6.2

Attention all Taiko and Taiko Hoodi Node Runners! We’ve released a non-mandatory execution engine upgrade for both networks that which restores replay-style debug/trace RPCs and eth_estimateGas on Unzen networks. We recommend all node operators upgrade their execution engine versions to alethia-reth v1.3.1 for the smoothest experience possible! Update to stay connected: alethia-reth: v1.3.1 simple-taiko-node: v2.6.0

Attention Taiko Users! We will be sunsetting the following mainnet RPC endpoints within the next week: - rpc-2.mainnet.taiko.xyz - rpc-3.mainnet.taiko.xyz If you are currently using any of these endpoints, please update your configuration to rpc.mainnet.taiko.xyz as soon as possible to avoid any disruption to your node, app, or infrastructure connectivity.

Attention all Taiko Node Runners! We are excited to announce that the Unzen fork is coming to Taiko! Unzen is an upcoming fork that requires ZK proofs for every block, and introduces zk gas as a protocol-level budget for proving work and bumps the evm-version to support Osaka. Instead of limiting blocks only by ordinary EVM gas, Unzen adds a separate weighted gas metric that reflects how expensive different opcodes and precompiles are to prove; read more about the specifics here: docs.taiko.xyz/protocol/unze… Alongside this fork upgrade, we’re now strongly recommending users switch from taiko-geth to alethia-reth, our new high-performance Rust execution client built on top of Reth for the Taiko protocol! Users may speed up their sync progress upon switching with our new public L2 alethia-reth snapshots at snapshots.taiko.xyz/. Please note that the execution engine config will be different from taiko-geth; for a sample configuration please consult docker-compose.yml. The Unzen fork is rolling out to Taiko on 2026-08-06 13:00:00 UTC at timestamp 1786021200. All Taiko node operators must update their node to the following software versions before this time to stay connected. Please note that there are breaking command-line flag changes. Software Versions: - taiko-alethia-client: taiko-alethia-client-v2.6.0 - alethia-reth: v1.3.0 - simple-taiko-node: v2.5.0 Breaking Command-Line Flags Changes: Driver Flags --p2p.bootnodes: Please ensure your bootnodes config are up-to-date, 2.5.0 adds several bootnodes. They can directly be copied from start-driver.sh in simple-taiko-node. --inbox: Required config. Proxy for Inbox contract address for the Taiko protocol. 0x6f21C543a4aF5189eBdb0723827577e1EF57ef1f. --shastaInbox: deprecated. --shasta.time: deprecated. --pacayaInbox: deprecated. --preconfirmation.whitelist: deprecated. Execution Engine Flags --bootnodes: Please ensure your bootnodes config are up-to-date, 2.5.0 adds several bootnodes. They can directly be copied from .env.sample in simple-taiko-node Release notes can be found here: github.com/taikoxyz/simple-t…

Attention all Taiko Hoodi Node Runners! After further testing of the Unzen fork, we’ve released a required upgrade for the client on our testnet. We highly recommend all node operators upgrade their client versions for the smoothest experience possible! Update to stay connected: taiko-alethia-client: taiko-alethia-client-v2.5.0 simple-taiko-node: v2.3.2

Attention all Taiko Node Runners! We’ve released a client hotfix for mainnet to recover the chain post-hack. Please upgrade your client versions to taiko-alethia-client-v2.3.1 and sync fully. After syncing, please check whether your node’s block hash at height 8,110,008 is 0x358da783a0979fd6a128a79de24b0380d4f6fc90dfe390d120ea0ca938fb5b63. If it matches, your node is on the correct fork. If it does not, please resync from scratch; if the problem persists, please reach out to us via discord or telegram. Update to stay connected: taiko-alethia-client: taiko-alethia-client-v2.3.1 simple-taiko-node: v2.3.1

Attention all Taiko Hoodi Node Runners! We are excited to announce that the Unzen fork is coming to Taiko Hoodi! Unzen is an upcoming fork that introduces zk gas as a protocol-level budget for proving work and bumps the evm-version to support Osaka. Instead of limiting blocks only by ordinary EVM gas, Unzen adds a separate weighted gas metric that reflects how expensive different opcodes and precompiles are to prove; read more about the specifics here: docs.taiko.xyz/protocol/unze… Alongside this fork upgrade, we’re now strongly recommending users switch from taiko-geth to alethia-reth, our new high-performance Rust execution client built on top of Reth for the Taiko protocol! Users may speed up their sync progress upon switching with our new public L2 alethia-reth snapshots at snapshots.taiko.xyz/. Please note that the execution engine config will be different from taiko-geth; for a sample configuration please consult github.com/taikoxyz/simple-t…. The Unzen fork is rolling out to Taiko Hoodi on 2026-06-18 13:00:00 UTC at timestamp 1781787600. 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. Software Versions: taiko-alethia-client: taiko-alethia-client-v2.4.0 alethia-reth: v1.2.0 taiko-geth: v2.5.0 simple-taiko-node: v2.3.0 Breaking Command-Line Flags Changes: Driver Flags: --inbox: Required config. Inbox contract address for the Taiko protocol. 0xeF4bB7A442Bd68150A3aa61A6a097B86b91700BF for Hoodi. --shastaInbox: deprecated. --shasta.time: deprecated. --pacayaInbox: deprecated. --preconfirmation.whitelist: deprecated. Release notes can be found here: github.com/taikoxyz/simple-t…

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-mo…

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: 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: 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-mo… 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/simple-t…

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/bmdcp5YfzIn…