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

defi.hugen.tokyo/defi/stablecoins

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://defi.hugen.tokyo/defi/stablecoins
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x29322ea7ecb34aa6164cb2ddeb9ce650902e4f60
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-11-18 18:06 UTC
Catalog-reported calls / payers (30d)6 / 1

2.Probe history

2026-09-252026-11-17
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-17 16:40 UTCGETpass402815 ms—
2026-11-15 04:40 UTCGETpass402713 ms—
2026-11-11 22:40 UTCGETpass402711 ms—
2026-11-09 16:40 UTCGETpass402662 ms—
2026-11-07 13:40 UTCGETpass402640 ms—
2026-11-05 04:40 UTCGETpass402768 ms—
2026-11-02 13:40 UTCGETpass402620 ms—
2026-10-15 21:40 UTCGETpass402604 ms—
2026-10-14 15:40 UTCGETpass402862 ms—
2026-10-13 03:40 UTCGETpass402537 ms—
2026-10-12 03:40 UTCGETpass402706 ms—
2026-10-11 03:40 UTCGETpass402910 ms—
2026-10-09 21:40 UTCGETpass402667 ms—
2026-10-08 16:40 UTCGETpass4021366 ms—
2026-10-07 16:40 UTCGETpass402740 ms—
2026-10-06 16:40 UTCGETpass402685 ms—
2026-10-05 22:40 UTCGETpass402584 ms—
2026-10-04 13:40 UTCGETpass402908 ms—
2026-10-03 16:40 UTCGETpass402679 ms—
2026-10-02 22:40 UTCGETpass402837 ms—
2026-10-01 22:40 UTCGETpass402597 ms—
2026-10-01 04:40 UTCGETpass402969 ms—
2026-09-30 13:40 UTCGETpass402728 ms—
2026-09-29 16:40 UTCGETpass402643 ms—
2026-09-28 22:40 UTCGETpass402599 ms—
2026-09-28 04:40 UTCGETpass402772 ms—
2026-09-27 13:40 UTCGETpass4022402 ms—
2026-09-26 16:40 UTCGETpass402669 ms—
2026-09-25 22:40 UTCGETpass4022635 ms—
2026-09-25 04:40 UTCGETpass402685 ms—

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 1 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 (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 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).
1/1
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
09-17 12:07settled (nonce-bound)2000x3d9cbd27…19bbBase2204 ms
10000 units (≈ $0.01 USDC) · L2 no_declaration (recorded mismatch)Whose 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 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.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 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. (defi.hugen.tokyo · measured 2026-09-17)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/a47d9520-3444-4f65-9307-8150005f905e.svg)](https://vet402.com/observatory/e/a47d9520-3444-4f65-9307-8150005f905e)

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

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

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