tick.hugen.tokyo/tick/latest
1.Catalog declaration
| Resource URL | https://tick.hugen.tokyo/tick/latest |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x29322ea7ecb34aa6164cb2ddeb9ce650902e4f60 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 327 / 171 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 487 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 601 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 284 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 2112 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 281 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 398 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 3321 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 311 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 887 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 453 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 279 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 294 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 494 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 303 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 259 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 281 ms | — |
| 2026-08-14 08:52 UTC | GET | fail | 402 | 97 ms | accepts_invalid |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 2 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 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.
L2 no_declaration- the listing declares no output schema to check the response against.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-24 06:012026-09-24 06:01 UTC | settled (nonce-bound) | 200 | 0xa53578cc…5065 | 1444 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-18 00:012026-09-18 00:01 UTC | settled (nonce-bound) | 200 | 0xb8fc819a…31b5 | 1748 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/c141815c-51d6-4bfd-ba5c-ccaf0fef863f)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.