vedetta.dethboy.com/v1/screener
1.Catalog declaration
| Resource URL | https://vedetta.dethboy.com/v1/screener |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x21e16f1bc3aa847236354c8193d0cb21cf412efa |
| Declared price (base units) | 30000 |
| Catalog status | delisted (since 2026-09-30 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 13:40 UTC | GET | pass | 402 | 646 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 477 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 2522 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 491 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 643 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 587 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 507 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 532 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 454 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 497 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 655 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 717 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 599 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 715 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 576 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 659 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 747 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 705 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 521 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 611 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 2344 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 828 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 536 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 488 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 704 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 898 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 2358 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 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 |
|---|---|---|---|---|
| 09-03 07:022026-09-03 07:02 UTC | settled (amount + payee) | 200 | 0x21620f56…2940 | 2598 ms |
| 30000 units (≈ $0.03 USDC) · L2 matchWhose 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/9abb32b7-2cc8-4987-929b-a64eccf5e447)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-30 | 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.