Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-23 · 3 days ago
vet402Back to the registerMethodology

onchain-toolkit.bowling-anthony.workers.dev/tx

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://onchain-toolkit.bowling-anthony.workers.dev/tx
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x1831f336585a6c67b6a954d28f3e07f44c4eebbd
Declared price (base units)1000
Catalog statusdelisted (since 2026-09-24 01:02 UTC)
First seen / last seen2026-08-25 01:58 UTC / 2026-09-23 01:02 UTC
Catalog-reported calls / payers (30d)5 / 1

2.Probe history

2026-09-042026-09-23
Figure 1. Probe timeline, last 12 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-23 16:40 UTCGETfail4022386 msprice_mismatch
2026-09-22 22:40 UTCGETfail402357 msprice_mismatch
2026-09-22 04:40 UTCGETfail402371 msprice_mismatch
2026-09-21 13:40 UTCGETfail402130 msprice_mismatch
2026-09-20 16:40 UTCGETfail402257 msprice_mismatch
2026-09-19 22:40 UTCGETfail40297 msprice_mismatch
2026-09-19 11:24 UTCGETfail40254 msprice_mismatch
2026-09-17 11:24 UTCGETfail402100 msprice_mismatch
2026-09-12 11:24 UTCGETfail402102 msprice_mismatch
2026-09-09 11:24 UTCGETfail40212 msprice_mismatch
2026-09-05 11:24 UTCGETfail402102 msprice_mismatch
2026-09-04 11:24 UTCGETfail402129 msprice_mismatch

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-24delisted{"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.