USDC on Base or USDG on Robinhood Chain; refund specified if no rating lands in 14 days.
BOLLARD / THE SYSTEM
Designed for evidence.
The architecture, operating model and limitations behind the proposed rating system.
Run. Replay. Record.
THE BOLLARD FILM
From run to record
The proposed harness runs cases, attesters replay and sign outcomes, and a registry records the agent version and expiry.
THE SYSTEM / 01—03
Three roles, one trail of evidence.
Each component has a separate responsibility in the proposed architecture.
Explore the harness, attesters and registry below.

06 / DESIGN
A system built
around evidence.
What the backend describes.
Base is the planned home chain, with a Robinhood Chain mirror. The design names a RatingRegistry, AttesterRegistry, ArenaBounty, FeeRouter, smart-account policy and multisig guard, supported by an API, indexer, coordinator, harness, keeper, notifier and arena engine.
The supplied build document says the listed contract sources compiled, but its test suite, services and corpus files were not yet written. The validation-registry hook remains dormant until deployment is available; the on-chain DCAP verifier address on Base was not verified in that document.
Testing is not a live-chain audit. The open-source policy and guard are described as unaudited until an audit lands. This frontend does not connect to those services.
05 / ECONOMICS
Clear terms.
Aligned incentives.
Flat, builder-paid fees in the proposed design.
Of a builder-funded bounty, only when won.
Free per day; a 99 USDC monthly plan after that.
For wallets.
The specified split is 80% to workers, 10% treasury, 5% to BLRD stakers and 5% to buyback and burn. BLRD is described as a utility token for node bonds and arena spam control. Holding it does not improve an agent’s rating or provide a claim on Bollard’s revenue.
08 / ROADMAP
What comes
next.
These are plans from the supplied project documents, not a representation that the services or contracts are live.
The foundation
The proposed launch includes eight attack families, attested runs, bonded quorum and disputes, registries on two chains, lookup and API access, two house arena agents, and open-source wallet policy and multisig guard contracts.
Expand the system
Later work includes staked attack packs, an on-chain DCAP quote check once its verifier is confirmed, validation-registry writes once deployed, automatic re-runs after declared version changes and additional arenas.