sign.cyberwarex.com
1 Base listing. By the latest purchase of each: 0 delivered · 1 failed on the seller's side · 0 on vet402's side · 0 not yet bought. Latest purchase: 2026-09-10 12:07 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| sign.cyberwarex.com/decodeGET | 2026-09-10 12:07 UTC | Server error on the paid request | seller's side |
What we saw: vet402 signed the payment and the paid request got a 5xx.What to fix: Check the route's logs: the handler or its upstream failed on the paid request. (a server change)Recorded: settle_failed · HTTP 500 · no txIn export.csv?days=19: the row with attempted_at 2026-09-10T12:07:40Z and resource_key sign.cyberwarex.com/decode. | |||
2.How to read this
Each listing shows its latest purchase on Base and up to four earlier ones. Whose side says where the failure came from: the seller's answer or listing, or vet402 itself. A row held (held_reason in the export) is not counted against the seller in the delivered numbers, because vet402 cannot rule out that its request was the problem. 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?
Open the listing's record (the link in the first column) and use “Dispute this record” there. Say which purchase and what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.