Phase
Phase 0 → Phase 1 transition
Primary Objective
A working testnet path for proof work, signed service envelopes, and Ethereum-root-verified historical state from Paxiom-controlled infrastructure.
Funding
Self-funded. Day job pays the rent; internal operator tooling may help fund the build, but is not a public product.
S-110 · What exists, what's in flight
What's done. What's being built.
Completed
- Public drawing set (six documents, construction-document register)
- Phase 1 service map and reference architecture
- Audit relay blueprint with operator-controlled review loop
- Three-tier key custody model (hot, warm, cold)
- Operations runbook with severity framework and incident procedures
- OApp contracts deployed on Optimism and Base testnets, peered, message delivery confirmed
- AO compliance process loaded with real events and seeded with test data
- First mainnet AO process storing real Ethereum consensus data
- Working proof generation for slot storage and Uniswap V3 pool state predicates (substrate work for Phase 1 Service 01)
- Phase 1 service tests passing across sync committee, load-network, service, and UI surfaces
- A-202 slot-mismatch rejection added before response-envelope signing
- Strict deployment checks refuse mock paths and unsigned response envelopes
In Progress
- Reference implementation of Phase 1 services
- AO dispatcher experiments and proof job routing
- Public repository structure and service metadata
- Sync committee subprocess harness proof and HyperBEAM device dispatch hardening
- Paxiom-owned proof archive design: encrypted Arweave evidence, Paxiom-controlled index and keys, AO-assisted proof work
- Local Erigon archive sync into a Google Drive-backed cold warehouse with a local hot tier for active work
- A-201 and A-205 source-selection path for local Erigon
eth_getProof witnesses
- Private operator tooling for internal capital rehearsal; this remains separate from the public proof-service catalog
- Site v1 — public binder structure (this page is part of that work)
S-120 · Open questions
What hasn't been decided.
The platform has open architectural questions that remain genuinely undecided rather than provisionally settled. Naming them publicly is part of the discipline.
Open Questions
- Final proof system selection across the service catalog
- Settlement chain default — Base remains the working assumption
- Facilitator integration strategy (hosted Coinbase versus self-hosted x402-rs)
- Pricing under real workload — the current numbers are draft assumptions
- Which KYA standard to align with as the category consolidates
- Order of Phase 2 customer expansion (financial services first, healthcare second, or vice versa)
S-130 · Known constraints
What isn't claimed. And why.
Every claim the platform doesn't make is a claim it could be tempted to make later. Listing the non-claims explicitly keeps the temptation at the surface where it can be checked rather than buried where it can drift.
Not Claimed
- No production deployment yet — testnet and reference work only
- No production settlement claim — disabled or stubbed payment paths remain labeled as not settled
- No public proof archive bypass — commercially useful historical proof bundles are intended to be encrypted before Arweave storage
- No custody offering — the platform does not hold customer assets
- No mainnet-scale reliability — load characteristics are unverified at production volume
- No public trading, arbitrage, yield, or investment product — internal operator tooling is not a customer-facing service
- No regulated custody attestations or third-party security audit
- No enterprise SLA — service level commitments will be added as Phase 1 services mature
- No fully autonomous service market participation — ERC-8183 marketplace integration is forward-compatible but not active
- No guarantees beyond prototype scope — the documents describe what's intended, not what's certified
S-200 · Build log
Receipts.
Sparse by design. Entries appear when something material ships, not on a fixed cadence. Silence means the build is heads-down rather than newsworthy.
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 before 2026.04.27 live in the public repo commit history. The build log surfaces what's notable from a public reader's perspective; the full record is in version control.