eltociear-tokenguard.hf.space/stocks
1.Catalog declaration
| Resource URL | https://eltociear-tokenguard.hf.space/stocks |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x5bcda55247b238a573a968b234f788a2d35664dd |
| Declared price (base units) | 5000 |
| Catalog status | delisted (since 2026-09-12 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-11 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-11 13:40 UTC | POST | pass | 402 | 55 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 94 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 122 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 36 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 216 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 20 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 1877 ms | — |
| 2026-09-07 17:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 174 ms | — |
| 2026-09-06 14:40 UTC | POST | pass | 402 | 113 ms | — |
| 2026-09-05 23:40 UTC | POST | pass | 402 | 23 ms | — |
| 2026-09-05 14:40 UTC | POST | pass | 402 | 436 ms | — |
| 2026-09-04 23:40 UTC | POST | pass | 402 | 74 ms | — |
| 2026-09-04 14:40 UTC | POST | pass | 402 | 22 ms | — |
| 2026-09-03 23:40 UTC | POST | pass | 402 | 27 ms | — |
| 2026-09-03 14:40 UTC | POST | pass | 402 | 166 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 144 ms | — |
| 2026-09-02 17:40 UTC | POST | pass | 402 | 75 ms | — |
| 2026-09-02 05:40 UTC | POST | pass | 402 | 335 ms | — |
| 2026-09-01 23:40 UTC | POST | pass | 402 | 238 ms | — |
| 2026-08-14 08:53 UTC | POST | pass | 402 | 15 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 (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 |
|---|---|---|---|---|
| 08-28 12:202026-08-28 12:20 UTC | settled (amount + payee) | 200 | 0x57fb56f9…4993 | 1454 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-21 08:322026-08-21 08:32 UTC | settled (amount + payee) | 200 | 0x7e87cfe6…122f | 1868 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-14 10:022026-08-14 10:02 UTC | settled (amount + payee) | 200 | 0x18b54d6b…9059 | 1347 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 3/3 settled · 3 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/25af249e-1943-4db5-b2d0-dadb3d793945)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-12 | 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.