Gevulot primary sources — 2026-05-08

Official docs

• https://docs.gevulot.com/
  • Intro positioning: universal proving layer for ZK
  • Surfaces the split between current Firestarter and planned ZkCloud
• https://docs.gevulot.com/gevulot-docs/zkcloud-design/overview
  • Architectural framing: dual-node system of provers and validators
  • Main claims: low cost, high performance, liveness, censorship resistance, predictable fees
• https://docs.gevulot.com/gevulot-docs/zkcloud-design/provers
  • Protocol control surface: validator participation, prover staking, proof-of-workload qualification, fallback provers, custom prover sets, VRF-based workload allocation
• https://docs.gevulot.com/gevulot-docs/zkcloud-design/transactions
  • Full proving-workload lifecycle from Run transaction to proof generation, verifier voting, finality, and reward distribution
• https://docs.gevulot.com/gevulot-docs/misc/faq
  • Explains why the team believes proving coordination must live in a dedicated layer one instead of an appchain/layer two on another base layer

Code / repos

• https://github.com/gevulotnetwork/gevulot
• https://raw.githubusercontent.com/gevulotnetwork/gevulot/main/README.md
  • Legacy repo framing: permissionless programmable layer one for deploying prover/verifier programs
  • Important caveat: original devnet phased out in favor of Firestarter and upcoming ZkCloud architecture

Notes

• No canonical whitepaper or litepaper was surfaced from the official docs during this pass.
• Best corpus use: compare Gevulot against Boundless and other proving-market layers on where workload routing, verification, rewards, and hardware policy are enforced — at the market edge, inside middleware, or inside a dedicated proving chain.