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

csno.cc/api/csno/chips

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://csno.cc/api/csno/chips
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x267c2b764064a90cf779b2e645a144ab12e82ee5
Declared price (base units)100000
Catalog statusdelisted (since 2026-09-26 01:02 UTC)
First seen / last seen2026-08-27 01:15 UTC / 2026-09-25 01:02 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-09-062026-09-25
Figure 1. Probe timeline, last 30 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-25 22:40 UTCPOSTfail402453 msmetadata_mismatch
2026-09-25 04:40 UTCPOSTfail402257 msmetadata_mismatch
2026-09-24 13:40 UTCPOSTfail402313 msmetadata_mismatch
2026-09-23 16:40 UTCPOSTfail402276 msmetadata_mismatch
2026-09-22 22:40 UTCPOSTfail402384 msmetadata_mismatch
2026-09-22 04:40 UTCPOSTfail402250 msmetadata_mismatch
2026-09-21 13:40 UTCPOSTfail402229 msmetadata_mismatch
2026-09-20 16:40 UTCPOSTfail402456 msmetadata_mismatch
2026-09-19 22:40 UTCPOSTfail402213 msmetadata_mismatch
2026-09-19 13:40 UTCPOSTfail402234 msmetadata_mismatch
2026-09-18 16:40 UTCPOSTfail402331 msmetadata_mismatch
2026-09-17 22:40 UTCPOSTfail402228 msmetadata_mismatch
2026-09-17 04:40 UTCPOSTfail402239 msmetadata_mismatch
2026-09-16 16:40 UTCPOSTfail402368 msmetadata_mismatch
2026-09-15 16:40 UTCPOSTfail402236 msmetadata_mismatch
2026-09-15 04:40 UTCPOSTfail402258 msmetadata_mismatch
2026-09-14 13:40 UTCPOSTfail4022221 msmetadata_mismatch
2026-09-13 16:40 UTCPOSTfail402231 msmetadata_mismatch
2026-09-13 04:40 UTCPOSTfail402270 msmetadata_mismatch
2026-09-12 16:40 UTCPOSTfail402276 msmetadata_mismatch
2026-09-11 22:40 UTCPOSTfail4021346 msmetadata_mismatch
2026-09-11 13:40 UTCPOSTfail402237 msmetadata_mismatch
2026-09-10 23:40 UTCPOSTfail402538 msmetadata_mismatch
2026-09-10 05:40 UTCPOSTfail402272 msmetadata_mismatch
2026-09-09 17:40 UTCPOSTfail402934 msmetadata_mismatch
2026-09-09 05:40 UTCPOSTfail402233 msmetadata_mismatch
2026-09-08 14:40 UTCPOSTfail4021123 msmetadata_mismatch
2026-09-07 23:40 UTCPOSTfail402546 msmetadata_mismatch
2026-09-07 14:40 UTCPOSTfail402427 msmetadata_mismatch
2026-09-06 23:40 UTCPOSTfail402316 msmetadata_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-26delisted{"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.