Paxiom
Paxiom · Engineering Binder & Build Log
Build Journal
Chronological build log, architectural drawing set, and R&D substrate archive.
Sheet PXM-J-100· 10 Public Prints· Updated 2026.11
Current Engineering State 2026.11
Open Standard
Paxiom Receipts (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.
R&D Substrate Track
Ethereum sync-committee verification (A-202), local Erigon MPT witness pipeline (A-201/A-205), and AO/Arweave audit trails — preserved below as upstream R&D.
Operating Posture
Self-funded, single-operator discipline. Every public capability is backed by deterministic tests and machine-readable runtime flags on GET /version.
J-100 · Build log

Receipts from the build.

Sparse by design. Entries appear when something material ships or when the product focus narrows.

Build Log Most recent first
2026.11.15 · v0.2.0
  • Released 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 support
  • Transitioned https://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 friction
  • Published formatted HTML specification sheets for Trust States & Precedence (PXM-RC-101) and Canonical JSON Profile (PXM-RC-102) alongside raw Markdown artifacts
2026.11
  • Narrowed the public surface onto a single wedge: Paxiom Receipts (paxiom.receipt.v0) — proof-bound Ed25519 receipts binding HTTP requests, delivered outputs, and x402 payments
  • Published initial zero-dependency Node and Python SDKs (verified byte-for-byte via cross-language canonical JSON & Ed25519 test vectors) and registered io.github.k-luecke/paxiom-receipts on the Official MCP Registry
  • Deployed the Base Mainnet & Base Sepolia USDC Transfer-log verifier, SSRF-hardened pre-payment seller preflight scanner, and Ed25519 counter-attestation runtime at https://api.paxiom.org
  • Consolidated the earlier ten-sheet drawing set, Phase 1 substrate schedules, and historical gate notes into this Build Journal
2026.05.10
  • A-202 hardened against downstream-consumer confusion by rejecting slot-mismatched device responses before platform signing
  • Service envelope posture tightened: payment, settlement, notary, and mock/reference states remain explicit
  • Public direction updated from waiting on Load/Ultraviolet to building a Paxiom-owned historical proof archive over encrypted Arweave evidence and AO-assisted compute
  • Erigon started against a Google Drive-backed cold warehouse; initial archive sync is in progress, not yet a production archive claim
  • A local Erigon proof-source adapter now maps eth_getBlockByNumber and eth_getProof into Paxiom's existing MPT verification pipeline for A-201/A-205 rehearsal
  • Internal operator-capital tooling reached a Base path-validation milestone with live funds; this remains private infrastructure, not a public product surface
  • RPC providers remain transport, not authority; Ethereum roots and locally verified proofs are the trust anchor
2026.05.06
  • Audit resolution closed across all four repos — every Critical, High, Medium, Low, and Info finding addressed (181 total). Tracker reconciled with code state.
  • Resolution methodology used parallel implementation review plus a red-team reviewer and moderator for architectural items, with cluster PRs for mechanical hygiene.
  • Open follow-ups remain (env-floor + UI-mutates cluster, font self-host, six paxiom UI surfaces) — explicitly scoped, not audit-blocking.
2026.05.05
  • Public site v1 structure — Home, Docs, Services, Status, Contact
  • Drawing-set visual language extended to public surfaces
  • Build log added under Status; receipts cadence established
  • Mobile layout rules committed for the binder pages
2026.04.29
  • Project Narrative (B-series) issued to the drawing set, 26 sheets
  • Construction-document register applied to founder-context material
  • Phase 1 → Phase 5 trajectory documented with moats per phase
2026.04.28
  • Operations Runbook (O-series) issued — incident and routine procedures
  • Key Custody & Identity Blueprint (E-series) issued — three-tier architecture
  • Audit Relay Blueprint (M-series) issued — operator-controlled review loop
2026.04.27
  • Phase 1 Blueprint (A-series) issued — five services, reference architecture
  • mk19 archive recovered from prior development environment
  • Sync committee verifier rebuild plan downgraded from open risk to partially mitigated
Entries prior to 2026.04.27 live in version control commit history across the Paxiom repositories.
J-200 · Architectural drawing set

The technical prints (ten public sheets).

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

B-Series · 26 sheets Public · Rev. A
Project Narrative · the territory and the bet

A founder's account of the agent economy, x402, the threat surface, and the long-horizon verification thesis behind Paxiom.

Open Document →
A-Series · 12 sheets R&D · Rev. A
Phase 1 Blueprint · five services, build sequence

Original specifications for the five Ethereum & cross-chain proof services, build sequence, and risk register.

Open Document →
T-Series · 8 sheets R&D · Rev. A
Technical Architecture · AO dispatcher for proof work

How AO routes verifiable Ethereum proof work across a distributed dispatcher topology, message schemas, and composability boundaries.

Open Document →
CA-Series · 8 sheets Testnet · Rev. A
Compliance Architecture · verifiable records, by construction

Independent audit-trail verification anchored to on-chain events and replayable AO process state on Arweave.

Open Document →
M-Series · 11 sheets Public · Rev. A
Audit Relay Blueprint · the operator's review loop

Mechanical structure for recording, forwarding, and verifying audit events while preserving operator decision-making.

Open Document →
E-Series · 12 sheets Public · Rev. A
Key Custody & Identity · trust boundaries

The three-tier key architecture (hot, warm, cold) governing signing, treasury separation, rotation, and compromise response.

Open Document →
O-Series · 17 sheets Public · Rev. A
Operations Runbook · incident & routine discipline

Severity framework, first-response discipline, and post-incident learning loop for platform operations.

Open Document →
F-Series · 16 sheets Vision · Rev. A
Phase 2 Vision Brief · private data compute

Longer-term planning brief for ZK proofs over private inputs in healthcare and financial workflows.

Open Document →
R-Series · 1 sheet Public · Rev. B
Build Map · Phase 0 through Phase 5

The multi-phase strategic map showing how proof-bound receipts and Ethereum state attestations fit into the wider arc.

Open Document →
G-Series · 1 sheet Archive · Rev. A
Phase 0 Status · substrate gate audit trail

Acceptance criteria and evidence locations for the HyperBEAM, BLS sync-committee, and Ethereum L1 reconstruction gates.

Open Document →
Note · Operational privacy

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.

J-300 · R&D substrate archive

Upstream proof substrates (parked behind Receipts).

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:

J-400 · Boundaries & non-claims

What is open — and what isn't claimed.

Next Engineering Extensions
  • Additional EVM and Solana USDC settlement adapters beyond Base Mainnet & Base Sepolia in POST /v1/receipt/verify-live
  • Optional facilitator receipt cross-checking alongside direct on-chain Transfer log verification
  • Evidence-hash adapters binding upstream cryptographic witnesses (A-201/A-202) into payload.evidence
  • Upstream reference PRs for the x402 v2 delivery-receipt extension across facilitator and wallet SDKs
Explicit Non-Claims
  • POST /v1/receipt/verify is strictly offline: it never claims on-chain finality and always surfaces unverified tx hashes as settlement_claimed_not_checked
  • POST /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 v0
  • No custody of customer funds — Paxiom never holds buyer wallets or escrowed balances
  • No third-party security audit certification or regulated legal attestation is claimed in v0
  • Upstream R&D services (A-201–A-205) remain experimental substrates, not active commercial SLA endpoints