api.messari.io/signal/v1/assets/mindshare-gainers-24h
1.Catalog declaration
| Resource URL | https://api.messari.io/signal/v1/assets/mindshare-gainers-24h |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x75ddd3c42eace13c59ea0cd1141b886a1c70d2a5 |
| Declared price (base units) | 350000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 268 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 389 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 1934 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 431 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 542 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 2234 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 280 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 202 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 248 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 523 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 232 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 301 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 213 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 231 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 1691 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 406 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 2107 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 221 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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-02 01:002026-09-02 01:00 UTC | settled (amount + payee)tx from our index | 200 | 0xf5e49791…e513 | 1966 ms |
| 350000 units (≈ $0.35 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/0b3dcd2d-07ca-4b86-9159-ef30a41ccdf8)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-28 | 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.