scvd.store/api/buy/luckies
1.Catalog declaration
| Resource URL | https://scvd.store/api/buy/luckies |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xdd350976b8cffc65938c0464d39a2c78be079bd0 |
| Declared price (base units) | 990000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 9 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 1040 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 504 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 182 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 386 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 280 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 498 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 2277 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 2877 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 382 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 256 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 112 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 323 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 570 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 215 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 293 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 1640 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 1229 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 382 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 386 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 331 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-26 12:022026-09-26 12:02 UTC | settled (nonce-bound) | 200 | 0xf70c7561…0117 | 8254 ms |
| 990000 units (≈ $0.99 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-12 18:002026-09-12 18:00 UTC | settled (nonce-bound) | 200 | 0x1421cddc…85f6 | 7390 ms |
| 990000 units (≈ $0.99 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-05 19:002026-09-05 19:00 UTC | settled (nonce-bound) | 200 | 0xf3dabf7a…454c | 5001 ms |
| 990000 units (≈ $0.99 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/51a5d60a-2bbf-4d26-8f0f-c1dab3d6e8eb)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-12T18:00:50Z (UTC). The form starts with that time; add what you saw instead.