api.hyperextend.xyz/v1/liquidations/BTC
1.Catalog declaration
| Resource URL | https://api.hyperextend.xyz/v1/liquidations/BTC |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x548fc289526ab2f0391d562a723cda64bbf1abc4 |
| Declared price (base units) | 111000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-09 01:03 UTC |
| Catalog-reported calls / payers (30d) | 22 / 15 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-09 05:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-08 17:40 UTC | GET | fail | 402 | 460 ms | price_mismatch |
| 2026-09-08 05:40 UTC | GET | fail | 402 | 404 ms | price_mismatch |
| 2026-09-07 17:40 UTC | GET | fail | 402 | 401 ms | price_mismatch |
| 2026-09-07 05:40 UTC | GET | fail | 402 | 433 ms | price_mismatch |
| 2026-09-06 17:40 UTC | GET | fail | 402 | 335 ms | price_mismatch |
| 2026-09-06 05:40 UTC | GET | fail | 402 | 311 ms | price_mismatch |
| 2026-09-05 14:40 UTC | GET | fail | 402 | 495 ms | price_mismatch |
| 2026-09-04 23:40 UTC | GET | fail | 402 | 2309 ms | price_mismatch |
| 2026-09-04 14:40 UTC | GET | fail | 402 | 522 ms | price_mismatch |
| 2026-09-04 05:40 UTC | GET | fail | 402 | 425 ms | price_mismatch |
| 2026-09-03 17:40 UTC | GET | fail | 402 | 407 ms | price_mismatch |
| 2026-09-03 05:40 UTC | GET | fail | 402 | 451 ms | price_mismatch |
| 2026-09-02 17:40 UTC | GET | fail | 402 | 333 ms | price_mismatch |
| 2026-09-02 05:40 UTC | GET | fail | 402 | 679 ms | price_mismatch |
| 2026-09-01 23:40 UTC | GET | fail | 402 | 210 ms | price_mismatch |
| 2026-08-14 08:53 UTC | GET | pass | 402 | 81 ms | — |
3.L1 — real purchases
1 of 2 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-09 07:012026-09-09 07:01 UTC | settle_claimed | 200 | 0x15191d3c…e078 | 18292 ms |
| 111000 units (≈ $0.11 USDC) · L2 mismatch | ||||
| 08-14 10:102026-08-14 10:10 UTC | settled (amount + payee) | 200 | 0xdaf067d5…6f86 | 13153 ms |
| 111000 units (≈ $0.11 USDC) · L2 no_declaration | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/2 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/11e53fea-e122-4363-97d5-74d357c51b4b)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.