The main site presents the live shipped product — Paxiom Receipts, the @paxiom/receipts & paxiom-receipts SDKs + MCP server, and the Base Mainnet verifier at api.paxiom.org. This journal keeps the complete engineering trail in one place: dated release notes, the ten-sheet architectural drawing set, earlier Ethereum/AO substrate explorations, and explicit non-claims.
paxiom.receipt.v0 · v0.2.0) — MIT specification, x402 v2 delivery-receipt extension draft, @paxiom/receipts@0.2.0 on npm, paxiom-receipts==0.2.0 on PyPI, Official MCP Registry (io.github.k-luecke/paxiom-receipts), and free public Base Mainnet reference verifier on api.paxiom.org.A-202), local Erigon MPT witness pipeline (A-201/A-205), and AO/Arweave audit trails — preserved below as upstream R&D.GET /version.Sparse by design. Entries appear when something material ships or when the product focus narrows.
paxiom.receipt.v0 v0.2.0 across Node (@paxiom/receipts@0.2.0) and Python (paxiom-receipts==0.2.0) alongside the x402 v2 delivery-receipt extension draft: added vendor-neutral Payment-Receipt headers, /.well-known/x402-keys.json seller key discovery & unauthorized_issuer verification, dual jcs-sha256 / raw-sha256 payload hashing, native x402 v2 header auto-parsing, and CAIP-2 EVM + Solana base58 transaction signature supporthttps://api.paxiom.org (0.2.0) into a 100% free, rate-limited public reference utility — removing commercial per-call paywalls and API-key gating on POST /v1/receipt/verify-live and POST /v1/x402/preflight so any x402 buyer, wallet, or facilitator can adopt or self-host the standard without frictionPXM-RC-101) and Canonical JSON Profile (PXM-RC-102) alongside raw Markdown artifactspaxiom.receipt.v0) — proof-bound Ed25519 receipts binding HTTP requests, delivered outputs, and x402 paymentsio.github.k-luecke/paxiom-receipts on the Official MCP RegistryTransfer-log verifier, SSRF-hardened pre-payment seller preflight scanner, and Ed25519 counter-attestation runtime at https://api.paxiom.orgeth_getBlockByNumber and eth_getProof into Paxiom's existing MPT verification pipeline for A-201/A-205 rehearsalBefore narrowing onto Paxiom Receipts as the immediate product wedge, we documented the broader verifiable-claims thesis in a construction-style drawing set: narrative, service blueprints, AO proof-routing topology, compliance records, key custody, and incident runbooks. None of these prints are required to adopt @paxiom/receipts, but every sheet remains online for architectural diligence.
A founder's account of the agent economy, x402, the threat surface, and the long-horizon verification thesis behind Paxiom.
Open Document →Original specifications for the five Ethereum & cross-chain proof services, build sequence, and risk register.
Open Document →How AO routes verifiable Ethereum proof work across a distributed dispatcher topology, message schemas, and composability boundaries.
Open Document →Independent audit-trail verification anchored to on-chain events and replayable AO process state on Arweave.
Open Document →Mechanical structure for recording, forwarding, and verifying audit events while preserving operator decision-making.
Open Document →The three-tier key architecture (hot, warm, cold) governing signing, treasury separation, rotation, and compromise response.
Open Document →Severity framework, first-response discipline, and post-incident learning loop for platform operations.
Open Document →Longer-term planning brief for ZK proofs over private inputs in healthcare and financial workflows.
Open Document →The multi-phase strategic map showing how proof-bound receipts and Ethereum state attestations fit into the wider arc.
Open Document →Acceptance criteria and evidence locations for the HyperBEAM, BLS sync-committee, and Ethereum L1 reconstruction gates.
Open Document →Cold-tier custody procedures, escalation contacts, and operator-only key rotation details are intentionally omitted from the public sheets. Architecture is public; operational attack-surface specifics stay private.
During April–May 2026, Paxiom prototyped five Ethereum and cross-chain attestation services (A-201 storage-slot proofs, A-202 sync-committee header verification, A-203 cross-chain message verification, A-204 transaction simulation, and A-205 historical MPT state). Building those envelopes revealed a simpler, universal gap across every x402 API: buyers lacked a standard signed receipt proving what any paid HTTP call actually delivered. That envelope became Paxiom Receipts.
The earlier binder pages remain available verbatim at their original URLs:
POST /v1/receipt/verify-liveTransfer log verificationA-201/A-202) into payload.evidencex402 v2 delivery-receipt extension across facilitator and wallet SDKsPOST /v1/receipt/verify is strictly offline: it never claims on-chain finality and always surfaces unverified tx hashes as settlement_claimed_not_checkedPOST /v1/receipt/verify-live verifies Base / Base Sepolia USDC Transfer events and counter-signs with Paxiom's published Ed25519 key; it does not retrieve off-chain Arweave archives in v0A-201–A-205) remain experimental substrates, not active commercial SLA endpoints