Skip to content

Status and verification

Everything on this page is a historical record from the product repository, with its date. None of it is a current availability check, and this site made no payment to produce it. What each party can see is summarised in Who sees what.

Date Configuration Record
2026-10-31 Public Sepolia (eip155:11155111), self-run facilitator, one bounded run (T9) One payment by the unmodified client; delivery on the mined receipt; chain finality later; after a Provider restart, SIWX recovery of the same order with zero payment signatures; another wallet got 403.
2026-11-01 Public Sepolia (eip155:11155111), self-run facilitator, one bounded run (T10-H) The official approval hook: deny and mismatch gave zero signatures and zero settlements; allow gave one settlement and the body. Same recovery results as T9. The denied order answered 409.
2026-11-08 Base Sepolia (eip155:84532), capacity measurement New-order creation is serialized, about 9 s per order. This is a measurement, not a latency guarantee.
2026-11-09 Base Sepolia (eip155:84532), hosted multi-Provider configuration Switch to the hosted configuration, followed by one public purchase verifying relay, delivery and recovery 200.
2026-11-13 Base Sepolia (eip155:84532), hosted multi-Provider configuration The repository describes registration by invite, being opened in stages, with the operator path kept as the fallback. This describes the registration path; it is not a record of any registration.
2026-11-16 Base Sepolia (eip155:84532), hosted multi-Provider configuration The repository describes registration by application, and a facilitator price cap: each Provider prices its routes freely up to the cap, published as maxOrderAmount by GET /register/info. This describes the registration path and the price policy; it is not a record of any registration or payment.

The Sepolia rows are the repository’s historical records. The 2026-11-09 row is a switchover record, not sustained-operation or scale evidence. The 2026-11-13 and 2026-11-16 rows are dated descriptions of the registration path; the procedure is on Register and run a Provider (by application).

On the hosted testnet the facilitator operator sees, per order, the payer address, amount, transaction, digest and Provider. It holds only each Provider’s POS key: it can derive addresses, write that Provider’s lane, and know which addresses are the Provider’s. It cannot spend. It holds no seed and no view key. The Provider trusts the payTo the facilitator hands out at 402 time and audits afterwards with its own view key; the operator could still withhold orders, attribute an order to another Provider, or hand out an address that is not the Provider’s, and the audit finds this after the fact.

A self-run facilitator is a different configuration: its operator holds the merchant and broadcaster keys and sees the merchant wallet’s whole activity.

  • Availability or retention. The operator may pause, drain or reset the service and its state. Capacity is limited and the service may be paused or reset.
  • Delivery after a chain reorg of the payment. Delivery follows the mined receipt, not finality; a reorg or an ASP rejection can occur after delivery, so body delivery does not guarantee merchant credit or spendability. A slower finalized policy exists in the source; it is not available on the hosted testnet’s receipt-only path.
  • A guaranteed relay. Settlement is relayed to a delegated x402 facilitator, which broadcasts and pays gas; the relay is unguaranteed, and its terms and mainnet availability are unknown.
  • The Sepolia sample does not cover several payers, more orders, budget refills, monitoring or hosting.
  • Browser wallet signing and browser purchase-to-recovery are not verified.
  • Multi-instance deployment, Router integration, mainnet and a latency SLA are outside the sample’s verification scope; the sample states Router and SVM are out of its scope.
  • Real reorgs and sustained latency are not proven.
  • The hosted record adds one purchase at switchover, not sustained-operation or scale evidence.
  • Provider-only rage exit is unverified.
  • Merchant private-state mint and spendability were not observed in the documented Sepolia runs T9 and T10-H. The hosted-testnet record of 2026-11-09 confirms relay, delivery and recovery 200, and does not establish merchant private-state mint or spendability.

“Outside the verification scope” means nothing is claimed either way, now or for the future.

SubEtha is not intended to be a Sepolia-only service; we plan to extend to mainnet assets across chains supported by zERC20 v2, with integration and validation per chain and asset. The mainnet gates C1 (the Provider trusts the facilitator’s payTo, with after-the-fact audit), C2 (receipt-only delivery), C3 (settlement relayed to a delegated x402 facilitator without guarantees) and C12 (Provider-only rage exit unverified) are open. No date is promised.

The v2 Provider extension is the ./x402 entry of @subetha/provider 0.2.0. That version, with @subetha/x402-scheme 0.2.0 and the Provider tools @subetha/provider-tools 0.1.0, is installed from the npm registry at exactly those versions; @subetha/provider 0.1.0 is the V1 package and has no ./x402 subpath. The v2 facilitator and adapter are private workspace packages; source access is an authorized checkout of the private repository, provided to design partners on request. The three versions carry no npm provenance attestation. Approved applicants also receive them as package tarballs with the invite code, and every copy is checked against the integrity values listed on the registration guide.

SubEtha-authored code is Apache-2.0. The zERC20 v2 SDKs are installed from npm under their own terms. The repository grants no commercial-use rights, public-hosting rights or official status for any zERC20 component. Production-use permission is not established by the evidence. This offering is framed as testnet design-partner work.

Router integration with SubEtha v2 is outside the verification scope of the documented path, and no integration or roadmap promise is made; see SubEtha and the Router.

Reviewed 2026-11-16 against the product repository at e972064; re-read on 2026-11-18 against 68e061b, which changes only the quickstart’s and the operations notes’ funding and probe text. Evidence is the product repository’s own records; this site made no payment for this page.