cyre.dev/api/lockbox
1.Catalog declaration
| Resource URL | https://cyre.dev/api/lockbox |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | 9iubApKktcxphCVgBg9CPRPhSH8nkzVRSapxhYwxfCVS |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-31 01:03 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 2082 ms | — |
| 2026-10-18 16:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 474 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 563 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-10-04 10:30 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-27 10:31 UTC | GET | pass | 402 | 126 ms | — |
| 2026-09-23 10:30 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 36 ms | — |
| 2026-09-17 11:24 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-04 11:24 UTC | GET | pass | 402 | 44 ms | — |
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-17 21:302026-10-17 21:30 UTC | settled (nonce-bound) | 200 | gFeCHSGgKM…2cBU | 1586 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 10-11 20:302026-10-11 20:30 UTC | settled (nonce-bound) | 200 | 2md6SuapWx…LYK2 | 1436 ms |
| 2000 units (≈ $0.002 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/4ff1ecdb-773f-488f-8595-4f1b3d80448a)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-03 | relisted | {"status":"delisted"} | {"status":"active"} |
| 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.