wailand.tailf99551.ts.net/v1/opportunities
1.Catalog declaration
| Resource URL | https://wailand.tailf99551.ts.net/v1/opportunities |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x32e293a7fa946331b3ecd013cf0461bf32c99a9d |
| Declared price (base units) | 15000 |
| Catalog status | active |
| First seen / last seen | 2026-09-02 01:03 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 734 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 4314 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 4267 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 636 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 1017 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 818 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 4658 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 867 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 584 ms | — |
| 2026-10-08 04:40 UTC | GET | unverified | — | 436 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 672 ms | — |
| 2026-10-06 04:41 UTC | GET | unverified | — | 418 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 829 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 544 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 1339 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 531 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 594 ms | — |
| 2026-09-30 16:40 UTC | GET | fail | — | 169 ms | dnsThe host name did not resolve. |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 442 ms | — |
| 2026-09-29 07:38 UTC | GET | pass | 402 | 1206 ms | — |
| 2026-09-28 22:40 UTC | GET | fail | 402 | 470 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-28 04:40 UTC | GET | fail | 402 | 634 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-27 13:40 UTC | GET | fail | 402 | 2442 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-26 16:40 UTC | GET | fail | 402 | 821 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-25 22:40 UTC | GET | fail | 402 | 513 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 881 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 1738 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 462 ms | — |
| 2026-09-22 22:40 UTC | GET | fail | — | 89 ms | networkThe connection failed (refused or reset) before a response. |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 495 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 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-07 01:002026-09-07 01:00 UTC | settled (nonce-bound) | 200 | 0x37d1f568…9b0c | 1345 ms |
| 100000 units (≈ $0.10 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/68330232-fda8-47ae-a2c4-2b92b2396b12)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.