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

witness-controlled-testnet-v019.witness-test.workers.dev/v1/contract-witness

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://witness-controlled-testnet-v019.witness-test.workers.dev/v1/contract-witness
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:84532
Receiving address0x6f85ec53ab86618ec4a86b5c7da4252bb24c3867
Declared price (base units)1000
Catalog statusdelisted (since 2026-09-27 01:02 UTC)
First seen / last seen2026-08-28 01:12 UTC / 2026-09-26 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-042026-09-23
Figure 1. Probe timeline, last 7 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-23 10:30 UTCPOSTfail400225 msno_402
2026-09-19 11:24 UTCPOSTfail400345 msno_402
2026-09-17 11:24 UTCPOSTfail400218 msno_402
2026-09-12 11:24 UTCPOSTfail400292 msno_402
2026-09-09 11:24 UTCPOSTfail400236 msno_402
2026-09-05 11:24 UTCPOSTfail400184 msno_402
2026-09-04 11:24 UTCPOSTfail400360 msno_402

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-27delisted{"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.