yieldsignal.vercel.app/signal/usdc-base-yield
1.Catalog declaration
| Resource URL | https://yieldsignal.vercel.app/signal/usdc-base-yield |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x561143bfe9e2d975d92e915b8effeaa54119472a |
| Declared price (base units) | 100000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 16:40 UTC | GET | pass | 402 | 487 ms | — |
| 2026-10-18 22:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 279 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 323 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 95 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 186 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 327 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 145 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 58 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 1869 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 50 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 240 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 2275 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 245 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 97 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 (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's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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-06 19:002026-09-06 19:00 UTC | settled (nonce-bound) | 200 | 0xf068541a…e7af | 2261 ms |
| 100000 units (≈ $0.10 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/ae804ba9-4071-4113-865e-8f21591ffa80)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-03 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-22 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-10 | 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.