# AIGEN / OABP portable mission receipt readback

Buyer-specific packet for Aigen-Protocol/aigen-protocol and OABP implementers.

## Revenue hypothesis

- A$390 fixed readback: JSON schema, verifier checklist, endpoint delta, and failure-mode notes.
- A$1,900 mock-first implementation sprint: sample receipt endpoint, fixture tests, and docs PR.
- Payment after scope confirmation: invoice or USDC on Base/Polygon to `0x17D7251A8a8d60ab74d7D2B2d20D2a0389871729`.

No wallet signing, spend, transfer, bridge, swap, stake, trade, signup, or legal/payment-term acceptance happened while preparing this packet.

## Why this is timely

The CrewAI AIGEN thread explicitly asks for requirements around receipt format for AgentFolio/SATP compatibility. AIP-1 already has mission discovery, content-addressed submissions, reward paths, and verification types. AIP-3 already uses server-signed attestations for reputation portability. The missing seam is a self-contained mission completion receipt that survives endpoint downtime and can be checked by a third-party agent, registry, marketplace, or buyer.

## Minimal receipt shape

```json
{
  "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.

## Endpoint delta

- Add `receipt_uri` or embedded `receipt` to resolved mission/submission responses.
- Add `GET /missions/{id}/receipts/{submission_id}` or equivalent.
- Advertise a receipt signing public key in `/.well-known/oabp.json`.
- Keep receipt verification independent of any AIGEN-specific SDK.

## 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`.
- Registry-routed anonymous sessions do not receive identity-attested receipts unless the registry attestation flow has bound an EVM address.

## 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.

## CTA

If useful, I can turn this into either:

1. A$390 receipt-schema readback: schema, examples, endpoint diff, verifier checklist.
2. A$1,900 mock-first implementation sprint: sample endpoint, fixtures, tests, and docs PR.

Contact: info@transhumanism.com.au