All payouts Paid and confirmed on Starknet
$0.50
Testing campaign · starkscan.co · to 0x4f1f…f434
What the chain saysanyone can check this
- Transaction
- 0x1a58…c694
- Status
- SUCCEEDED
- Block
- 14,110,356
- Recipient
- 0x4f1f6530f84e4a1db7fa35bafc313174a2482a54c775c4321487eb0fe91f434
The private legwho collected it is not on this ledger
- Vault released0x1a58…c694
- Escrowed behind
poseidon(secret)0x4939…3f3b - Collected by the one-time linkcommitment 267411…8689
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 · 35% confidence
- Reason
- no_evidence
- Summary
- The submission note is detailed and the evidence URL itself confirms the correct contract-page path, but the fetched page text contains only the site's navigation and footer with no contract name, tab strip, or transaction summary — the very content the criteria require. The strongest counter-fact is that the evidence is incomplete (the page shows 'Checking...'), so the contract data may simply not have been captured, but per the evidence-only rule the populate-the-page criteria (4–6, 8–10) cannot be verified. A human should re-fetch the evidence URL after the page fully loads and verify the contract name 'Starknet: Attestation', the five-tab strip, and the 'Last received' / indexed-transactions summary appear verbatim in the page body.
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.