safe.cyberwarex.com: x402 purchase results on Base, as of 2026-09-28

1 Base listing. By the latest attempt at each: 1 delivered · 0 failed on the seller's side · 0 on vet402's side · 0 not tried yet. Latest attempt: 2026-09-28 12:02 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. safe.cyberwarex.com/checkGET

   Latest attempt

   2026-09-28 12:02 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.003 USDC · payTo 0x058d…21b2. 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.003 USDC · payTo 0x058d…21b2 · nonce 0xa98d…05da · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.The latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xe0064042…6843 · bought by the retestIn export.csv?days=2: the row with attempted_at 2026-09-28T12:02:43Z and resource_key safe.cyberwarex.com/check.Dispute this purchaseEmail me when this result changes

   Earlier attempts

   1. 2026-09-10 07:00 UTC · vet402 did not send the declared query · vet402's sidesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)
      What vet402 recorded

      Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing declares them (example values, or required names). The seller refused the request with 400 or 422.The 402 terms vet402 paid: vet402 signed: exact · 0.003 USDC · payTo 0x058d…21b2. 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.003 USDC · payTo 0x058d…21b2 · nonce 0x2cd9…e076 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.
      Dispute this purchase

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.