escrowpulse.waltsoft.net/v1/escrow
1.Catalog declaration
| Resource URL | https://escrowpulse.waltsoft.net/v1/escrow |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | base |
| Receiving address | 0x318a4b4764eb37c3fcbce434713128143815fd57 |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-10-01 01:03 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 8 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 10:30 UTC | POST | pass | 402 | 182 ms | — |
| 2026-10-01 10:30 UTC | POST | fail | 502 | 118 ms | no_402HTTP 502 instead of 402 to an unpaid POST. |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 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.
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
settle_claimed- the seller returned a receipt that vet402 has not re-read on-chain yet.
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 |
|---|---|---|---|---|
| 10-02 12:012026-10-02 12:01 UTC | settle_claimedtx from our index | 200 | 0xb4192169…bedc | 2354 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: not sorted: awaiting on-chain verification | ||||
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
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.