Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago

stablefinance.dev/api/earnings

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://stablefinance.dev/api/earnings
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xbd17480bf6ff056f7b91d9adc9dfda001eb7283d
Declared price (base units)20000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-142026-10-19
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-10-19 13:40 UTCGETpass402196 ms—
2026-10-17 22:40 UTCGETpass402292 ms—
2026-10-16 15:40 UTCGETpass402306 ms—
2026-10-01 10:30 UTCGETpass402103 ms—
2026-09-25 10:31 UTCGETpass402181 ms—
2026-09-21 11:24 UTCGETpass40245 ms—
2026-09-17 16:19 UTCGETpass40268 ms—
2026-09-14 11:24 UTCGETpass40254 ms—
2026-09-11 11:24 UTCGETpass40252 ms—
2026-09-07 11:24 UTCGETpass402124 ms—
2026-09-02 11:24 UTCGETpass402147 ms—
2026-08-14 08:53 UTCGETfail40240 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-10-07relisted{"status":"delisted"}{"status":"active"}
2026-10-02delisted{"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