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

forgesignals.org/attest

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://forgesignals.org/attest
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x403570a1f21fe14a3a80cae4779de92eddba6e2a
Declared price (base units)20000
Catalog statusdelisted (since 2026-09-02 01:03 UTC)
First seen / last seen2026-08-18 01:06 UTC / 2026-09-01 01:03 UTC
Catalog-reported calls / payers (30d)4 / 1

2.Probe history

2026-09-01
Figure 1. Probe timeline, last 1 probe for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-01 23:14 UTCPOSTfail503310 msno_402

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.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-02delisted{"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.