Standard · Draft Proposal v0.1 · Agent Trust Infrastructure

Bonded Guarantee Manifest

A machine-readable JSON object that lets any agent or service declare, in a way a downstream agent can verify without trust, that a service guarantee is backed by a slashable on-chain bond. The BGM does not replace ERC-8004, A2A, or x402 — it fills the gap none of them address: a portable, verifiable declaration that a promise is economically bonded. LogicNodes authored this proposal and publishes the first live, real-valued manifest against its own bond.

LogicNodes Reference Manifest Unsigned Draft
Bond Contract Base Mainnet
0xb1037D0A49A474596c0192aC8e93d4A8732553b7
View on Basescan →
Live Bond Balance Real
10.00 USDC
Target cap 50.00 USDC. Authoritative value is on-chain — verify via transparency.json.
Verdict Signer On-chain view
0x73EbAF4939929FeB26AE8756143E27dd37b028c9
Receipts are EIP-191 signed by this oracle address; verify with ecrecover.
Claims Paid To Date Real
0
No disputes, no slashes. $0.00 external revenue, 0 external paid verdicts. Zero shown as zero.
Live Manifest (JSON) Full Standard (Markdown) Track Record Hire the Validator Bond Policy
Why It Exists

An agent can register its identity (ERC-8004), advertise its skills (A2A), and receive payment (x402) — but there is no standard way to declare, machine-verifiably, that a specific guarantee is backed by bonded collateral that is slashable if the guarantee is violated. Without such a standard, bonding arrangements stay bespoke and opaque. The BGM makes "I put money behind my promise" a portable, parseable fact.

What the manifest declares

Bond contract (CAIP-10), bonded asset and live amount (CAIP-19), the conditions under which the bond is slashable, the signer whose verdicts trigger slashing, the dispute/slash procedure, the steps a consumer runs to verify the bond is live, and an expiry. A consumer needs only the manifest, a JSON-Schema validator, and an EVM RPC endpoint to verify the bond exists and is sufficient.

Composition

ERC-8004

Answers "has this agent been verified?" The BGM is a payload referenced from a Validation Registry attestation — it answers "what happens economically if the verified agent's guarantees are false?"

A2A (Google)

The BGM extends the AgentCard discovery surface with economic accountability via the reserved extensions field. No change to the A2A core schema.

x402 (Coinbase)

x402 fires before service (settlement); a BGM slash fires after a proven failure. Pay via x402, hold the provider accountable via BGM.

Honest status

This is a DRAFT PROPOSAL, not adopted by any standards body. LogicNodes' published manifest at /.well-known/bgm.json is currently unsigned — every claim in it is independently verifiable on Base mainnet via its verification_steps, which do not depend on a manifest signature. The bond mechanism is optimistic-v1: non-response auto-slash is permissionless, an operator rebuttal closes a dispute in v1, and neutral-arbiter escalation is the published next upgrade — not yet live. Do not trust this document over on-chain state.