Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-29 · 6 days ago
vet402Back to the registerMethodology

poolproof.ru/v1/launch

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://poolproof.ru/v1/launch
Sourcecdp_bazaar
Declared methodGET
Networkbase
Receiving address0x11efa031d56316bd63720d172f9d5c1448e9a21f
Declared price (base units)—
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)11 / 2

2.Probe history

2026-08-242026-09-29
Figure 1. Probe timeline, last 9 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-29 07:38 UTCGETpass402277 ms—
2026-09-26 10:30 UTCGETfail402447 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.
2026-09-22 11:24 UTCGETfail402669 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.
2026-09-18 11:24 UTCGETfail402870 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.
2026-09-15 11:24 UTCGETfail402607 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.
2026-09-11 11:24 UTCGETfail402130 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.
2026-09-08 11:24 UTCGETfail402153 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.
2026-09-03 11:24 UTCGETfail402553 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.
2026-08-24 11:11 UTCGETfail402378 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

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.

20–2,000 characters · 0 so far