Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-04 · 10 days ago

www.tereno.xyz/api/v1/capabilities/chain.snapshot/invoke

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://www.tereno.xyz/api/v1/capabilities/chain.snapshot/invoke
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xfbf218accbb0d57fc4e8fc3e2a885c910c4c9e94
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-14 13:03 UTC
Catalog-reported calls / payers (30d)3 / 3

2.Probe history

2026-09-142026-10-04
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-10-04 22:40 UTCGETfail402127 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-04 04:40 UTCGETfail402272 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-03 04:40 UTCGETfail402353 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-02 13:40 UTCGETfail4021344 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-01 16:40 UTCGETfail402328 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-09-30 22:40 UTCGETfail402380 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-09-29 22:40 UTCGETfail402160 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-09-29 10:30 UTCGETfail402233 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-09-29 07:38 UTCGETfail402730 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-09-28 16:40 UTCGETfail402596 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 22:40 UTCGETfail402422 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 04:40 UTCGETfail402264 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 13:40 UTCGETfail402175 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-25 16:40 UTCGETfail402173 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 22:40 UTCGETfail402250 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 04:40 UTCGETfail402211 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 13:40 UTCGETfail402140 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 16:40 UTCGETfail402227 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 22:40 UTCGETfail402163 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 04:40 UTCGETfail4022200 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-20 16:40 UTCGETfail402284 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 22:40 UTCGETfail402973 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 04:40 UTCGETfail402141 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-18 13:40 UTCGETfail402360 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 16:40 UTCGETfail402379 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 04:40 UTCGETfail402383 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-16 13:40 UTCGETfail402332 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-15 13:40 UTCGETfail402362 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-14 22:40 UTCGETfail402648 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-14 04:40 UTCGETfail402263 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were 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

No listing changes observed.

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