Boundless runs a live, permissionless marketplace where provers compete to fulfill on-chain requests for zero-knowledge proofs. From June 17 to June 24, 2026, Veridise reviewed a redesigned fulfillment flow that splits proof verification and request assessment out of the core market contract, routing both through a new router with pluggable verifier and assessor adapters. The review surfaced five issues, none critical. Boundless fixed three, including the highest-severity one, and documented its reasoning for the remaining two, both tied to deliberate design and migration choices.
TLDR
- Veridise reviewed Boundless Marketplace’s new fulfillment router, covering 16 Solidity files
- The highest-severity finding, around binding proofs to provers, is fixed with a commit-reveal scheme
- Manual review led the engagement; Vanguard and Slither screened for common bug patterns
- Zero critical findings; Boundless documented its reasoning on the two design-level items
What Veridise Reviewed
Three Veridise analysts reviewed 16 Solidity files at commit e2bc0cc, covering the redesigned fulfillment flow for Boundless Marketplace. The redesign moves proof verification and request assessment out of the core market contract into a new BoundlessRouter, which resolves a request’s proof type to one of several pluggable verifier and assessor adapters. Veridise had reviewed an earlier version of the same marketplace at commit f0e5fc4.
Manual Review, With Static Analysis for the Common Patterns
Manual review led the engagement, tracing how the router selects a verifier or assessor and how the market settles a fulfillment. Vanguard and the open-source tool Slither ran alongside, screening for common patterns like reentrancy and uninitialized state so analysts could concentrate on the trust boundaries between the market, the router, and its adapters. Boundless and Veridise tracked findings and fixes through AuditHub, the security platform built by the Veridise team, throughout the engagement.
What the Review Found
The review surfaced five issues: one high, three medium, and one informational, with no criticals. Three are fixed.
The highest-severity finding concerned how the router’s on-chain assessor ties a submitted proof to the prover who earns credit for it. The batch signature covered the prover’s address, but each proof was validated only against its claim digest, so a copy of a pending fulfillment could in principle be resubmitted under a different address. Boundless closed this with a commit-reveal step: provers now commit to the exact batch in a prior block before revealing the proof.
A related finding covered permissionless verifier and assessor classes, where registration checked interface support rather than verification behavior. Boundless tightened this by disallowing permissionless assessor classes, keeping the permissionless verifier path as an explicit opt-in for requestors.
The remaining two medium items reflect deliberate choices Boundless documented in the report. The legacy fallback path is a temporary bridge for the broker migration window, and Boundless keeps its proof-type settings in sync with the new router through its governance runbook until the path is removed. The second covers payment ordering in the never-locked fulfillment path, behavior Boundless had already reviewed in an earlier audit and treats as known. The informational item, unused code, was removed.
Why This Matters
A proof marketplace depends on two guarantees: payment goes to the prover who did the work, and the router accepts only proofs that pass real verification. This review focused on exactly those boundaries in the new modular design, and the commit-reveal change strengthens the first one directly.
This is Veridise’s second audit of Boundless Marketplace. Emiliano Bonassi, VP of Engineering at Boundless, described why the team keeps coming back:
“Compared to traditional crypto protocols, where the business logic is usually straightforward, Boundless works with zero-knowledge proofs, mathematical objects that only a few people know how to build, and only a few people can actually verify. Veridise is one of the few that understands that complexity.”
The tools from this engagement remain available to Boundless through AuditHub as the router continues to evolve.
Working on a similar protocol?
If your protocol separates who signs a submission from what gets verified, the binding between the two deserves its own review. It’s easy to treat them as one check during design.
If you want a second pair of eyes before your next deploy, Request Audit.
What Is Boundless Marketplace? The Takeaway
Boundless Marketplace lets provers compete to fulfill on-chain requests for zero-knowledge proofs. Veridise’s second review of the marketplace covered its new modular fulfillment router, combining manual analysis with automated tooling through AuditHub. Boundless fixed the highest-severity finding with a commit-reveal step and documented its reasoning on the remaining design-level items.