shield.vainplex.dev: x402 purchase results on Base, as of 2026-09-28

2 Base listings. By the latest attempt at each: 1 delivered · 0 failed on the seller's side · 1 on vet402's side · 0 not tried yet. Latest attempt: 2026-09-28 06:01 UTC.

Rows marked census or retest were bought to give this seller a row of its own, or to buy again after a failure on vet402's side.

1.Your listings

1. shield.vainplex.dev/api/cdp/check-password-rangeGET

   Latest attempt

   2026-09-28 06:01 UTC

   Result

   delivered

   Whose side

   no failure (delivered)

   What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0xfcaf…02a6. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0xfcaf…02a6 · nonce 0x3b55…80b3 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x8c0a68b7…631e · bought by the retestIn export.csv?days=2: the row with attempted_at 2026-09-28T06:01:26Z and resource_key shield.vainplex.dev/api/cdp/check-password-range.Dispute this purchaseEmail me when this result changes
2. shield.vainplex.dev/api/cdp/check/ipGET

   Latest attempt

   2026-09-15 00:01 UTC

   Result

   vet402's wallet was out of USDC

   Whose side

   vet402's side

   What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0xfcaf…02a6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0xfcaf…02a6 · nonce 0xf5be…7450 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=16: the row with attempted_at 2026-09-15T00:01:03Z and resource_key shield.vainplex.dev/api/cdp/check/ip.Dispute this purchaseEmail me when this result changes

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result (“Recorded (L1 paid purchase)”); a row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. Even then, one such failure is “not sorted: one failure so far”: a failure goes on the seller's side only when the same listing has one on two different days (UTC), and those rows are marked “under re-check” while we re-check them. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export), a failure where no payment was taken (“no charge”), and a payment that settled before the seller refused an input vet402 had not sent. “Signed payment” and “Answer to the paid request” show what the row recorded, and nothing else: the answer's body and header values are not published. The maxTimeoutSeconds on a row is the listing's value today; a declared price or address on a not-bought row is the value recorded at the time of the attempt. The transaction link opens the settlement on Basescan. Listings removed from the Bazaar, and listings whose catalog network is not Base, are not on this page. The fix-first page groups the same results across sellers (methodology).

3.Think a row is wrong?

Use “Dispute this purchase” on the row: it opens Dispute this record on the listing's record page with the purchase time filled in. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.