Taiko

Taiko's latest Security Council proposal (Proposal0026) executes a 21-action batch that sends 100% of the L2 basefee to the block proposer, up from 75%, via the inbox basefeeSharingPctg. Users pay exactly the same as before; the change means proposers who sponsor a user's gas now recover the full amount instead of three quarters, making gas sponsorship a break-even round trip rather than a guaranteed loss.

The same batch rotates proving to raiko2 v0.9.0: new RISC0 image IDs, SP1 program keys, and SGX enclave measurements are all trusted together, while the previous v0.8.0-rc1 identifiers are marked untrusted. From execution onward, only v0.9.0 proofs are accepted. The proposal was already reflected in Taiko's codebase and client releases, with artifact-verification material published for review.

Taiko posted a warning that scammers are sending emails impersonating the project and offering fake jobs. The team says these messages are not from them, and asks people to always verify the sender and rely only on official Taiko channels for recruitment-related communication.

Taiko released taiko-geth v2.7.0, a mandatory, consensus-sensitive execution-engine upgrade for node runners on both networks. The release fixes EIP-4788 beacon-roots system-call handling when building Unzen blocks, aligning block building with the import path to prevent state-root mismatches once the beacon-roots contract is deployed.

It sets the canonical zero parent beacon root before execution, rejects non-zero roots during block building and header validation, and drops built-in Masaya network support. Nodes deriving blocks from L1 — not just block producers — must upgrade; runners already on alethia-reth need no changes, and Taiko repeats its recommendation to switch to alethia-reth for ongoing node operation.

Taiko's Security Council Proposal #39 is approved and now sits in the community veto window for roughly 10 days. It upgrades the Bridge and ERC20Vault, and per Taiko's walkthrough it targets a bridging bug exposed by EIP-8037 ("Glamsterdam" storage pricing): creating a new storage slot now costs 97,920 gas while the bridge forwarded only 35,000 when paying out Ether, refunds, unused fees, recalls, and relayer fees. A smart wallet writing one storage slot on receipt runs out of gas, and the failed payout reverts the whole call.

The proposal also adds opt-in permit and Permit2 transfers so no separate approve transaction is needed (existing sendToken behavior is unchanged), and fixes a live bug where the first transfer to L1 of an L2-native token with no L1 counterpart failed since June. Taiko notes two other Security Council proposals executed this month: #37 bumped Raiko verifiers to v0.8.0, cutting Risc0 proving cycles, and #38 restructured the Security Council.

• All proposal addresses, storage-layout checks, and verification commands are published during the veto window.

Taiko DAO's Security Council Proposal #24 is open, with TAIKO holders having roughly a 10-day window to veto it. The proposal upgrades four proxies — the Bridge and ERC20Vault on both Ethereum and Taiko — and registers a new resolver on L2. No new contract code ships with the update.

Taiko's CTO Gus Gonzalez is stepping down from his role, as announced by the project on X. The team thanked him for building the rollup's engineering foundation. Gonzalez will remain part of the Taiko ecosystem as an advisor. A replacement CTO was not announced in the post.

The Pheasant Super App launched on Taiko, providing a single AI-powered interface for on-chain interactions. Users tell Pheasant what they want and it converts that intent into on-chain execution, which Taiko promoted as "tAIko."

Taiko enabled Unzen on mainnet, making a ZK proof mandatory for every block. No single proof system can finalize the chain on its own going forward — Validity Proofs are enforced at the protocol level, giving the rollup verifiable and always-on ZK security that runs on mainnet today.