library.proofivy.com/cryptoslate
1.Catalog declaration
| Resource URL | https://library.proofivy.com/cryptoslate |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x859af250df0b68bfd0768ca22142a1afa0abeaf4 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 22:40 UTC | POST | pass | 402 | 121 ms | — |
| 2026-10-18 04:40 UTC | POST | pass | 402 | 131 ms | — |
| 2026-10-16 21:40 UTC | POST | pass | 402 | 27 ms | — |
| 2026-10-15 12:40 UTC | POST | pass | 402 | 61 ms | — |
| 2026-10-14 03:40 UTC | POST | pass | 402 | 59 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 402 ms | — |
| 2026-10-11 15:40 UTC | POST | pass | 402 | 2029 ms | — |
| 2026-10-10 15:40 UTC | POST | pass | 402 | 112 ms | — |
| 2026-10-09 15:40 UTC | POST | pass | 402 | 174 ms | — |
| 2026-10-08 13:40 UTC | POST | pass | 402 | 208 ms | — |
| 2026-10-07 13:40 UTC | POST | pass | 402 | 190 ms | — |
| 2026-10-06 13:40 UTC | POST | pass | 402 | 267 ms | — |
| 2026-10-04 22:40 UTC | POST | pass | 402 | 230 ms | — |
| 2026-10-04 04:40 UTC | POST | pass | 402 | 109 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 86 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 265 ms | — |
| 2026-10-01 16:40 UTC | POST | pass | 402 | 128 ms | — |
| 2026-09-30 22:40 UTC | POST | pass | 402 | 57 ms | — |
| 2026-09-30 04:40 UTC | POST | pass | 402 | 206 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 196 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 110 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 171 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 447 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 178 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 139 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 304 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 87 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 18 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 41 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 55 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 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
L2 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
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 15:282026-09-17 15:28 UTC | settled (nonce-bound) | 200 | 0xcece082b…345b | 1015 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered) | ||||
| 09-11 12:092026-09-11 12:09 UTC | settled (nonce-bound) | 200 | 0x807e31bc…fc0c | 941 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-02 12:092026-09-02 12:09 UTC | settled (amount + payee) | 200 | 0xe23f6ed9…9dca | 958 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose 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/42505720-dcd3-4638-b7cb-645700fe87ad)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-18 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-17 | 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.