1 · THE ONE BREATH
What the reserve builds — receipts first, agents second
Beehive Nature Reserve builds the
receipts-first evidence and agent layer for onchain ecosystems: an open (AGPL) organism of
40 live, keyless, static surfaces plus Rust instrumentation whose standing law is
every claim carries a receipt · every absence is honest · a failed fetch is never a value.
For Batch 004's agents vertical we bring the read-and-trust infrastructure ERC-8004 needs
and nobody has shipped — measured first, on Base.
2 · OUR BASE RECEIPTS — measured on your chain, two oracles each, all re-runnable
RECEIPT 1 · the ERC-8004 read-first pass — your canonical
Trustless Agents registries, token by token
the singletons are real but deliberately minimal (130-B ERC-1967 upgradeable proxies,
chain-identical implementations, admin slot empty, no on-chain count surface, URI-optional) —
and live: every sampled id exists on both chains with distinct owners; Base token #25331 is
owned by exactly the Prover Agent address the ecosystem literature names. the chain verified the
literature — that is our product working. honest absences named: the Validation registry has no
canonical address yet. → the receipt ·
the re-runnable tool
RECEIPT 2 · the frozen-seed measurement — Base deployed
storage, read at the SLOAD level
the ERC-20i family's open escrow question (locked record: frozen seed or recompute?)
answered on Base bytecode + live wallets — one wallet holding five mutually distinct seed values
kills every recompute hypothesis; the Base boundary (frozen data, balance-coupled existence) is
measured at storage level, which is what any marketplace on the family needs first.
→ the receipt ·
conserved contract sources
RECEIPT 3 · the census — Base's ERC-20i family enumerated,
with the controls
Souli (2024, 1,150 holders), PEPI-Base, FUNGI, JELLI — enumerated on two independent
oracles with the Blockscout-truncation control (1,000-row silent truncation caught and corrected)
and a passing control proving a dead market dead rather than unreachable.
→ the census
THE INSTRUMENT — the b-indexer: keyless by construction, Base-ready today
Rust + SQLite read-only indexer, 14/14 tests CI-green, GET-only router with no POST
handler in existence, sendtx: NO printed on the wire by an attestation command, the two-oracle law
in the schema (every response carries its sources; divergence fails closed). ERC-8004's minimal
registries require exactly this: agents on Base will need an indexer — ours is built, tested, and
keyless. → the crate
3 · THE SYNERGY MAP — your named bets × our live lanes
| batch 004 vertical | our lane, live today | the 8-week product |
|---|---|---|
| agents | E-1 receipts of the canonical registries; the b-indexer; the integrity grammar (scores as evidence, never weight) in production on BiGen | the Trustless-Agents read layer on Base: discovery, reputation-as-evidence, feedback-as-receipts — keyless, sovereign-rail first |
| trading | §10 unblocked the escrow question; the OFFER mechanism specified; the Apiary surface live | a Base-native marketplace pilot with the frozen-seed boundary engineered in from day one |
| payments | optical scan-to-pay adjacency (bComb); the festival economy spec | advisable stretch, not the batch thesis |
why this is synergy and not flattery: every row is a lane
we were already building, on rails that already read your chain — the batch accelerates work with
receipts behind it, not work that starts at acceptance.
4 · THE 8-WEEK PLAN — every milestone a receipt
The roadmap — what is live, what comes next
weeks 1–2 — the agent read layer live on Base's public rails (sovereign first; the free-tier oracle never default, never sole)
weeks 3–4 — reputation rendered as evidence with the integrity grammar; feedback as receipts
weeks 5–6 — one real agent-counterpart integration (we know the registered token ids — we read them)
weeks 7–8 — the Demo Day artifact: a live registry view whose every number carries its source
weeks 3–4 — reputation rendered as evidence with the integrity grammar; feedback as receipts
weeks 5–6 — one real agent-counterpart integration (we know the registered token ids — we read them)
weeks 7–8 — the Demo Day artifact: a live registry view whose every number carries its source