Verification

Updated 22 September 2026. The current product is TRIDENT holder access through the shared OpenRouter treasury. Token registration and public token/pool creation are retired.

Automated checks

The latest implementation passes TypeScript, the production build, 63 unit/integration tests, 70 HTTP checks and 56 checks against isolated PostgreSQL 17 databases in GitHub Actions. Tests cover wallet signatures, versioned consent, nonce replay, origin protection, real-balance gating, hashed keys, shared-credit concurrency, streaming, settlement and reconciliation.

Live production checks

Production verifies PostgreSQL connectivity, the configured OpenRouter inference key and its credit-read permission. The account returned USD 50 in purchased credit and USD 49.997429 remaining at the latest recorded test time. A real bounded operator request completed using openai/gpt-4o-mini, recording USD 0.000008 after integer-microdollar rounding. It appears separately from holder activity. RPC independently verifies Robinhood Chain 4663, the TRIDENT contract, Pons factory registration and wallet token balances.

An ephemeral non-holder QA wallet signed the real policy-bearing challenge. The database recorded current-version acceptance, a replayed signature was rejected, the wallet's confirmed zero balance was read, and API key creation and inference correctly returned HTTP 403. The current policy exposes a USD 1 daily budget, 100 daily requests, 20 attempts per minute and two concurrent requests shared across keys. Logout invalidated the session and removed it from the active count. Public analytics exposed no wallet address.

The built-in access policy initializes automatically. No user token registration, deposit or budget-allocation step was needed. Historical signed-in counts include QA accounts; active counts reflect recent authenticated sessions, including any concurrent users.

Interface checks

The deployed homepage, API access, treasury, terms and privacy pages were inspected in the browser. The catalogue loaded 601 published models at the observation time. Wallet choices are disabled until the initially unchecked policy agreement is selected. The signed message records policy version 2026-09-22.3 and its memecoin disclosure.

The screenshots show the deployed application, not a generated mockup. A real wallet extension was not paired in that browser.

Market-data scope

The original random-token check retrieved public UBIK observations from Pons. The current project profile uses the supplied TRIDENT CA. RPC-verified token identity and wallet holdings are separate from indexed market-price observations. An indexed fallback remains labelled and cannot satisfy an access check.

Remaining live checks

Paid production inference from an eligible holder and live WalletConnect pairing have not been executed. Eligible-holder key use, streaming and accounting pass controlled provider tests. No mainnet token launch, pool creation, transfer or creator-fee collection occurred.

To complete a funded-holder acceptance check, connect an eligible wallet, accept the policies, create a key, run one bounded request, compare its provider cost with the recorded settlement, then revoke the key. No new token, user deposit or separate allocation is required. There is no claimed automatic conversion of creator fees into provider credits.

The repository's VERIFICATION.md, docs/holder-verification.json and docs/privacy-limits-verification.json retain the detailed results and limitations.

Privacy and wallet-limit checks

Public deployment documentation no longer links an operator account. The token API omits the deployer wallet, including when a cached response is served. Public status uses only the project contact. Scans of application source, public docs, assets and client bundles found no operator name, location, personal email or personal account link. PNG assets contain no text or EXIF metadata. Historical blockchain records and third-party caches remain outside the application’s control.

Tests cover parallel wallet reservations, budget sharing across keys and browser requests, daily resets, carried-over uncertain costs, zero-cost requests, key rotation and creation caps, recent token transfers, RPC failures and rejection of legacy token policies. Treasury views refresh every 15 seconds and after playground use. The one-time production check runs only as a private operator script; its temporary build invocation was removed after success.

Holder client compatibility repair

Production logs on 22 September showed repeated HTTP 400 and 413 responses from Chat Completions. The gateway previously accepted only a small plain-text schema and a 32 KB body. The repair accepts standard text/function-tool request shapes, content arrays, tool results, output-limit aliases, structured output and streaming options, with a 1 MiB body cap. Output remains capped at 4,096 tokens, and tool instructions count toward cost reservations. Provider price ceilings are rounded upward so floating-point arithmetic cannot exclude a provider at the published tariff.

Seven additional authenticated API tests exercise real wallet signature verification and key issuance against controlled chain/provider responses, then run a request above 32 KB, tool-result streaming, accounting settlement, CORS, alias routing and negative holder/budget tests. All 70 local tests and TypeScript pass. These controlled tests do not claim that an independent holder’s production key was used. Live provider credentials and funds were healthy before the repair; deployment and HTTP checks are verified separately.