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

dartapi.ljaysk.com/v1/events

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://dartapi.ljaysk.com/v1/events
Sourcecdp_bazaar
Declared methodGET
Networkbase
Receiving address0x3b20d22540deb3cf1162b195cd15756adb5ceb5d
Declared price (base units)—
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)10 / 6

2.Probe history

2026-08-192026-09-04
Figure 1. Probe timeline, last 8 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-09-04 17:40 UTCGETpass402815 ms—
2026-09-04 05:40 UTCGETpass402669 ms—
2026-09-03 17:40 UTCGETpass4021335 ms—
2026-09-03 05:40 UTCGETpass402646 ms—
2026-09-02 17:40 UTCGETpass4021166 ms—
2026-09-02 05:40 UTCGETpass402797 ms—
2026-09-01 23:40 UTCGETpass402699 ms—
2026-08-19 10:56 UTCGETpass402650 ms—

3.L1 — real purchases

3 of 3 paid attempts settled with a receipt, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 4xx or 5xx counts as settled and not as delivered — definitions.

3/3
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
L1 purchase history, newest first
Attempted atResultHTTPReceipt (tx)Latency
09-01 12:07settled (amount + payee)2000xf32716c0…788e8558 ms
2000 units (≈ $0.002 USDC) · L2 mismatch
08-25 12:52settled (amount + payee)2000x81e04868…15582101 ms
2000 units (≈ $0.002 USDC) · L2 mismatch
08-19 12:12settled (amount + payee)2000x70e666e1…56068111 ms
2000 units (≈ $0.002 USDC) · L2 mismatch

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It states a measurement, not a rating.

vet402: 3 of 3 paid attempts settled, 3 delivered

[![vet402 receipt](https://vet402.com/api/badge/endpoint/d31099b0-a36a-4610-91e7-3112fe35f0f7.svg)](https://vet402.com/observatory/e/d31099b0-a36a-4610-91e7-3112fe35f0f7)

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

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.