liquidation-oracle.api.klymax402.com/api/levels
1.Catalog declaration
| Resource URL | https://liquidation-oracle.api.klymax402.com/api/levels |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6e8b64638b24c6d625b045dd353120d850064e2e |
| Declared price (base units) | 3000 |
| Catalog status | delisted (since 2026-09-19 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-18 01:03 UTC |
| Catalog-reported calls / payers (30d) | 6 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-18 22:40 UTC | GET | unverified | — | 228 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-09-18 04:40 UTC | GET | unverified | — | 255 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 580 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 436 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 550 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 395 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 531 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 714 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 567 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 593 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 893 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 548 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 394 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 519 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 556 ms | — |
| 2026-09-06 17:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-09-06 05:40 UTC | GET | pass | 402 | 467 ms | — |
| 2026-09-05 17:40 UTC | GET | pass | 402 | 591 ms | — |
| 2026-09-05 05:40 UTC | GET | pass | 402 | 521 ms | — |
| 2026-09-04 17:40 UTC | GET | pass | 402 | 410 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 368 ms | — |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 508 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 404 ms | — |
| 2026-09-02 17:40 UTC | GET | pass | 402 | 442 ms | — |
| 2026-09-02 05:40 UTC | GET | pass | 402 | 422 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
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).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-11 06:022026-09-11 06:02 UTC | settled (nonce-bound) | 200 | 0x4f129c3a…7557 | 2625 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-01 12:082026-09-01 12:08 UTC | settled (amount + payee) | 200 | 0xe275ce2d…3fd2 | 2350 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-25 12:532026-08-25 12:53 UTC | settled (amount + payee) | 200 | 0xc7971afb…6fc1 | 2254 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-19 12:122026-08-19 12:12 UTC | settled (amount + payee) | 200 | 0x54484f0c…d09f | 2213 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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/6e03d752-722f-41e1-bfce-d00e75ff8608)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-19 | delisted | {"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.