Buyer-specific proof packet · AIGEN / OABP

Portable mission receipts for agent bounty payouts.

AIGEN already has strong mission discovery, content-addressed submissions, reward paths, and reputation. The missing interop seam is a self-contained receipt that a third-party agent, registry, or buyer can verify after the AIGEN endpoint is offline.

This packet proposes a small signed receipt shape for OABP v0.4: bind agent_id, mission_id, submission_id, content_hash, verifier decision, payout transaction, and spec version into one portable document.

Book A$390 readback Read markdown brief

Why now

AIGEN's CrewAI thread asks for AgentFolio/SATP-style receipt requirements. AIP-1 already requires content-addressed submissions and reward paths; AIP-3 covers server-signed attestations for reputation. A portable payout receipt connects those surfaces.

What changes

Add receipt_uri or receipt to resolved mission/submission responses, backed by GET /missions/{id}/receipts/{submission_id} and a signing key advertised in /.well-known/oabp.json.

What agents get

A buyer or agent can prove: this mission existed, this deliverable hash won, this verifier method accepted it, this payout or credit settled, and this server signed the bundle under a published key.

Minimal receipt shape

{
  "type": "oabp.mission_receipt",
  "spec_version": "AIP-1@0.4-draft",
  "issuer": "https://cryptogenesis.duckdns.org",
  "issued_at": "2026-05-22T07:09:00Z",
  "mission_id": "mis_94fb71f4d987",
  "submission_id": "sub_...",
  "agent_id": "0x...",
  "content_hash": "sha256:...",
  "verification": {
    "type": "first_valid_match",
    "result": "accepted",
    "decided_at": "2026-05-22T07:09:00Z"
  },
  "settlement": {
    "asset": "AIGEN",
    "amount": "100000000000000000000",
    "chain_id": 8453,
    "tx_hash": "0x...",
    "status": "settled"
  },
  "signature": "ed25519:..."
}

For off-chain credits, use settlement.status = credited with a ledger entry hash; for creator-judged missions, include the judging account and decision URI.

Acceptance checklist

Receipt is self-contained enough to verify without live database access.
Unknown fields are tolerated, matching AIP-1 forward-compatibility.
Content hash is the same hash already expected in AIP-1 submissions.
Signing public key is discoverable in /.well-known/oabp.json.
Receipt status distinguishes accepted, settled, credited, voided, and disputed.

Failure modes to avoid

Only exposing payout_tx behind a live API.
Omitting the deliverable hash, so the receipt proves payment but not work.
Signing mutable mission titles/descriptions without canonicalization.
Letting registry-routed anonymous submissions receive receipts as if identity-attested.
Making the receipt require an AIGEN-specific SDK to verify.

Outbound-ready GitHub note

Posted/usable as a spec discussion for Aigen-Protocol/aigen-protocol: propose OABP v0.4 portable mission receipts, link this packet, and offer either a small readback or a mock-first implementation sprint.

AIGENOABPagent bounty receiptsUSDC/AIGEN settlement proofno wallet spend