kronossignals.com/api/v1/forecast/doge
1.Catalog declaration
| Resource URL | https://kronossignals.com/api/v1/forecast/doge |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x36038e1d712c5e39f35952164ec58ec2b96caee7 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 408 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 121 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 274 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 1877 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 694 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 127 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 111 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 403 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 81 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 81 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 169 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 36 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 183 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 169 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 2342 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 263 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 244 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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 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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-10 19:012026-09-10 19:01 UTC | settled (nonce-bound) | 200 | 0xd7750f0f…8e68 | 3291 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-28 12:192026-08-28 12:19 UTC | settled (amount + payee) | 200 | 0x75b03f87…d2d1 | 2330 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-21 08:312026-08-21 08:31 UTC | settled (amount + payee) | 200 | 0x29d80d18…2aed | 2563 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-14 09:572026-08-14 09:57 UTC | settled (amount + payee) | 200 | 0x4b04febe…9b00 | 1869 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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/60ab5653-cd90-48a7-bfce-98b1f10109c7)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.