api.hyperextend.xyz/v1/candles/BTC/1m
1.Catalog declaration
| Resource URL | https://api.hyperextend.xyz/v1/candles/BTC/1m |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x548fc289526ab2f0391d562a723cda64bbf1abc4 |
| Declared price (base units) | 50960 |
| Catalog status | active |
| First seen / last seen | 2026-09-09 01:03 UTC / 2026-10-24 13:02 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-22 16:40 UTC | GET | pass | 402 | 2207 ms | — |
| 2026-10-21 04:40 UTC | GET | pass | 402 | 998 ms | — |
| 2026-10-19 16:40 UTC | GET | fail | 402 | 546 ms | price_mismatchDeclared 50930 of 0x8335…2913; the 402 offered 51000 of 0x8335…2913, 0.051 of USDC:0…e054, 51000 of 0x8335…2913. |
| 2026-10-18 04:40 UTC | GET | fail | 402 | 614 ms | price_mismatchDeclared 50930 of 0x8335…2913; the 402 offered 51000 of 0x8335…2913, 0.051 of USDC:0…e054, 51000 of 0x8335…2913. |
| 2026-10-16 21:40 UTC | GET | fail | 402 | 446 ms | price_mismatchDeclared 50930 of 0x8335…2913; the 402 offered 51000 of 0x8335…2913, 0.051 of USDC:0…e054, 51000 of 0x8335…2913. |
| 2026-10-15 12:40 UTC | GET | fail | 402 | 470 ms | price_mismatchDeclared 50930 of 0x8335…2913; the 402 offered 51000 of 0x8335…2913, 0.051 of USDC:0…e054, 51000 of 0x8335…2913. |
| 2026-10-14 03:40 UTC | GET | fail | 402 | 663 ms | price_mismatchDeclared 50930 of 0x8335…2913; the 402 offered 51000 of 0x8335…2913, 0.051 of USDC:0…e054, 51000 of 0x8335…2913. |
| 2026-10-04 10:30 UTC | GET | pass | 402 | 408 ms | — |
| 2026-09-27 10:30 UTC | GET | pass | 402 | 432 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-19 11:24 UTC | GET | fail | 402 | 384 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 333 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 357 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 363 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.