proxy.suverse.io/v1/data/fiat-exchange-rates
1.Catalog declaration
| Resource URL | https://proxy.suverse.io/v1/data/fiat-exchange-rates |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x260fbe1ec46968ee02e5b972507d7bb7f09f82b0 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 7 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 262 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 353 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 277 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 306 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 469 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 2233 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 613 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 387 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 738 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 2757 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 192 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 1183 ms | — |
| 2026-09-13 11:24 UTC | GET | pass | 402 | 429 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 465 ms | — |
| 2026-08-25 10:47 UTC | GET | pass | 402 | 427 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 2 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.
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).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-27 00:022026-09-27 00:02 UTC | settled (nonce-bound) | 200 | 0x90d4ae15…f65c | 1716 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-17 00:002026-09-17 00:00 UTC | settled (nonce-bound) | 200 | 0xb4bc2cb0…4bc9 | 2010 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/f9355deb-476d-4ab4-b90a-ae68a2fffbc6)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-10 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-31 | 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.
About the purchase at 2026-09-27T00:02:19Z (UTC). The form starts with that time; add what you saw instead.