You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fifteen missions, one hands-on step (mission 42, the signet transaction). The path is named Full Independence and it's the capstone of the Advanced tier — but after mission 42 the learner reads fourteen lessons about running their own infrastructure without ever touching any.
Missions: 42 (onchain-signet), then 47, 53, 54, 67-76 and 50, all kind: 'knowledge'.
Proposals
Verify a release signature. Download Bitcoin Core (or Sparrow), check the maintainer signatures against the release manifest, and report the fingerprint. This is the single most practical sovereignty skill in the path and it's currently not exercised anywhere.
Point BitPilot at your own node. If the learner runs Core or Electrum, have them submit a value only their node can produce — a block hash at a height we name, for instance. Verifiable against a public explorer, and it proves the node is real and synced without us ever connecting to it.
Prove you can restore. Wipe a test wallet and restore it from the seed, then submit the first derived address. The derive-address kind (mission 41) already does the derivation half client-side, so the plumbing largely exists. "I have a backup" is a belief until the day you test it.
Multi-explorer cross-check. Ask for the same block hash from two independent sources and confirm they agree. Small exercise, but it's the concrete version of "don't trust, verify" that the path keeps asserting.
Mission 50 — You made it is the graduation lesson and should stay as it is.
Notes for contributors
verify_signet_txid in backend/src/routes/missions.rs shows the pattern for asking an external explorer and turning the answer into a pass or fail, including how to distinguish "not found" from "couldn't reach it".
Mind the failure modes: an exercise that depends on a third-party service should fail as "try again", never as "you got it wrong". See the same function for how that's handled.
Part of #76.
Fifteen missions, one hands-on step (mission 42, the signet transaction). The path is named Full Independence and it's the capstone of the Advanced tier — but after mission 42 the learner reads fourteen lessons about running their own infrastructure without ever touching any.
Missions: 42 (
onchain-signet), then 47, 53, 54, 67-76 and 50, allkind: 'knowledge'.Proposals
Verify a release signature. Download Bitcoin Core (or Sparrow), check the maintainer signatures against the release manifest, and report the fingerprint. This is the single most practical sovereignty skill in the path and it's currently not exercised anywhere.
Point BitPilot at your own node. If the learner runs Core or Electrum, have them submit a value only their node can produce — a block hash at a height we name, for instance. Verifiable against a public explorer, and it proves the node is real and synced without us ever connecting to it.
Prove you can restore. Wipe a test wallet and restore it from the seed, then submit the first derived address. The
derive-addresskind (mission 41) already does the derivation half client-side, so the plumbing largely exists. "I have a backup" is a belief until the day you test it.Multi-explorer cross-check. Ask for the same block hash from two independent sources and confirm they agree. Small exercise, but it's the concrete version of "don't trust, verify" that the path keeps asserting.
Mission 50 — You made it is the graduation lesson and should stay as it is.
Notes for contributors
verify_signet_txidinbackend/src/routes/missions.rsshows the pattern for asking an external explorer and turning the answer into a pass or fail, including how to distinguish "not found" from "couldn't reach it".frontend/src/lib/types.ts. See Curriculum: 91 of 106 missions end at a quiz #76 for the guide to adding a newDoKind.