Verification and remaining live gates

Automated checks

The project provides TypeScript checking, unit tests, a production build and HTTP smoke checks. Tests cover wallet signatures and nonce replay, receipt reuse, origin protection, accounting reservations, unknown-cost holds, reconciliation, key hashing/revocation, shared wallet allowances and native-v4 pool arithmetic.

See VERIFICATION.md at the repository root for the final run results. Tests use isolated databases and ephemeral test keys. They do not fund or sign mainnet transactions.

Live Pons read

On 22 September 2026, the read-only indexed test retrieved the public Pons page for UBIK, checked its address-scoped identity and parsed numeric supply and GLD-quoted price. The source displayed a degraded-performance notice. The result is retained in docs/live-verification.json with its retrieval timestamp.

Direct Robinhood RPC requests from this environment timed out. Therefore this is evidence of a working indexed-data integration, not evidence of successful confirmed onchain reads. The app labels that distinction and keeps indexer data out of eligibility and accounting decisions.

Current public flow

The product connects existing tokens. New token and pool creation routes are retired and return HTTP 410. Older adapter tests document reference code, not an available minting feature.

Mainnet transactions not executed

No wallet-funded token launch, pool deposit, creator-fee claim or community contribution was executed during this build. No private signing key was provided. Simulation and calldata tests do not replace a funded mainnet smoke test.

A funded provider account was not connected, so no paid inference call was made. Community gateway tests can verify mocked provider accounting and streaming behavior without proving a particular provider's live availability or permission for commercial resale.

Production acceptance sequence

Use an existing token and a small bounded amount from an operator-controlled wallet. Verify its network and address before registration.

Register the existing token community, check a holder and a non-holder, contribute a small amount, top up the provider account and allocate it. Issue and revoke a test key. Run short non-streaming and streaming requests; compare actual provider charges, community balance and wallet allowance. Exercise interrupted-request reconciliation before increasing budgets.

Use the actual production RPC and database. A test against one public Pons sample does not validate every token implementation, pool phase or quote asset. Tokenized assets, transfer restrictions and unusual token behavior need their own checks.

Interface evidence

Static images of rendered components demonstrate layout only. They are not browser interaction, wallet or paid-provider test evidence. The cloud browser available during this build cannot access this workspace's localhost; no claim of full end-to-end browser validation is made on that basis.