gateway.grapevine.fyi
2 Base listings. By the latest purchase of each: 0 delivered · 0 failed on the seller's side · 1 on vet402's side · 1 not yet bought. Latest purchase: 2026-09-06 07:01 UTC.
Your most recent purchase failed on vet402's side. Nothing for you to fix there.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| gateway.grapevine.fyi/x402/cid/bafybeidw3gs4ff5gthqt4kovvtcanae4gqbzmuhrxe6c5jaayoanhdwp6iGET | 2026-09-06 07:01 UTC | vet402's own run did not finish | vet402's side |
What we saw: vet402's request did not complete on its side (its run was cut off, or a step failed inside vet402).What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: request_error · HTTP — · no txNot in the public export: a vet402-side state it leaves out. | |||
| gateway.grapevine.fyi/x402/cid/bafkreib7s7xuwc57wri43lyauwjeyfx3zqyc4ue34td5o7ab6wxp7sbqhmGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
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.