penny402.fun/horoscope
1.Catalog declaration
| Resource URL | https://penny402.fun/horoscope |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x9d0bb5da24cade855dee8d1231a1c416e0bb2ffe |
| Declared price (base units) | 2500 |
| Catalog status | active |
| First seen / last seen | 2026-09-03 01:03 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 110 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 97 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 83 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 50 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 622 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 1583 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 547 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 252 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 187 ms | — |
| 2026-10-02 13:40 UTC | POST | pass | 402 | 374 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 237 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 191 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 347 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 202 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 253 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 938 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 578 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 59 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 244 ms | — |
| 2026-09-23 10:31 UTC | POST | pass | 402 | 106 ms | — |
| 2026-09-19 11:24 UTC | POST | pass | 402 | 240 ms | — |
| 2026-09-17 11:24 UTC | POST | pass | 402 | 93 ms | — |
| 2026-09-13 11:24 UTC | POST | pass | 402 | 141 ms | — |
| 2026-09-09 11:24 UTC | POST | pass | 402 | 121 ms | — |
| 2026-09-05 11:24 UTC | POST | pass | 402 | 11 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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 | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-25 00:022026-09-25 00:02 UTC | settled (nonce-bound)tx from our index | 200 | 0x94f555f7…543e | Base | 580 ms |
| 2500 units (≈ $0.0025 USDC) · L2 no_declarationWhose side: no failure (delivered) | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/42199682-6b02-418a-88a0-da00d7caae14)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-10 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-03 | delisted | {"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.