starring-generated-forests-trader.trycloudflare.com/report
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://starring-generated-forests-trader.trycloudflare.com/report |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x479b69dfb8f7cce52da68f8276286840e8211ab9 |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-09-10 01:03 UTC) |
| First seen / last seen | 2026-09-05 01:03 UTC / 2026-09-09 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-09 17:40 UTC | GET | fail | — | 58 ms | dnsThe host name did not resolve. |
| 2026-09-08 23:40 UTC | GET | fail | — | 56 ms | dnsThe host name did not resolve. |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 441 ms | — |
| 2026-09-07 23:40 UTC | GET | pass | 402 | 639 ms | — |
| 2026-09-07 14:40 UTC | GET | pass | 402 | 610 ms | — |
| 2026-09-06 23:40 UTC | GET | pass | 402 | 627 ms | — |
| 2026-09-06 14:40 UTC | GET | pass | 402 | 594 ms | — |
| 2026-09-05 23:40 UTC | GET | pass | 402 | 993 ms | — |
| 2026-09-05 11:24 UTC | GET | pass | 402 | 555 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-06 12:082026-09-06 12:08 UTC | settle_failed (withdrawn from the catalog) | 402 | — | Base | 2716 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: vet402 unprovenLeft out of the public L0 fail count. | |||||
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.