By the end, you’ll be able to…
- Explain a soft fork as a restriction of accepted behavior.
- Avoid treating a proposal number as deployment evidence.
Three questions to carry into this lesson.
Rules change through concrete mechanisms
A soft fork narrows the set of behavior accepted by upgraded validators in a way intended to retain compatibility with older validation rules. Activation mechanisms vary. BIP 9 describes one version-bits signaling approach; it is not a universal description of every past or future upgrade. Study the actual deployment rather than generalizing from one mechanism.
Publication is not adoption
A Bitcoin Improvement Proposal can be a discussion document, specification or historical record. Having a BIP number does not make a proposal accepted, safe or active. Source code availability, releases, signaling and economic adoption are distinct evidence. A miner’s signal and a user’s rule enforcement also play different roles; no single popularity counter captures the whole process.
Disagreement belongs in an open system
Technical review includes adversarial questions about failure modes, compatibility, incentives and maintenance. Supporting Bitcoin does not require treating every proposed feature as an improvement or every critic as an opponent. For a community explanation, identify what is deployed, what is debated and which conclusions are your interpretation. Do not use the project’s Nakamoto standard phrase as though it settles a protocol governance dispute.
Practice on paper
A social post says “BIP 999 exists, therefore every wallet now supports it.” List the missing evidence without assuming anything about that hypothetical proposal.
I’ve tried it — show the worked answer
Check the actual document and status, implementation, deployment conditions and the specific wallet’s released support. Existence in a proposal repository does not establish adoption or interoperability.
Want to explore with buttons and instant feedback? Try the practice lab ↗
Make a choice. Discover why.
Choose an answer and check the explanation. You can retry as often as you like. These are practice questions, not a test of mastery; answers are not saved or sent.
One idea to take with you
Track the path from proposal to enforced behavior.
Your learning, at your pace
Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.
Continue with your next unfinished lesson →
Remove the saved completion marks for this course on this browser? Other courses will stay unchanged.
Saved only in this browser for this website address. Clearing storage, changing device or using a different gateway may lose these marks. No sync, grading or credential; nothing is sent to us. The export is a record for you, not a file this site can import.