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

whaletape.xyz/liquidations/BTC

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://whaletape.xyz/liquidations/BTC
Sourcecdp_bazaar
Declared methodGET
Networksolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
Receiving address226DYoWb2e6uYxDkFp7vK8jZhzzh2VNvHH6DgbDsNueC
Declared price (base units)50000
Catalog statusactive
First seen / last seen2026-08-30 01:02 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)3 / 1

2.Probe history

2026-09-222026-10-19
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-19 13:40 UTCGETpass402650 ms—
2026-10-17 22:40 UTCGETpass402554 ms—
2026-10-16 15:40 UTCGETpass402496 ms—
2026-10-15 03:40 UTCGETpass402674 ms—
2026-10-13 21:40 UTCGETpass402518 ms—
2026-10-12 15:40 UTCGETpass402445 ms—
2026-10-11 15:40 UTCGETpass402516 ms—
2026-10-10 12:40 UTCGETpass402755 ms—
2026-10-09 12:40 UTCGETpass402622 ms—
2026-10-08 04:40 UTCGETpass402425 ms—
2026-10-07 04:40 UTCGETfail402578 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-10-06 04:41 UTCGETfail402822 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-10-04 22:40 UTCGETfail402332 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-10-04 04:40 UTCGETfail4022449 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-10-03 04:40 UTCGETfail402390 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-10-02 13:40 UTCGETfail402364 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-10-01 16:40 UTCGETfail402340 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-09-30 22:40 UTCGETfail402129 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-09-30 04:40 UTCGETfail402321 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-09-29 10:30 UTCGETfail402121 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-09-29 07:38 UTCGETfail402291 msprice_mismatchDeclared 10000 of EPjFWd…Dt1v; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-09-28 16:40 UTCGETfail402421 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-28 04:40 UTCGETfail402840 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 13:40 UTCGETpass402519 ms—
2026-09-26 16:40 UTCGETpass402398 ms—
2026-09-25 22:40 UTCGETpass402467 ms—
2026-09-25 04:40 UTCGETpass402779 ms—
2026-09-24 13:40 UTCGETpass402408 ms—
2026-09-23 16:40 UTCGETpass4021001 ms—
2026-09-22 22:40 UTCGETpass402139 ms—

3.L1 — real purchases

3 of 3 paid attempts settled on-chain, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). 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.

Terms in this table

settled (nonce-bound)
vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 no_declaration
the listing declares no output schema to check the response against.
Whose side
the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
3/3
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txLatency
10-08 06:00settled (nonce-bound)2005EhuZYGmdz…XCgu2803 ms
50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered)
09-25 18:00settled (nonce-bound)2003E61CdAaMW…6g1q2202 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)
09-19 12:07settled (nonce-bound)200cpDTtXYGeU…cZdp2062 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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.

vet402: 3 of 3 paid attempts settled with an on-chain receipt, and 3 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (whaletape.xyz · measured 2026-10-08)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/ec74a047-187b-4d10-abaa-66d3caf356b2.svg)](https://vet402.com/observatory/e/ec74a047-187b-4d10-abaa-66d3caf356b2)

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