money-reactor.makar52nn2016.workers.dev/api/verdict
1.Catalog declaration
| Resource URL | https://money-reactor.makar52nn2016.workers.dev/api/verdict |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0xf47b7e5912fd4218ac4c992cdc6fae04e1ff512e |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-10-20 13:01 UTC / 2026-11-12 16:05 UTC |
| Catalog-reported calls / payers (30d) | 13 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-11 04:40 UTC | GET | fail | 402 | 217 ms | price_mismatchDeclared 1000 of 0x8335…2913; the 402 offered 20000 of 0x8335…2913. |
| 2026-11-08 22:40 UTC | GET | fail | 402 | 387 ms | metadata_mismatchDeclared payTo 0xf47b…512e on eip155:8453; the 402 offered 0xC2B9…2130 on eip155:8453. |
| 2026-11-06 16:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-11-04 13:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-11-01 16:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-10-22 10:30 UTC | GET | fail | 402 | 102 ms | price_mismatchDeclared 1000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913. |
| 2026-10-21 10:30 UTC | GET | fail | 402 | 51 ms | price_mismatchDeclared 1000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913. |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 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
settle_claim_refuted- the transaction in the receipt did not show this payment on-chain, or was not found there within 7 days.
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). vet402 checks the current 402 from the seller before the catalog schema. An output example in the 402 (extensions.bazaar.info.output.example) is part of that check when the catalog also declares an output.
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).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 11-05 09:322026-11-05 09:32 UTC | settle_claim_refuted | 200 | 0x02e7c4bd…2f06 | Base | 1066 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: not sorted: one failure so far | |||||
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-11-01 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-26 | 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
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.
About the purchase at 2026-11-05T09:32:18Z (UTC). The form starts with that time; add what you saw instead.