piano-refugees-coupons-experienced.trycloudflare.com/api/base-status-query-v8
1.Catalog declaration
| Resource URL | https://piano-refugees-coupons-experienced.trycloudflare.com/api/base-status-query-v8 |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x34b3e42d1f758ca31ded6f1b00d205ddff531827 |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-08-20 01:30 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-08-19 01:34 UTC |
| Catalog-reported calls / payers (30d) | 3 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-08-14 08:53 UTC | GET | pass | 402 | 439 ms | — |
3.L1 — real purchases
0 of 1 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 match- the response had the 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-14 10:082026-08-14 10:08 UTC | delivered_no_receipt | 200 | — | 594 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: not sorted: no charge | ||||
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-20 | 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.