fiatdock.com/v1/stablecoin/intel
1.Catalog declaration
| Resource URL | https://fiatdock.com/v1/stablecoin/intel |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xeb12bb2f52eed33dba6a00774e48324032fd87c6 |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 12 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | POST | pass | 402 | 462 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 440 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 359 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 262 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 377 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 426 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 318 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 338 ms | — |
| 2026-10-08 22:40 UTC | POST | pass | 402 | 193 ms | — |
| 2026-10-07 22:40 UTC | POST | pass | 402 | 251 ms | — |
| 2026-10-06 22:40 UTC | POST | pass | 402 | 260 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 190 ms | — |
| 2026-10-04 16:40 UTC | POST | pass | 402 | 2097 ms | — |
| 2026-10-03 22:40 UTC | POST | pass | 402 | 173 ms | — |
| 2026-10-03 04:40 UTC | POST | pass | 402 | 225 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 188 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 269 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 364 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 508 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 482 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 408 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 368 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 489 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 774 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 760 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 896 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 512 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 400 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 270 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 316 ms | — |
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 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 |
|---|---|---|---|---|
| 08-16 12:502026-08-16 12:50 UTC | settled (amount + payee) | 200 | 0xf975c249…9489 | 1491 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose 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/39895cdb-39c8-46c4-8641-6665937c3c22)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.