Ferveo primary sources

Reviewed: 2026-05-13 UTC

Core project framing

  • https://nikkolasg.github.io/ferveo/
    • Best concise public entrypoint in this pass. It frames Ferveo as a Tendermint-integrable platform for weighted DKG plus threshold decryption, with encrypted pending transactions and front-running resistance as the central goal.
  • https://github.com/anoma/ferveo
    • Useful implementation home and project-status anchor. Confirms this is being presented as a codebase plus documentation set rather than a polished product site.
  • https://raw.githubusercontent.com/anoma/ferveo/main/README.md
    • Best short source for the synchronous DKG for front-running protection framing, the note that the output key can feed threshold encryption or threshold signatures, and the explicit warning that the library is still under development and not audited.

Architecture and assumptions

DKG and threshold-crypto mechanism

Encrypted-transaction flow

  • https://raw.githubusercontent.com/anoma/ferveo/main/book/src/tx.md
    • Most valuable mechanism page in this pass. It makes explicit that proposers commit to encrypted transactions before reveal, block proposals carry previous-block decryption data, and finalization requires validator signatures to include valid decryption shares for each encrypted transaction.
    • Also the best source for two narrower but important control surfaces: fee payment is left outside the encrypted payload, and malformed transactions go through an aggregated invalid-share verification path rather than a simple silent discard.

Canonical paper

  • https://eprint.iacr.org/2022/898
    • Canonical research paper and best high-level statement of the formal goal: mempool privacy on BFT blockchains, with new DKG and threshold public-key-encryption constructions designed for Tendermint-like validator environments and large transaction throughput.

Main takeaways from this pass

  • Ferveo clears the corpus bar because it gives a comparison-ready lower-layer baseline for encrypted-mempool and fair-ordering systems rather than just another anti-MEV slogan.
  • The key analytical split is between weighted epoch-key generation, proposer commitment to ciphertext order, finalization-coupled decryption-share release, and invalid-ciphertext handling.
  • Ferveo is especially useful as a historical / mechanism baseline for later projects like Shutter Network, Blocklock, and other threshold-encryption ordering systems because it couples decryption liveness directly to consensus finality instead of to a separate trigger network or API.
  • The docs also make the privacy boundary unusually explicit: Ferveo hides pending transaction contents in the mempool, not long-term state or post-execution transaction data.
  • The main caveat is maturity. The repo explicitly says the library is under development and unaudited, so it is strongest in this corpus as a mechanism reference and comparison point rather than as confirmed production infrastructure.