claude-p.tail7a0ba4.ts.net/funding-rates
1.Catalog declaration
| Resource URL | https://claude-p.tail7a0ba4.ts.net/funding-rates |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x810f6d61f7606deee2657d3083e150a222bc29c5 |
| Declared price (base units) | 3000 |
| Catalog status | delisted (since 2026-09-05 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-04 01:03 UTC |
| Catalog-reported calls / payers (30d) | 8 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-04 17:40 UTC | GET | pass | 402 | 735 ms | — |
| 2026-09-04 05:40 UTC | GET | unverified | — | 663 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 2573 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 2759 ms | — |
| 2026-09-02 23:40 UTC | GET | pass | 402 | 1098 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 1311 ms | — |
| 2026-08-19 10:56 UTC | GET | fail | 402 | 681 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 (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 mismatch- the response lacked fields the listing's output schema declares.
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-03 19:002026-09-03 19:00 UTC | settled (amount + payee) | 200 | 0x672b8b87…27cd | 7338 ms |
| 3000 units (≈ $0.003 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 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/90cac45d-6078-4de0-9cc5-75b7670b77d2)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-05 | 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.