trading-perps.vercel.app/api/enso/indices
1.Catalog declaration
| Resource URL | https://trading-perps.vercel.app/api/enso/indices |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0xbd356968846829e32983bb4abe2d0dd29f2c2f7b |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-16 01:07 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-21 04:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-10-19 22:40 UTC | GET | pass | 402 | 112 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 478 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 499 ms | — |
| 2026-10-12 21:40 UTC | GET | fail | 502 | 582 ms | no_402HTTP 502 instead of 402 to an unpaid GET. |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 149 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 2059 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 175 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 130 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 248 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 108 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 265 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 202 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 421 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 627 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 236 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
settled (amount + payee)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
L2 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
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 | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-18 18:022026-09-18 18:02 UTC | settled (nonce-bound) | 200 | 0x0ee37169…8031 | Base | 918 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | |||||
| 09-12 00:002026-09-12 00:00 UTC | settled (nonce-bound) | 200 | 0x7b74b8a9…ff62 | Base | 1394 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | |||||
| 09-03 01:002026-09-03 01:00 UTC | settled (amount + payee) | 200 | 0xbac02f16…bcfb | Base | 1321 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose 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.
[](https://vet402.com/observatory/e/7c3388fc-91a4-4302-b913-6b730d6c99e3)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.