OBOL / Permit2 / x402 release confidence

Third-party readback for Spark2 x402 payments before release.

A fixed-scope packet for the Obol Stack release path: verify the user-facing sell/buy docs, payment-token wording, 402 asset metadata, Permit2 assumptions and Spark2 external endpoint smoke plan before maintainers tag or announce.

Readback targets

  • obol sell inference / obol sell http payment-token wording.
  • ServiceOffer and PurchaseRequest docs for asset symbol, decimals and atomic units.
  • 402 response shape: token address, symbol, transfer method and Permit2 metadata.

Spark2 smoke plan

  • Unpaid request should return the expected OBOL/Permit2 challenge.
  • Paid-path proof should be validated only with a maintainer-provided safe fixture.
  • Endpoint, facilitator and target-network assumptions get written down clearly.

Guardrails

  • No private keys, wallet signing, token transfers or live payment attempts by default.
  • No live-system probing beyond public docs/headers unless explicitly in scope.
  • Local, fork, testnet or maintainer-provided fixtures preferred.

Deliverable

  • One-page release-readback table: observed command/docs surface, expected token metadata, and gaps.
  • Safe smoke script or command checklist for maintainers to run locally/against staging.
  • Release-note wording suggestions for OBOL Permit2 vs USDC ERC-3009 paths.
  • Follow-up PR-ready docs patch if the readback finds wording or fixture gaps.

Settlement rail

Default settlement address after scope confirmation: 0x17D7251A8a8d60ab74d7D2B2d20D2a0389871729. Preferred network: USDC on Base or Polygon.

No spending, signing, transfer, bridge, swap, stake, trade or crypto action happens from Peter's wallet without explicit approval.

OBOL Permit2x402 v2Spark2 external endpointRelease smoke