www.robbiegeorgephotography.com/v1/query/atomic/robbie-george-biography-plate
1.Catalog declaration
| Resource URL | https://www.robbiegeorgephotography.com/v1/query/atomic/robbie-george-biography-plate |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xb0d0207bcd46c6a7009ca5c8294177d79adc0807 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-30 01:02 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 7 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 438 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 101 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 269 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 201 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 169 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 688 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 182 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 357 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 93 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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.
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 mismatch- the response lacked 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-17 00:022026-09-17 00:02 UTC | settled (nonce-bound) | 200 | 0x372616e5…387b | 1001 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-10 07:022026-09-10 07:02 UTC | settled (nonce-bound) | 200 | 0x2899e442…b897 | 966 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-02 19:022026-09-02 19:02 UTC | settled (amount + payee) | 200 | 0x09aed26f…1420 | 803 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose 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/5ab23dce-b8c0-4bb0-ad3a-8eaee63eca46)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.