dartapi.ljaysk.com/v1/events
1.Catalog declaration
| Resource URL | https://dartapi.ljaysk.com/v1/events |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | base |
| Receiving address | 0x3b20d22540deb3cf1162b195cd15756adb5ceb5d |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-15 12:40 UTC | GET | pass | 402 | 814 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 782 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 961 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 864 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 852 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 2123 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 929 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 957 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 769 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 885 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 901 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 795 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 942 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 726 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 872 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 2150 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 949 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 734 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 806 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 694 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 806 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 708 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 1166 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 1031 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 693 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 696 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 2678 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 693 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 776 ms | — |
3.L1 — real purchases
5 of 5 paid attempts settled on-chain, and 5 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 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 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 mismatch- the response lacked fields the listing's output schema declares.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-16 18:012026-09-16 18:01 UTC | settled (nonce-bound) | 200 | 0x7c643e43…1421 | 8882 ms |
| 2000 units (≈ $0.002 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-10 01:002026-09-10 01:00 UTC | settled (nonce-bound) | 200 | 0xa8e45005…7e8e | 2060 ms |
| 2000 units (≈ $0.002 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-01 12:072026-09-01 12:07 UTC | settled (amount + payee) | 200 | 0xf32716c0…788e | 8558 ms |
| 2000 units (≈ $0.002 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-25 12:522026-08-25 12:52 UTC | settled (amount + payee) | 200 | 0x81e04868…1558 | 2101 ms |
| 2000 units (≈ $0.002 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-19 12:122026-08-19 12:12 UTC | settled (amount + payee) | 200 | 0x70e666e1…5606 | 8111 ms |
| 2000 units (≈ $0.002 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 5/5 settled · 5 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/d31099b0-a36a-4610-91e7-3112fe35f0f7)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.