Bitcoin Privacy Developer Track. Contribution-first, by design.

12 biweekly 90-minute sessions over 6 months, covering chain analysis, wallet fingerprinting, Silent Payments, Payjoin, Floresta, Kyoto, Lightning privacy, and a contribution sprint. Every session ends with a real open source contribution.

For Developers 6 months · biweekly ~3 hrs/week Free if accepted

Apply to the Track See the modules

12 Sessions

6mo Duration

5–8 PRs per graduate

10+ Target repos

/GitHub_Curriculum_

Season One: 12 sessions, one contribution path.

The public curriculum is now mapped on GitHub: each session teaches one Bitcoin privacy problem, then sends students into a curated issue pool so the work can become a real upstream pull request.

90 min/session

6 months

PR per session

Bitcoin privacy hardware used in Code Orange workshops

Open GitHub track PR checklist

Month by month Full guide →

Month 1

Chain Analysis; Wallet Fingerprinting

Month 2

Coin Selection and UTXO Management; Silent Payments

Month 3

Payjoin; Light Clients with Floresta and Kyoto

Month 4

P2P Privacy and Node Fingerprinting; ASmap and Network Attacks

Month 5

CoinJoin with JoinMarket; OpenSwap

Month 6

Lightning Privacy; Contribution Sprint

~/privacy-track/RULE.md

Every session ends with a contribution. No exceptions.

Not "homework." Not "exercises." A contribution: a PR, a review, an issue triage, a docs fix - something with your name on it, in a real Bitcoin privacy repo, before you log off. Over 12 focused sessions that compounds into a public contribution record no CV can fake.

            # session checklist
            [x] deep-dive - 90 min
            [x] pair on open issues
            [x] ship contribution ✓
            ── merged or it didn't happen
          

/Curriculum_

Six months. Six privacy layers.

Two sessions per month, each module anchored to the live repos you'll contribute to.

/Where_You_Contribute_

Real repos. Real maintainers.

Every PR tracked publicly →

✓ The track is for you if

→ You're comfortable in at least one programming language (Rust helps, not required) → You care about Bitcoin privacy enough to work on it for a year → You want a public contribution record, not a certificate → You can sustain ~3 hrs/week, biweekly sessions, for 6 months

✕ It's not for you if

→ You're brand new to programming - do rawBit first → You want theory without shipping - every session ends in a contribution → You can't commit to a 6-month arc - this is contribution-first by design

Bitcoin privacy needs hands.

Enrollment for the 2026 track is open now. Free for accepted students - your contributions are the tuition.

Apply to the Track Ask in Discord first