trade.chainverdict.xyz/v1/gtin/prefix
1.Catalog declaration
| Resource URL | https://trade.chainverdict.xyz/v1/gtin/prefix |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xae2634e709c454f2720c65a0b2f9ba168e431842 |
| Declared price (base units) | 4000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | GET | pass | 402 | 277 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 537 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 542 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 387 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 415 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 490 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 511 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 494 ms | — |
| 2026-10-05 22:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 303 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-10-01 10:31 UTC | GET | pass | 402 | 357 ms | — |
| 2026-09-26 10:30 UTC | GET | pass | 402 | 194 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 419 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 312 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 216 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 141 ms | — |
| 2026-08-24 11:11 UTC | GET | fail | 402 | 117 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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 |
|---|---|---|---|---|
| 10-10 20:312026-10-10 20:31 UTC | settled (nonce-bound) | 200 | 0xdbcec5fc…0c0f | 7046 ms |
| 4000 units (≈ $0.004 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 10-03 00:012026-10-03 00:01 UTC | settled (nonce-bound) | 200 | 0xba33d8f8…5edb | 1802 ms |
| 4000 units (≈ $0.004 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/1ec2d7e1-70ba-444d-9b4c-e900b82dc15d)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.