Every running surface exposes or generates its exact Render source fingerprint from the official RENDER_GIT_COMMIT: static viewer /release.json, x402 runtime /api/release, and Enterprise OS /api/v1/release. Each response identifies the repository, branch and deployed commit without exposing credentials or write capabilities. A deployment is accepted only when that fingerprint equals the intended Git commit; correction-only deployments are not counted as new product updates.
npm run test:x402-production
npm run test:base-verify
npm run test:x402-offer-receipt
npm run test:static-releaseBaseProofPay is a read-only public demo for verifying agent-payment settlement receipts and payer-controlled spending policies on Base.
BaseProofPay is the Treasury/Payment component of CATVERSE Base Lab Enterprise OS. The Enterprise OS is the umbrella product; BaseProofPay keeps its component name on the static viewer and x402 runtime.
- Canonical umbrella product:
CATVERSE Base Lab Enterprise OS - Base Dashboard short alias:
CATVERSE Base Lab OS - Primary Base Account:
gaysonloser.base.eth/0xBa36D092dB2999bb1FaBbaf281AC956A97189C25 - Linked execution EOA:
base/0x9903E1e8C871321ee2Ed80cea8a5899F0992ba9e - Base App ID:
6a5c632cf364895c3c606518 - Builder Code:
bc_iscm570t
The execution EOA is used for eligible Coinbase Wallet actions. It does not replace the Base Account as the Basename, Base App, Base Dashboard, Talent or contract/evidence identity.
Builds and tests run in ephemeral GitHub-hosted runners through BaseProofPay Cloud CI. Render owns the public runtime, Frappe Cloud owns ERPNext records, and the local Mac is reserved for source editing and final wallet review. See Cloud Development Runtime.
index.html: static receipt viewer with the completed Base Mainnet technical canary.baseproofpay_app_icon_1024.png: public application icon.- Base Dashboard ownership marker:
base:app_id=6a5c632cf364895c3c606518.
The public viewer does not connect a wallet, request a signature, send a transaction, or store credentials.
- SpendingPolicyManager:
0x1bBe5B45757D66Fd97A818A62c89FaBD90cdC1d1 - PaymentReceiptRegistry:
0xD7CE8ecED9CDda01365b2eAD539581Afd981880B - Canary transaction:
0x9295affca6214350e9c55d8785354f123ef47bd15e4249efe1b7fbea140f2f1c - Result: exact
1 USDCsettlement, zero residual allowance, zero Registry balance, and matching policy plus immutable receipt.
The payer and payee wallets are controlled by the same owner. This is a technical canary, not independent-user adoption.
- Production endpoint:
https://baseproofpay-x402.onrender.com/payer - Builder-attributed canary:
0x3293bae0c55f9dcf49991ae92fa5bfaf740c4b165d5d26df4556ca75b8cc0528 - Result: exact
0.01 USDCEIP-3009 settlement, no allowance, zero ETH value, facilitator-paid gas, and a successfulPAYMENT-RESPONSE. - Attribution: the official ERC-8021 checker recognizes BaseProofPay Builder Code
bc_iscm570t; transaction calldata also carries facilitator codecdp_facil1.
This production payment used a self-controlled technical payer. It proves the x402 transport and Builder attribution path, but it is not independent-user adoption and must not be replayed.
GET /api/inventory-entitlement-evidence is a second x402-protected resource for CATVERSE inventory-entitlement reconciliation. It returns only after a valid exact Base USDC x402 settlement and exposes the verified BaseInventoryRoot, the BASE-XERP-INVENTORY-01 business-event class, and a read_only_evidence ERP handoff boundary. It neither creates an ERP document nor values inventory onchain. Payment identifiers remain globally replay-locked across both protected resources.
The public /payer client now lets a voluntary external EOA choose either reconciliation evidence or CATVERSE InventoryRoot entitlement evidence before connecting. The selected route is then locked into the unpaid challenge, EIP-712 authorization, payment identifier, Builder Code assertion and one-time settlement check. It never auto-connects a wallet, requests token approval, or permits a self-controlled GAYSON wallet to stand in for independent adoption.
GET /api/agent-commerce-resources is the read-only discovery surface for agents and reviewers. It publishes the two available x402 resources, exact Base USDC terms, Builder Code, the inventory BASE-XERP-INVENTORY-01 classification, and the fail-closed ERP boundary before any wallet connection or payment request.
GET /api/catbox-policy-evidence is the third x402 resource. It exposes the completed Base Sepolia CATBOX allowlist-only policy, the exact 100 CATBOX mint, and the verified 10 CATBOX burnWithMemo close event. The current testnet supply is 90 CATBOX and the burn memo hash binds BASE-LAB-B20-BURN-202608-001. It labels the lifecycle proof as testnet-only, keeps transfer ALWAYS_BLOCK, and never presents it as a mainnet asset, inventory valuation, payment, or ERP write.
- CATBOX burn transaction:
0xe1e478bbd25430d0d4f06683ae95e6f3999645995ddebc4afcc7918a003c8d40 - CATBOX closing supply:
90 CATBOX - Burn memo hash:
0x711378df7b1cac4d4588b62c0f9456481ab0913bb626cf57ae87db40ba9be6ba
All three paid resources declare the official x402 Bazaar discovery extension in their PAYMENT-REQUIRED response. That gives an agent catalog the HTTP method and a schema-backed example result without opening a wallet, changing the exact $0.01 USDC terms, or settling a request.
The same catalog now exposes its verified Base Mainnet evidence anchor: BASE-LAB-X402-CATALOG-20260727-001, transaction 0xd258fd6882499054e8ffd103c4ba2c09f8f79b0fede1dcf6ca1eaef78aa53fce, Registry 0x17fD9e593320461204887Bb2644e2F013FeF55bD, the catalog evidence root, and the existing InventoryRoot parent. This is a 0 ETH evidence-control call, not an x402 settlement, ERC-20 approval, or ERP write.
Talent's public BaseProofPay project showed 2 transactions, 2 DAU, and <0.0001 ETH gas fees on 2026-07-21. Both verified Base contracts and the public GitHub repository remain attached as data sources. The public aggregate does not expose transaction hashes, so those metrics are reported as platform indexing evidence rather than assigned to a specific canary.
Base.dev's Base App and Base Chain leaderboards still displayed a 2026-07-19 snapshot at the same review. BaseProofPay therefore waits for the documented refresh instead of generating another transaction.
independent-proof.html provides a separately disclosed Base Account flow for a genuine external user to send exactly 0.10 USDC to the GAYSON Base Account. It creates unique policy and payment IDs in the browser, requires atomic batch support, preflights balances, allowance, contract code and unused IDs, and postflights the full policy, receipt, balance deltas and zero residual allowance. It has no backend and makes no wallet request until the user clicks Connect. The payment is not an investment, token purchase, donation promise, or refundable deposit.
Do not submit private keys, seed phrases, API keys, wallet sessions, or confidential payment data. See SECURITY.md.