wallet.lonestaroracle.xyz/score
1.Catalog declaration
| Resource URL | https://wallet.lonestaroracle.xyz/score |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x52ab53912d37759b2ad364f22dd06b16714b6c06 |
| Declared price (base units) | 150000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | GET | pass | 402 | 408 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 532 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 621 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 457 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 335 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 110 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 331 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 144 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 2053 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 234 ms | — |
| 2026-10-01 10:30 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-25 10:31 UTC | GET | pass | 402 | 245 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 65 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 40 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 48 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 112 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 92 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
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 (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-02 09:302026-10-02 09:30 UTC | settled (nonce-bound) | 200 | 0xb88b70f7…16d7 | 4837 ms |
| 150000 units (≈ $0.15 USDC) · L2 no_declarationWhose 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/230b432a-f80c-43fa-8d9f-a00f28e99450)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.