insider.lonestaroracle.xyz
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-22 00:01 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| insider.lonestaroracle.xyz/tradesGET | 2026-09-22 00:01 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=8: the row with attempted_at 2026-09-22T00:01:02Z and resource_key insider.lonestaroracle.xyz/trades. | |||
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.