twitter.surf.cascade.fyi/api/v1/twitter/users/search
1.Catalog declaration
| Resource URL | https://twitter.surf.cascade.fyi/api/v1/twitter/users/search |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | 9MkM5Ra48KFcSv9HDQ8sb3C3r5HjouEwGQ6sp1cx1vde |
| Declared price (base units) | 4000 |
| Catalog status | active |
| First seen / last seen | 2026-08-15 01:36 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 107 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 10:30 UTC | POST | pass | 402 | 616 ms | — |
| 2026-09-25 10:30 UTC | POST | pass | 402 | 476 ms | — |
| 2026-09-20 11:24 UTC | POST | pass | 402 | 537 ms | — |
| 2026-09-17 12:35 UTC | POST | pass | 402 | 520 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 516 ms | — |
| 2026-09-10 11:24 UTC | POST | pass | 402 | 482 ms | — |
| 2026-09-06 11:24 UTC | POST | pass | 402 | 528 ms | — |
| 2026-09-01 23:14 UTC | POST | pass | 402 | 516 ms | — |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 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
delivered_no_receipt- the paid request answered 2xx without a settlement receipt.
L2 match- the response had the 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-18 00:002026-09-18 00:00 UTC | delivered_no_receipt | 200 | — | 20113 ms |
| 4000 units (≈ $0.004 USDC) · L2 matchWhose side: not sorted: no charge | ||||
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.