ChonkyBFT

  • Name: ChonkyBFT
  • URL: https://arxiv.org/abs/2503.15380
  • Category: committee-based single-slot-finality BFT consensus / rollup sequencer-consensus primitive / low-latency fast-BFT baseline
  • Summary: ChonkyBFT is worth cataloging not just as ZKsync’s consensus protocol or a footnote in the recent fast-BFT wave, but as a distinct committee-based design that makes a particular practical tradeoff unusually explicit: it prefers simplicity, single-slot finality, and one voting round over the higher Byzantine tolerance and more layered communication structure of classic 3f + 1 designs. In the reviewed paper and Matter Labs specification materials, ChonkyBFT combines FaB Paxos, Fast-HotStuff, and HotStuff-2 influences into a protocol with quadratic replica-to-replica communication, n >= 5f + 1 fault tolerance, no chained-finality pipeline, and explicit re-proposal rules to avoid rogue blocks that might look final to partial observers. That makes ChonkyBFT a useful comparison point for HotStuff-2, Minimmit, HotShot, and Alpenglow because the real mechanism is not just single-slot finality, but the specific tradeoff between reduced fault tolerance, no chaining, quadratic communication, re-proposal discipline, and formal-spec-backed implementation simplicity.
  • What it does:
    • Defines a partially synchronous committee-based BFT protocol used in the ZKsync system, targeting one voting round and single-slot finality
    • Uses a stricter n >= 5f + 1 fault model so it can reduce the number of voting rounds relative to more conservative 3f + 1 families
    • Avoids chained consensus and instead aims to finalize every block directly, so user-visible finality does not depend on later descendant blocks
    • Keeps quadratic communication between replicas rather than optimizing for a more complex linear path, explicitly trading some asymptotic elegance for simpler reasoning and implementation
    • Requires re-proposals after timeout scenarios where a commit quorum certificate may have existed but not propagated widely enough, so observers are less likely to encounter apparently committed-but-noncanonical rogue blocks
    • Ships with both implementation code and formal-spec / model-checking artifacts, making safety arguments and edge cases more legible than in many performance-first consensus designs
  • Key claims:
    • ChonkyBFT clears the corpus bar because it isolates a reusable fast-BFT design point that later performance-stack comparisons often flatten together: single-slot finality through reduced fault tolerance plus quadratic communication, rather than through better networking alone.
    • The paper’s abstract makes the protocol’s bundle of claims explicit: one round of voting, single-slot finality, quadratic communication, and n >= 5f + 1 tolerance. That bundle is the main reason to preserve it as its own mechanism page.
    • Matter Labs’ spec README is especially useful because it states the practical design philosophy plainly: authenticator and linear-message optimizations were deprioritized in favor of transaction latency, systemic simplicity, provable finality, and implementability.
    • The re-proposal rule is a particularly reusable insight from this pass. The reviewed spec notes a subtle public-blockchain problem where a commit quorum could form without propagating widely enough; ChonkyBFT addresses that by forcing the next proposal to re-propose the earlier block, preserving block-level interpretability.
    • ChonkyBFT is analytically valuable because it separates single-slot finality from several neighboring design choices that are often bundled together: chain-versus-slot finality, communication topology, fault threshold, timeout handling, and justification discipline.
    • The strongest caveat from this pass is scope. The paper and repo materials are specific to ZKsync / ZK Stack consensus, so this should be treated first as a mechanism page and comparison baseline, not as a generic standalone blockchain profile.
  • Whitepaper: Yes. The canonical primary artifact is the paper ChonkyBFT: Consensus Protocol of ZKsync, supported by Matter Labs’ official specification materials in the era-consensus repository; see ../whitepapers/chonkybft-primary-sources-2026-05-14.md.
  • Sources:

Internal linkages