wallet-sanctions.use.x402atlas.com/exposure
1.Catalog declaration
| Resource URL | https://wallet-sanctions.use.x402atlas.com/exposure |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x8c128f1ee62bb5e47867cfbae2ad89be325df1b2 |
| Declared price (base units) | 100000 |
| Catalog status | active |
| First seen / last seen | 2026-08-16 01:06 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 122 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 316 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 237 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 2110 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 65 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 200 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 33 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 305 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 1967 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 21 ms | — |
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 match- the response had the 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-05 19:012026-09-05 19:01 UTC | settled (nonce-bound) | 200 | 0x1741ac4f…adaf | 1362 ms |
| 100000 units (≈ $0.10 USDC) · L2 matchWhose 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/c780c815-eea3-48dc-9200-d0b799e29bc1)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.