trade.chainverdict.xyz/v1/container/validate
1.Catalog declaration
| Resource URL | https://trade.chainverdict.xyz/v1/container/validate |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog 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-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-21 13:40 UTC | GET | pass | 402 | 475 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 553 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 266 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 395 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 445 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 174 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 338 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 790 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 898 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 699 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 783 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 415 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 335 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 149 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 452 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 278 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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 | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-04 01:012026-09-04 01:01 UTC | settled (amount + payee) | 200 | 0xd30e2ab2…6655 | Base | 1571 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 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/63ce29f5-e29b-476a-8e08-c46e9d05fc4f)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-28 | 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.