All payouts Paid and confirmed on Starknet
$0.50
Testing campaign · starkscan.co · to 0x5db1…3048
What the chain saysanyone can check this
- Transaction
- 0x6e44…d36e
- Status
- SUCCEEDED
- Block
- 14,108,878
- Recipient
- 0x5db1a00fa6ad44e82de90cae46d82cd5ce052394320d60946ef661db68e3048
The private legwho collected it is not on this ledger
- Vault released0x6e44…d36e
- Escrowed behind
poseidon(secret)0x1cb0…6160 - Collected by the one-time linkcommitment 248547…7888
The money never lands in the wallet that earned it. The claim is keyed by a commitment, not a person; where it goes next — a public address or a shielded note — is theirs alone.
Why Sage paidSage’s own record
- Verdict
- hold · 15% confidence
- Reason
- no_evidence
- Summary
- Recommendation: hold. The URL pattern matches and the evidence link resolves to a /contract/<address> page, but the fetched evidence contains only site navigation boilerplate and none of the required contract-page content (name 'Starknet: Attestation', tab strip, indexed-transactions or Last-received line). Against: every substantive criterion depends entirely on the submitter's note, which is untrusted data, while the verified evidence is silent on those points. A human reviewer should first re-fetch https://starkscan.co/contract/0x10398fe631af9ab2311840432d507bf7ef4b959ae967f1507928f5afe888a99 with a tool that renders the dynamic contract body and re-check criteria 4–6 and 8–10.
Settled by the campaign’s Cairo vault on Starknet (0xa532…ec5b): the vault derived the reward from the mission and could have refused with a code. The amount, recipient and status above come from the chain; the reasoning comes from Sage. See the campaign.