The technical blueprint is out. This is how we're building a based rollup that actually works.

Why based matters

Most rollups today run on centralized sequencers. One company controls transaction ordering. One point of failure. One entity that can censor you, extract MEV, or simply go offline and take the whole network with it.

We didn't want to scale Ethereum by introducing new trust assumptions. So Taiko hands the sequencing back to Ethereum's own validators. Same censorship resistance, same liveness guarantees. If Ethereum is live, Taiko is live. If Ethereum won't censor you, neither will we.

What we built

Sub-second preconfirmations without a centralized operator. Our two-phase system starts with whitelisted operators and evolves to permissionless participation, where any L1 validator can opt in.

Batch-based proving that slashes costs while keeping blocks small and responsive. Multiple blocks are proved together with aggregated proofs.

A multiproving system where every batch gets verified through ZK-SNARKs and SGX. If one proof system breaks, you're still covered.

The whitepaper has the formulas, the protocol specs and the technical architecture. It walks through Ontake, Pacaya, and what's coming with Shasta (10x cost reductions, anyone?).

The point

Based rollups work. They're not theoretical. They're live, handling real transactions, proving that you can scale Ethereum without compromising on decentralization.Read it here.

Explore open positions on our job board.

Get the latest from Taiko:

• Website: https://taiko.xyz.

• Discord: https://discord.gg/taikoxyz.

• GitHub: https://github.com/taikoxyz.

• Twitter: https://twitter.com/taikoxyz.

• Community forum: https://community.taiko.xyz.

• YouTube: https://www.youtube.com/@taikoxyz.

• Warpcast: https://warpcast.com/taikoxyz.

Contribute to Taiko on GitHub and earn a GitPOAP! You will also be featured as a contributor on our README. Get started with the contributing manual.