Receipts
Each receipt is re-verified against the published signing key on this request, not read from a stored flag. Download the JSON and you can check the same chain yourself, offline, with no access to MergeGate.
6/6
verified just now
105
checks re-run on this request
2
chains
Recomputed per request from the receipts themselves. Never a stored flag.
FAIL
4KInc/mergegate-demo-task
0.25
USDC refunded to buyer
Submission
1758ca30…bcfe0e
Settlement
0x8362ac…245354
Verifier fee
0.05
✓ 17 checks passed, re-run now
Open →
PASS
4KInc/mergegate-demo-task
0.25
USDC released to provider
Submission
97e4bd61…799373
Settlement
0xf8cb4b…cfe9b6
Verifier fee
0.05
✓ 18 checks passed, re-run now
Open →
FAIL
4KInc/mergegate-demo-task
0.25
USDC refunded to buyer
Submission
272356db…a730aa
Settlement
0x4581ed…895b1e
Verifier fee
0.05
✓ 17 checks passed, re-run now
Open →
PASS
4KInc/mergegate-demo-task
0.25
USDC released to provider
Submission
e83964b7…d210ff
Settlement
0xb8a45e…2fe827
Verifier fee
0.05
✓ 18 checks passed, re-run now
Open →
FAIL
4KInc/mergegate-demo-task
0.25
USDC refunded to buyer
Submission
906e9c8c…162d14
Settlement
0x34eb52…23b6c7
Verifier fee
0.05
✓ 17 checks passed, re-run now
Open →
PASS
4KInc/mergegate-demo-task
0.25
USDC released to provider
Submission
a34a6bf1…9c248a
Settlement
0xe5affe…509229
Verifier fee
0.05
✓ 18 checks passed, re-run now
Open →
Five bound fields rest on the signature alone: settlement_tx, verifier_fee_tx, reason, settlement_asset, settlement_chain. Confirming those means comparing the receipt to the chain, which no offline verifier can do.