// the find
taikoxyz/taiko-mono
Taiko Alethia based rollup protocol 🥁
Taiko is a based rollup on Ethereum — meaning Ethereum L1 validators sequence transactions instead of a centralized sequencer. It's a monorepo covering protocol contracts, two client implementations (Go and Rust), bridge UI, relayer, event indexer, and supporting tooling. Target audience is Ethereum infrastructure developers and node operators, not application developers.
The 'based' sequencing design is genuinely interesting — removing the sequencer trust assumption is a real architectural bet, not just marketing. The repo has two independent client implementations (taiko-client in Go, taiko-client-rs in Rust) which is a meaningful commitment to client diversity. Protocol contracts are fully NatSpec-documented and specs live alongside the code in packages/protocol/docs, which makes the gap between spec and implementation auditable. CI coverage is thorough — separate Docker, test, and deploy workflows per package, with a merge gatekeeper and release-please automation.
Main branch is explicitly warned as unstable and you're pointed to a versioned branch for anything production-relevant — fine for a live protocol, but disorienting for contributors trying to understand current state. The monorepo mixes Go, Rust, TypeScript, and Solidity with no single unified build entrypoint; getting a full local dev environment running requires coordinating four different toolchains. The Rust client (taiko-client-rs) appears newer and less documented than the Go client, so it's unclear which one is the canonical implementation going forward. The NFT packages (nfts, taikoon-ui) feel bolted on and unrelated to the core rollup work, adding noise to an already large repo.