Claims you can inspect.

Browse Pump.fun pairing assets, then inspect native Pump coins paired against a selected mint, with source coverage, verified creation times and estimated valuations. Public reads require no wallet, authentication or funds.

Evidence compiled 1 November 2026, 16:52:51 UTC; this is not a market capture. Version 0.1.0. Runtime source revision: a166a09f6e92006adf13f3ae0a0f2a3e6015647f. Source is in an access-controlled repository; identity alone does not certify artifact behavior.

Release boundary: this page belongs to the Pump pairing-directory release. The runtime revision above identifies the source reported by this running service. Local HTTP, browser and live-feed acceptance was recorded against 564fd94bb91f11706bc0948d9eeec9ba12486e1b; local and hosted observations are separate evidence. The earlier Railway recovery at eadbf4c49185ae0335c4a805bbf90e7c74c16285 verifies generic discovery only.

Try the main flow

1. Open the pairing-asset directory. Inspect source scope, catalog/count capture times and partial coverage. Pending counts are not zero.
2. Search NVDA. The xStocks mint Xsc9qvGR1efVDFGLrVsmkzv3qi45LTBjeUKSPmx9qEh and separate Backpack-logo mint NVDAVuiB7hwd3m5Wa1JuHNovPaPG6BH1QNztbKFxNjv must stay distinct despite their ticker.
3. Open xStocks NVIDIA children. Native counts cover current Pump curves, including completed curves once. Sort by estimated cap (FDV) or Newest; inspect stage, source and coverage labels. These are not lifetime or website totals.
4. Inspect directory JSON and newest JSON. Compare a creation signature with its mainnet transaction; first observation cannot establish creation.
5. Malformed quote mint, unsupported sort and invalid pagination must reject. Unknown counts/prices stay unavailable. Provider rejection must not turn into zero or a different source population.

Pump views refresh every 60 seconds; the worker warms counts and consumes free creation hints. Neither policy guarantees continuous delivery. RPC quotas, disconnects, closed accounts and bounded history leave gaps. Failures expose warnings, stale/pending/unavailable values or retryable errors. The identity catalog is not a frozen market feed.

Evidence for advertised capabilities

P1–P2 · Pairing identities and native counts

Claim: all 227 identities from the official creation selector captured at 2026-11-01T16:04:47.539Z remain visible: SOL, USDC and 225 custom quotes; native mode verifies QuoteControl membership. Observed: local adapter capture at 16:29:44.490 UTC returned 227 assets, two known directory counts and incomplete coverage. Current native xStocks NVIDIA count was 10,038; the separate NVIDIA mint was 172, at curve slot 464159590. These are dated observations, not current constants. Control: mint identity stays distinct; unknown stays null. Evidence: catalog, native provider and presentation regressions; private research archive live-adapter-result.json. Limits: closed/historical curves, dynamic secondary-quote eligibility and legacy SOL totals are not exhaustively indexed.

The optional pump-listed population is different. Ordinary official-feed server requests returned HTTP 403 locally and from Railway. This scope reports unavailable data; it never silently substitutes native counts. Blocked inspection is not evidence of zero coins.

P3 · Child coins and estimated FDV

Claim: native curves and verified canonical graduated PumpSwap pools can receive estimated total-supply FDV in the pairing asset. Observed: the dated adapter capture returned graduated Clout at 150.26135002 NVDAX and Microduck at 118.02937736, using canonical reserve/mint-supply snapshots; USD values and some creation dates remained unavailable. Control: unrelated token accounts, bad pool identities/vaults and missing reserve groups cannot supply valuations. Evidence: native curve and canonical AMM adapters, corresponding regressions and common-context read archives. Limits: reserve-ratio FDV is not circulating market cap, a swap quote or underlying NVIDIA share value. Missing values remain unknown.

P4 · Newest verified creation subset

Claim: Newest uses actual successful Pump-owned CreateEvent times among the bounded index. Observed: Alien Inu mint 2qp2TrXggB8ieabW6yDXkbsaEHzrAY1cdBhzHLLhpump had verified creation time 2026-11-01T15:42:23Z, slot 464146411, in this successful mainnet transaction. Review only read the transaction. Control: failed/spoofed events, mismatched identities and oldest-signature assumptions do not establish creation. Evidence: variable-length event decoder, ingestion/history regressions and raw transaction archive. Limit: one verified result proves neither full history nor globally newest delivery.

P5 · Free hints and worker lifecycle

Claim: the local worker uses one keyless PumpPortal creation subscription as untrusted hints, then verifies confirmed chain events. No paid token/account trade stream is used. Observed source: a separate probe from 16:30:47.900 to 16:31:23.006 UTC received six creation hints; these are not six verified creations. The probe also requested free migration notifications; product code subscribes only to creation. Control: malformed/oversized messages, duplicates, queue overflow and failed/unavailable transaction evidence have deterministic handling. Evidence: worker and ingest code, module regressions and private pumpportal-probe.json. Limits: final integrated acceptance is recorded separately; disconnects and no deterministic replay leave gaps. WatchLarp was a pattern reference; its current Shrine use proves no Pairwatch integration and no credentials were copied.

Verification by environment

• Unit/API: module reports record focused Pump checks. Final integrated candidate checks are recorded separately after execution. Historical 1 November evidence/transport candidate passed 129 tests in 22 files, typecheck, source guard, webpack build, both smoke modes and audit. That earlier candidate does not certify Pump changes. Fixture-based smoke is local behavior evidence.
• Local validator: unverified; no execution or receipts supplied.
• External read-only: local native adapter and free-source captures above are distinct from Railway. Recovery production checks at 15:52:09.6823557–15:52:11.3674630 UTC observed homepage/readiness 200, SOL 200 with 615 indexed pools, malformed mint 400 and private wallets 403. This verified generic discovery only. Current Orca-specific notifications remain unverified; October combined messages prove no Orca callback.
• Funded live transactions: unverified; no purchase, sale or withdrawal receipt/state change supplied or performed for this review. Quotes, paper fills, signing and submission are not settlement.

Earlier default Turbopack traversal was blocked by an external dependency junction; webpack passed. This tooling limitation differs from an observed application failure. Reachability/readiness alone do not prove the main outcome. Source/configuration/deployment changes require fresh checks.

Local tools, ownership and affiliations

The secondary Solana pool explorer reads partial venue indexes; its pool counts are not Pump coin counts. Hosted public-only mode denies every private API and disables private strategies. Encrypted wallets, authorization, quotes and paper mode require the local terminal. Local custody/signing implementations do not establish funded settlement.

Reads use Solana mainnet-beta. No Pairwatch token, mint, distribution, vesting, liquidity lock, fee allocation or utility is supplied or claimed. Imported token/issuer/provider metadata does not establish authenticity, ownership or partnership. No independently confirmed affiliation, public maintainer identity/contact or evaluator report/score is supplied. Source is private.

Authorized repository users can inspect docs/EVIDENCE.md, docs/CLAIM-AUDIT.md and docs/VERIFICATION.md for exact inputs, code paths, captures and remaining limits, and submit corrections through the repository. Public contact remains unverified. See coverage and risk disclosures.