Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-29 · 4 days ago

api.carbon-cashmere.de/v1/btc-derivatives/mempool-pressure

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.carbon-cashmere.de/v1/btc-derivatives/mempool-pressure
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xf8b2dd46542175ad46e14e6133340e652665f2ee
Declared price (base units)20000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-08-262026-09-29
Figure 1. Probe timeline, last 8 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-29 10:31 UTCGETpass402523 ms—
2026-09-24 10:30 UTCGETpass402516 ms—
2026-09-20 11:24 UTCGETpass402474 ms—
2026-09-17 11:24 UTCGETpass402464 ms—
2026-09-13 11:24 UTCGETpass402487 ms—
2026-09-10 11:24 UTCGETpass402407 ms—
2026-09-03 11:24 UTCGETpass402140 ms—
2026-08-26 10:33 UTCGETfail402209 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

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. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-10relisted{"status":"delisted"}{"status":"active"}
2026-09-08delisted{"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.

20–2,000 characters · 0 so far