Practice Test Geeks(CBP) Certified Bitcoin Professional Practice Test
← All CBP Flashcard Decks

Forks and Network Upgrades Flashcards

7 cards from real CBP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Forks and Network Upgrades flashcards as text

  1. What is the primary purpose of replay protection in a hard fork event?

    Answer: To ensure transactions on one chain cannot be rebroadcast and confirmed on the other chain

    Replay protection modifies transaction signing so a valid transaction on one fork is invalid on the other, protecting users from unintended fund movement.

  2. Bitcoin Cash implemented which mechanism to adjust mining difficulty more rapidly after its fork from Bitcoin?

    Answer: An Emergency Difficulty Adjustment (EDA) to cope with fluctuating hash rate

    BCH introduced an Emergency Difficulty Adjustment that could lower difficulty significantly if blocks were too slow, addressing hash rate instability post-fork.

  3. When analyzing a proposed hard fork, which factor most directly determines whether two chains will survive long-term?

    Answer: Whether each chain has sufficient economic activity and hash rate to sustain itself

    Long-term chain survival depends on sustained economic value attracting miners and users; without both, a chain collapses.

  4. What does 'flag day' activation mean in the context of Bitcoin forks?

    Answer: A pre-specified block height or date after which nodes enforce new rules unconditionally

    Flag day activation means new rules take effect at a predetermined point regardless of miner signaling percentage.

  5. Which scenario describes an 'accidental hard fork'?

    Answer: A software bug causes some nodes to accept blocks that others reject, temporarily splitting the chain

    The March 2013 Bitcoin incident is a classic example where a BerkeleyDB lock limit bug caused a temporary chain split between v0.7 and v0.8 nodes.

  6. In the context of SegWit2x (2017), why did the hard fork portion ultimately fail to activate?

    Answer: Key signatories withdrew support and the fork lacked sufficient node and economic backing

    Major SegWit2x backers publicly withdrew weeks before the planned November 2017 activation, collapsing support for the 2MB block hard fork.

  7. What is 'wipe-out risk' in the context of a soft fork?

    Answer: The risk that a minority miner chain is completely orphaned by the majority chain enforcing new rules

    In a soft fork, old-rule blocks produced by non-upgraded miners are invalid to upgraded nodes and will be orphaned, 'wiping out' that chain.