Summary: Boundless is the prover-market layer built on top of the RISC Zero line, not a new zkVM. What matters is the market structure: request routing, broker logic, collateralized fulfillment, and onchain settlement for proof jobs.
What it does:
Lets developers submit proof requests for zkVM workloads instead of operating their own proving hardware
Uses competing provers that bid on requests, lock them, generate proofs, and submit fulfillments onchain
Ships a Broker service for market interactions and a Bento proving stack for queuing, scheduling, execution, retries, and proof aggregation
Positions itself as infrastructure for app developers, rollups, and custom offchain execution flows that want reusable proofs without directly running prover fleets
Exposes SDK, CLI, contracts, and a foundry template so developers can request proofs and verify them from applications or smart contracts
Frames the network as a way to decouple execution from consensus so complex computation can happen off the base chain while succinct proofs are verified onchain
Key claims:
The official site says Boundless offers 99.99% uptime, high-performance compute, and below-market cost, positioning itself as production-oriented prover infrastructure rather than a research demo
The “What is Boundless?” docs describe a universal protocol where developers submit proof requests and provers compete to fulfill them, earning direct rewards and protocol-level incentives through proof of verifiable work
The “Why Boundless?” docs explicitly frame the mechanism as decoupling execution from consensus so blockchains verify succinct proofs instead of globally re-executing all computation
The proving-stack docs describe Bento as a semi-multi-tenant proving cluster built from prior Bonsai operating experience and Broker as the component responsible for pricing, bidding, collateralized lock-in, and proof fulfillment on the market
The monorepo README shows the project surface is broader than one service endpoint, with core contracts, SDK, CLI, broker, and zkVM guest components all living in the main repo
The repository also notes a mixed licensing posture, with contracts and assessor pieces under Business Source License before later Apache conversion, which matters when comparing how open the proving-market layer is versus the underlying runtime stack
Whitepaper: No canonical public whitepaper or litepaper was surfaced in the official site/docs during this pass. The strongest primary materials were the official site, docs, and monorepo README; see ../whitepapers/boundless-primary-sources-2026-05-08.md.