CBP - Certified Bitcoin Professional Forks and Network Upgrades Questions and Answers 1 — Questions and Answers
Question 1: What is the fundamental distinction between a hard fork and a soft fork in the context of Bitcoin network upgrades?
- A soft fork is a temporary chain split, while a hard fork is permanent.
- A hard fork requires a majority of miners to upgrade, while a soft fork requires a majority of users.
- A soft fork tightens consensus rules and is backward-compatible, while a hard fork changes rules in a non-backward-compatible way. (Correct answer)
- Soft forks are for minor bug fixes, whereas hard forks are for major feature additions.
Correct answer: A soft fork tightens consensus rules and is backward-compatible, while a hard fork changes rules in a non-backward-compatible way.
The core difference lies in backward compatibility. A soft fork is an upgrade where new rules are a subset of the old rules (i.e., more restrictive), allowing non-upgraded nodes to still see new blocks as valid. [11, 25] A hard fork introduces a rule change that makes blocks created by upgraded nodes invalid to old nodes, thus it is not backward-compatible and requires all participants to upgrade to remain on the same network. [14, 22]
Question 2: The Segregated Witness (SegWit) upgrade was implemented as a soft fork. How did this implementation method allow the network to upgrade without forcing all nodes to update their software immediately?
- It created a separate, optional blockchain for SegWit transactions that older nodes could ignore.
- The witness data was structured in a way that older nodes would see the transactions as valid, even though they couldn't fully interpret the new data. [8, 15] (Correct answer)
- It required all miners to signal support, which automatically pushed the update to all nodes.
- It was implemented via a hard fork but was called a soft fork for political reasons.
Correct answer: The witness data was structured in a way that older nodes would see the transactions as valid, even though they couldn't fully interpret the new data. [8, 15]
SegWit was a soft fork where the new witness data was segregated from the main transaction data. [15, 24] This new data was structured in a way that older, non-upgraded nodes would see the transaction as valid (specifically, as an 'anyone-can-spend' output which they don't enforce strictly), even though they couldn't validate the new witness signatures. This maintained backward compatibility. [18]
Question 3: In 2017, a contentious hard fork resulted in the creation of Bitcoin Cash (BCH). Which of the following was a direct and immediate consequence for users who held Bitcoin at the time of the fork?
- They ended up holding an equal amount of coins on both the BTC and BCH chains, as the transaction history was duplicated up to the point of the split. (Correct answer)
- Their BTC was automatically converted to BCH on the new chain.
- They were required to choose which chain to support, forfeiting their coins on the other.
- All transaction history was erased on the new BCH chain to provide a clean start.
Correct answer: They ended up holding an equal amount of coins on both the BTC and BCH chains, as the transaction history was duplicated up to the point of the split.
A hard fork that results in a chain split duplicates the entire blockchain ledger up to the fork block. [4] This means anyone who held BTC before the split now held the same amount of BTC on the original chain and a new, separate asset (BCH) on the forked chain, accessible with the same private keys. [5, 7]
Question 4: Which of the following represents the most significant risk associated with implementing a non-unanimous hard fork on the Bitcoin network?
- A temporary decrease in transaction fees.
- The requirement for all users to generate new private keys.
- An automatic increase in the block size limit.
- A permanent chain split if there is not overwhelming consensus, leading to two competing cryptocurrencies. (Correct answer)
Correct answer: A permanent chain split if there is not overwhelming consensus, leading to two competing cryptocurrencies.
The primary risk of a contentious hard fork is a lack of network-wide consensus. If a significant portion of the network (miners, nodes, users, businesses) does not agree to the new rules, the blockchain can permanently split into two distinct and competing versions, creating confusion, fragmenting the community, and diluting the network effect and security. [12, 14, 31]
Question 5: A Bitcoin Improvement Proposal (BIP) suggests a new feature to be activated as a soft fork using a miner-signaling mechanism like BIP 9. What does it mean when miners "signal" for the upgrade?
- They send a special transaction to a designated address to cast their vote.
- They include specific data (a version bit) in the headers of the blocks they mine to indicate their readiness for the new rules. (Correct answer)
- They verbally agree to the change in public forums and developer mailing lists.
- They stop mining blocks until the new rules are officially accepted by all major exchanges.
Correct answer: They include specific data (a version bit) in the headers of the blocks they mine to indicate their readiness for the new rules.
Miner-activated soft forks, such as those using the BIP 9 version bits mechanism, require miners to signal their readiness by setting specific bits in the block headers they produce. [3, 21] Once a certain threshold of blocks within a difficulty period signals readiness (e.g., 95%), the new rules are "locked-in" and will activate shortly thereafter. [27, 29]
Question 6: A new soft fork upgrade is scheduled to activate on the Bitcoin network. As an operator of a non-mining full node, what is the primary consequence of choosing NOT to upgrade your software?
- Your node will be banned from the network and will stop receiving any new blocks.
- Your node will continue to operate but will have a less secure or complete view of the blockchain's state, as it cannot fully validate the new rules. (Correct answer)
- Your node will automatically reject all transactions, both old and new, until it is upgraded.
- Your node will cause a hard fork because it is enforcing the old rules.
Correct answer: Your node will continue to operate but will have a less secure or complete view of the blockchain's state, as it cannot fully validate the new rules.
Because a soft fork is backward-compatible, a non-upgraded node will still see new blocks created under the new rules as valid and will continue to sync with the network. [2] However, it will not be able to enforce the new, tighter rules itself. It relies on the upgraded majority of miners to enforce them correctly, thus reducing its own validation security and becoming, in a sense, a less-than-full node regarding the new features. [11, 20]
CBP - Certified Bitcoin Professional Forks and Network Upgrades Questions and Answers 1
What is the fundamental distinction between a hard fork and a soft fork in the context of Bitcoin network upgrades?