Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-11-16 · 1 day ago

eltociear-tokenguard.hf.space/stocks

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://eltociear-tokenguard.hf.space/stocks
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x5bcda55247b238a573a968b234f788a2d35664dd
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-11-17 10:05 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-032026-11-16
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-16 13:40 UTCPOSTpass402114 ms—
2026-11-12 22:40 UTCPOSTpass4022031 ms—
2026-11-10 16:40 UTCPOSTpass40259 ms—
2026-11-08 16:40 UTCPOSTpass402115 ms—
2026-11-06 13:40 UTCPOSTpass40230 ms—
2026-11-04 06:40 UTCPOSTpass40245 ms—
2026-11-01 04:40 UTCPOSTpass40237 ms—
2026-10-30 04:40 UTCPOSTpass4022034 ms—
2026-10-28 13:40 UTCPOSTpass40280 ms—
2026-10-26 15:40 UTCPOSTpass40246 ms—
2026-10-24 16:47 UTCPOSTpass40218 ms—
2026-10-22 22:40 UTCPOSTpass40282 ms—
2026-10-21 13:40 UTCPOSTpass40280 ms—
2026-10-13 10:30 UTCPOSTpass40226 ms—
2026-09-11 13:40 UTCPOSTpass40255 ms—
2026-09-10 23:40 UTCPOSTpass40294 ms—
2026-09-10 14:40 UTCPOSTpass402122 ms—
2026-09-09 17:40 UTCPOSTpass40236 ms—
2026-09-09 05:40 UTCPOSTpass402216 ms—
2026-09-08 17:40 UTCPOSTpass40220 ms—
2026-09-08 05:40 UTCPOSTpass4021877 ms—
2026-09-07 17:40 UTCPOSTpass402172 ms—
2026-09-07 05:40 UTCPOSTpass402174 ms—
2026-09-06 14:40 UTCPOSTpass402113 ms—
2026-09-05 23:40 UTCPOSTpass40223 ms—
2026-09-05 14:40 UTCPOSTpass402436 ms—
2026-09-04 23:40 UTCPOSTpass40274 ms—
2026-09-04 14:40 UTCPOSTpass40222 ms—
2026-09-03 23:40 UTCPOSTpass40227 ms—
2026-09-03 14:40 UTCPOSTpass402166 ms—

3.L1 — real purchases

3 of 3 paid attempts settled on-chain, and 3 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.

Terms in this table

settled (amount + payee)
vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
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 in the 402 (extensions.bazaar.info.output.example) counts as a declaration. When the catalog also declares an output, the example's top-level keys are required. When it does not, vet402 checks that the response is a JSON object or array, and the record page reads match (no required keys).
Stage delivered
vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side
the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
3/3
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txPayment chainLatency
08-28 12:20settled (amount + payee)2000x57fb56f9…4993Base1454 ms
5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
08-21 08:32settled (amount + payee)2000x7e87cfe6…122fBase1868 ms
5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
08-14 10:02settled (amount + payee)2000x18b54d6b…9059Base1347 ms
5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered

Add this badge to your docs

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.

vet402: 3 of 3 paid attempts settled with an on-chain receipt, and 3 of those also returned a deliverable HTTP 2xx response. settled is the confirmed transfer; delivered is a 2xx other than 202 with a non-empty body. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (eltociear-tokenguard.hf.space · measured 2026-08-28)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/25af249e-1943-4db5-b2d0-dadb3d793945.svg)](https://vet402.com/observatory/e/25af249e-1943-4db5-b2d0-dadb3d793945)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-06relisted{"status":"delisted"}{"status":"active"}
2026-09-12delisted{"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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far