proxy.suverse.io/v1/data/suverse-crypto-market-rankings
1.Catalog declaration
| Resource URL | https://proxy.suverse.io/v1/data/suverse-crypto-market-rankings |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x260fbe1ec46968ee02e5b972507d7bb7f09f82b0 |
| Declared price (base units) | 50000 |
| Catalog status | delisted (since 2026-09-25 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-24 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-23 22:40 UTC | POST | pass | 402 | 356 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 117 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 279 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 312 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 713 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 345 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 323 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 314 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 348 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 582 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 678 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 362 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 588 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 2420 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 561 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 2373 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 507 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 279 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 887 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 754 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 233 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 299 ms | — |
| 2026-09-09 14:40 UTC | POST | pass | 402 | 689 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 392 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 389 ms | — |
| 2026-09-07 17:40 UTC | POST | pass | 402 | 400 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 159 ms | — |
| 2026-09-06 17:40 UTC | POST | pass | 402 | 873 ms | — |
| 2026-09-06 05:40 UTC | POST | pass | 402 | 364 ms | — |
| 2026-09-05 17:40 UTC | POST | pass | 402 | 766 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
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 |
|---|---|---|---|---|
| 08-25 12:542026-08-25 12:54 UTC | settled (amount + payee) | 200 | 0xf2298a60…1fb7 | 1888 ms |
| 50000 units (≈ $0.05 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/6d691518-d258-47d5-b538-c78ac6eec502)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-25 | delisted | {"status":"active"} | {"status":"delisted"} |
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.