crypto.openverbs.com/v1/news
1.Catalog declaration
| Resource URL | https://crypto.openverbs.com/v1/news |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xb3f4de103f34b99f0da19b4f16d6b53a14c2194a |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-09-11 01:03 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | POST | pass | 402 | 120 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 338 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 529 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 67 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 2039 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 244 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 594 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 78 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 182 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 88 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 303 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 56 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 628 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 235 ms | — |
| 2026-09-15 11:24 UTC | POST | pass | 402 | 161 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 356 ms | — |
| 2026-09-11 11:24 UTC | POST | fail | 402 | 126 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
0 of 1 paid attempts settled with a receipt, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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
settle_failed- vet402 signed a payment and got no settlement receipt back.
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.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-19 12:072026-09-19 12:07 UTC | settle_failed | 502 | — | 799 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
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.
About the purchase at 2026-09-19T12:07:56Z (UTC). The form starts with that time; add what you saw instead.