svm402.com/discover
1.Catalog declaration
| Resource URL | https://svm402.com/discover |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | 4ofUMGcRHsfr6LMY6AuaRSQpqyKsvibSbXmieQL4i8Dc |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 804 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 10:31 UTC | POST | pass | 402 | 836 ms | — |
| 2026-09-28 10:30 UTC | POST | pass | 402 | 331 ms | — |
| 2026-09-23 10:31 UTC | POST | pass | 402 | 424 ms | — |
| 2026-09-19 11:24 UTC | POST | pass | 402 | 331 ms | — |
| 2026-09-17 11:24 UTC | POST | pass | 402 | 425 ms | — |
| 2026-09-13 11:24 UTC | POST | pass | 402 | 279 ms | — |
| 2026-09-09 11:24 UTC | POST | pass | 402 | 259 ms | — |
| 2026-09-05 11:24 UTC | POST | pass | 402 | 294 ms | — |
| 2026-08-14 08:53 UTC | POST | pass | 402 | 80 ms | — |
3.L1 — real purchases
0 of 3 paid attempts settled on-chain, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
delivered_no_receipt- the paid request answered 2xx without a settlement receipt.
L2 no_declaration- the listing declares no output schema to check the response against.
L2 mismatch- the response lacked fields the listing's output schema declares.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-17 12:522026-09-17 12:52 UTC | delivered_no_receipt | 200 | — | 815 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: not sorted: no charge | ||||
| 08-30 12:072026-08-30 12:07 UTC | delivered_no_receipt | 200 | — | 842 ms |
| 20000 units (≈ $0.02 USDC) · L2 mismatchWhose side: not sorted: no charge | ||||
| 08-23 12:432026-08-23 12:43 UTC | delivered_no_receipt | 200 | — | 1050 ms |
| 20000 units (≈ $0.02 USDC) · L2 mismatchWhose side: not sorted: no charge | ||||
4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.