github taikoxyz/taiko-mono taiko-alethia-client-v2.6.0
taiko-alethia-client: v2.6.0

pre-release5 hours ago

taiko-alethia-client v2.6.0

This release prepares the Taiko Alethia client, proposer, and prover for the Unzen Mainnet upgrade, restores forced-inclusion support, introduces new ZK proving strategies, and improves driver synchronization reliability.

Unzen Mainnet activation

Taiko Mainnet activates Unzen at Unix timestamp 1786021200, corresponding to 2026-08-06 13:00:00 UTC.

Upgrade client, proposer, and prover deployments before the activation time.

CLI changes

Added

  • --prover.forceSP1Proof / PROVER_FORCE_SP1_PROOF
    • Default: false
    • Selects SP1 instead of trying RISC0 first.
  • --prover.zkOnlyProofs / PROVER_ZK_ONLY_PROOFS
    • Default: false
    • Produces both RISC0 and SP1 proofs without an SGX companion.
    • Overrides --prover.forceSP1Proof and --prover.maxRisc0ProofProposalDistance.
    • Use only after Unzen activation; pre-Unzen RISC0+SP1 submissions will revert.
  • --prover.primaryProofDummy / PROVER_PRIMARY_PROOF_DUMMY
  • --prover.companionProofDummy / PROVER_COMPANION_PROOF_DUMMY

Renamed

  • --prover.maxZKProofProposalDistance--prover.maxRisc0ProofProposalDistance
  • PROVER_MAX_ZK_PROOF_PROPOSAL_DISTANCEPROVER_MAX_RISC0_PROOF_PROPOSAL_DISTANCE

Exceeding the configured RISC0 distance now falls back to SP1.

Removed or replaced

  • --prover.dummy / PROVER_DUMMY, replaced by the primary and companion dummy-proof flags.
  • --raiko.host.zkvm / RAIKO_HOST_ZKVM; proof requests are routed through --raiko.host.
  • --prover.sgx.batchSize / PROVER_SGX_BATCH_SIZE.
  • --p2p.syncTimeout / P2P_SYNC_TIMEOUT; P2P sync no longer switches to sequential block insertion after a timeout.

Proposer and prover startup now explicitly rejects missing --l1.ws or --l2.ws. The driver can use HTTP polling instead.

Proving and client changes

  • Restore forced-inclusion proposal inputs in the Go and Rust clients.
  • Add ZK-only RISC0+SP1 proving for SGX outages and deployments without a TEE service.
  • Fall back from RISC0 to SP1 when the RISC0 backlog exceeds the configured distance.
  • Support the Unzen verifier requirement that every proof pair contains at least one ZK proof.

Reliability improvements

  • Roll back proposal cursors after failed proposals so they are re-scanned.
  • Wait for execution sync before processing events.
  • Postpone event sync only while chain data is syncing.
  • Harden driver restarts during beacon-sync handover.
  • Correct forced-inclusion single-block handling.

Full changelog: taiko-alethia-client-v2.5.0...taiko-alethia-client-v2.6.0

Don't miss a new taiko-mono release

NewReleases is sending notifications on new releases.