Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago

x402.freeq.one/tools/wallet_verify_nostr

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.freeq.one/tools/wallet_verify_nostr
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x90b0dc893406d6ea63bb077ed59f5e8340f98d84
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-08-27 01:15 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)11 / 1

2.Probe history

2026-09-042026-10-19
Figure 1. Probe timeline, last 29 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-19 13:40 UTCPOSTpass402724 ms—
2026-10-17 22:40 UTCPOSTpass402565 ms—
2026-10-16 15:40 UTCPOSTpass402209 ms—
2026-10-15 03:40 UTCPOSTpass402287 ms—
2026-10-13 21:40 UTCPOSTpass402224 ms—
2026-10-12 15:40 UTCPOSTpass402243 ms—
2026-10-11 12:40 UTCPOSTpass402104 ms—
2026-10-10 12:40 UTCPOSTpass402114 ms—
2026-10-09 12:40 UTCPOSTpass4022143 ms—
2026-10-08 04:40 UTCPOSTpass402138 ms—
2026-10-07 04:40 UTCPOSTpass4022060 ms—
2026-10-06 04:41 UTCPOSTpass40284 ms—
2026-10-04 22:40 UTCPOSTpass402102 ms—
2026-10-04 04:40 UTCPOSTpass402193 ms—
2026-10-03 04:40 UTCPOSTpass402931 ms—
2026-10-02 13:40 UTCPOSTpass402225 ms—
2026-10-01 16:40 UTCPOSTpass402145 ms—
2026-09-30 22:40 UTCPOSTpass40288 ms—
2026-09-30 04:40 UTCPOSTpass402263 ms—
2026-09-25 13:40 UTCPOSTfail402138 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 16:40 UTCPOSTfail402194 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 22:40 UTCPOSTfail40280 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 13:40 UTCPOSTfail402441 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 11:25 UTCPOSTfail40287 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 11:24 UTCPOSTfail40282 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-16 11:24 UTCPOSTfail40283 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-12 11:24 UTCPOSTfail40282 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-09 11:24 UTCPOSTfail402100 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-04 11:24 UTCPOSTpass40296 ms—

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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-30relisted{"status":"delisted"}{"status":"active"}
2026-09-26delisted{"status":"active"}{"status":"delisted"}
2026-09-09relisted{"status":"delisted"}{"status":"active"}
2026-09-08delisted{"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.

20–2,000 characters · 0 so far