realestate.lonestaroracle.xyz/report
1.Catalog declaration
| Resource URL | https://realestate.lonestaroracle.xyz/report |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x52ab53912d37759b2ad364f22dd06b16714b6c06 |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 7 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 13:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 432 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 240 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 58 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 53 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 261 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 42 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 58 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 122 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 49 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 134 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 45 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 2069 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 61 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 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 |
|---|---|---|---|---|
| 09-17 18:022026-09-17 18:02 UTC | settled (nonce-bound) | 200 | 0x39a419c3…bb4d | 1308 ms |
| 30000 units (≈ $0.03 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-11 01:012026-09-11 01:01 UTC | settled (nonce-bound) | 200 | 0xd8aa7c9d…f294 | 1336 ms |
| 30000 units (≈ $0.03 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-02 19:012026-09-02 19:01 UTC | settled (amount + payee) | 200 | 0xa2b64421…9feb | 1298 ms |
| 30000 units (≈ $0.03 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/ff984c1e-e3b2-494f-8313-edd95600b7a2)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.