workbot1.oddsys.org/verify-sig
1.Catalog declaration
| Resource URL | https://workbot1.oddsys.org/verify-sig |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x15459498e1191d8787c83177809bd54022fa18c4 |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-09-17 12:35 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | POST | pass | 402 | 728 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 1283 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 756 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 954 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 921 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 833 ms | — |
| 2026-09-24 10:30 UTC | POST | pass | 402 | 464 ms | — |
| 2026-09-20 11:24 UTC | POST | pass | 402 | 478 ms | — |
| 2026-09-17 12:35 UTC | POST | pass | 402 | 360 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 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
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-25 00:012026-09-25 00:01 UTC | settled (nonce-bound) | 200 | 0x046bc3e4…99cb | 3290 ms |
| 2000 units (≈ $0.002 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/33dd3a0c-8f3d-46a2-a6ac-0ef85389e3fe)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-25T00:01:57Z (UTC). The form starts with that time; add what you saw instead.