goflightlabs.mpp.tempo.xyz

Solana, Tempo and Base

Graded from Solana, Tempo and Base purchases only. Listed on the Sellers page.

vet402 paid this seller 1 time with its own money (Tempo 1), most recently on 2026-09-28 (UTC). 1 settled on chain; 0 came back with an answer; 1 settled on chain, and nothing usable came back.

It costs the seller nothing, and there is nothing to sign up for.

… measuring · Measuring: a rank number needs 10 counted purchases on 2 different days; this seller has 1 on 1.

0 / 1
came back, of counted (0%)
0.00 to 0.79
95% interval
2026-09-28
last bought · 1 day counted
00.51

Came back, of counted, per chain: Tempo 0/1. Came back with an answer = vet402's payment settled, then the seller answered 2xx with a non-empty body. vet402 did not check that the answer is what the listing promised; whether its keys matched what the seller declared is a separate column.

Separate column, not in the grade. Answer matched what the seller declared: not checked.

Not counted

0vet402 or facilitator side not counted
0can't tell not counted

Counted against this seller

1seller side counted in the grade
paid not delivered 1
  1. 2026-09-28 08:04 UTC · Tempo · paid not delivered · HTTP 502 0x34fbc6…f965ec
    https://goflightlabs.mpp.tempo.xyz/airports-by-filters
    runner said: http 502 · settled on chain (found by the post-run chain check)

How each failure is assigned

Recent purchases

Each tx links to a public explorer.

  1. 2026-09-28 08:04 UTC · Tempo · seller side: paid not delivered 0x34fbc6…f965ec
    https://goflightlabs.mpp.tempo.xyz/airports-by-filters

Are you the seller?

Is a row wrong? A seller who thinks a row is wrong opens a GitHub issue with the URL or tx. vet402 checks it against the chain and the raw result; a wrong row is fixed and the fix is noted in the change log.

Tell vet402 a row is wrong (GitHub issue, prefilled)

Signed records of failed purchases are published only after the seller is told. More for sellers