tasknull documentation
tasknull turns a completed bounty into a cryptographic receipt. Reviewers can confirm the work is real and that the claim can't be spent twice — without ever learning which wallet did it.
The problem
Today, claiming a bounty usually means doxxing yourself. Either your wallet is attached to the payout for everyone to trace, or your contribution can't be trusted. There is no middle ground: privacy and provability seem to pull in opposite directions.
The third path
tasknull adds a third option — provable completion with an unlinkable identity. It rests on three guarantees:
- Verifiable completion — every claim carries a proof that the bounty's acceptance criteria were met. Reviewers check the math, not your reputation.
- Unlinkable identity — the payout wallet and the proof are cryptographically separated. A verifier learns "valid hunter", never which hunter.
- No double-claims — each claim emits a one-way nullifier. Reuse the same solution twice and the second nullifier collides, so the claim is rejected.
Who it's for
- Security researchers — claim a disclosure bounty without tying the patch or the payout to a real name or employer.
- Freelance hunters — build a track record through stable nullifiers while keeping every wallet single-use and clean.
- DAO contributors — let a treasury reward completed work on-chain without a public map of who did what for whom.
Status — v0.1 reference implementation. The cryptography (identity, commitments, nullifiers, signatures, double-claim prevention) is real and runs locally today via the CLI. On-chain settlement on Solana is simulated locally until the
$TNULL program launches (mint address TBA).Where to go next
- How it works — the commit → prove → settle flow.
- Core concepts — identities, commitments, and nullifiers explained.
- Installation — get the CLI running in a minute.
- CLI reference — every command, with examples.