chainverdict.xyz/v1/data/block
1.Catalog declaration
| Resource URL | https://chainverdict.xyz/v1/data/block |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xae2634e709c454f2720c65a0b2f9ba168e431842 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 6 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | GET | pass | 402 | 315 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 485 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 556 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 367 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 344 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 2207 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 399 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 2353 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 376 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 192 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 525 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 174 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 611 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 322 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 157 ms | — |
| 2026-08-20 10:50 UTC | GET | fail | — | 10003 ms | timeoutNo response headers arrived within 10 seconds. |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 no_declaration- the listing declares no output schema to check the response against.
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-26 00:012026-09-26 00:01 UTC | settled (nonce-bound) | 200 | 0xc55a50b1…7cfc | 2100 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-19 18:012026-09-19 18:01 UTC | settled (nonce-bound) | 200 | 0x1b1bae04…2129 | 1712 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-13 00:002026-09-13 00:00 UTC | settled (nonce-bound) | 200 | 0x2a9c0e18…169a | 1546 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/61156b01-4389-4efb-8aff-c25fbf2f8dce)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.
About the purchase at 2026-09-19T18:01:35Z (UTC). The form starts with that time; add what you saw instead.