shelf.thirdmade.net/probe/pii-guard
1.Catalog declaration
| Resource URL | https://shelf.thirdmade.net/probe/pii-guard |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x315708415764b7f2b783714ce82cf9c628e33fcf |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-31 01:03 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-13 10:31 UTC | POST | pass | 402 | 292 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 908 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 951 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 1053 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 626 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 494 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 427 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 2327 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 584 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 747 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 592 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 447 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 459 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 399 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 474 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 401 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 822 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 418 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 320 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 522 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 701 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 500 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 512 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 284 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 469 ms | — |
| 2026-09-12 13:40 UTC | POST | pass | 402 | 328 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 2660 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 676 ms | — |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 119 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 147 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 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-07 19:012026-09-07 19:01 UTC | settled (nonce-bound) | 200 | 0x5b5ac21e…75e8 | 1310 ms |
| 1000 units (≈ $0.001 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/53478b9c-15eb-4440-87a9-d95cc6517690)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-09 | 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.