Introduction
The Bitcoin Cash (BCH) network underwent a contentious hard fork on November 16, 2018, splitting into two incompatible chains: BCHABC (supported by Bitcoin ABC) and BCHSV (backed by Bitcoin SV). This article analyzes the events leading to the fork and how major exchanges navigated the divide.
The Fork Timeline: A Battle of Hashpower
Pre-Fork Tensions
- November 15, 21:37: SV-aligned Coingeek mined consecutive blocks (556746–556750), signaling early hashpower dominance.
- November 16, 00:35: ABC supporter Bitcoin.com mined block 556758, but SV maintained a real-time hashpower advantage.
The Fork Unfolds
- 00:40: Fork delayed—6 more blocks needed for upgrade activation.
- 01:10: SV miners (Coingeek, SVPool) mined the first three post-fork blocks.
- 01:18: ABC’s Bitcoin.com surged hashpower (+1593% in 24h) to overtake SV temporarily.
- 01:56: Final pre-fork block (556766) mined by SV’s SVPool, marking the official split.
Post-Fork Developments
- 02:05: Bitcoin.com mined ABC’s first independent block.
- 02:24: SV’s Mempool mined its first standalone block (556767).
- By 17:00, ABC led SV by 42 blocks in production.
Exchange Responses: Four Strategic Approaches
A-Type Exchanges (Explicit Support)
- Example: Bitstamp backed ABC exclusively but reserved post-fork reevaluation rights.
- Action: Paused deposits/withdrawals during fork, provided snapshots, and issued clear risk warnings.
B-Type Exchanges (Neutral)
- Majority stance: No alignment; promised 1:1 candy distribution if both chains stabilized.
- Example: HitBTC enabled trading immediately post-fork without snapshots.
C-Type Exchanges (Observers)
- Strategy: Announced snapshots and paused transactions but deferred decisions until chain stability.
- Flexibility: Could later support both chains or pivot to A/D-type strategies.
D-Type Exchanges (Flexible Support)
- Approach: Initially supported one chain (often ABC) but later enabled trading for both.
- Example: Some exchanges distributed SV tokens as "candy" after confirming network stability.
Investor Guidance
Key Considerations
- Asset Safety: Pre-fork BCH holdings were automatically duplicated on both chains.
- Candy Claims: Investors received equivalent tokens (BCHABC/BCHSV) if held during snapshots.
- Exchange Compatibility: Verify which chain(s) an exchange supports before transferring BCH.
- Replay Protection: Some exchanges implemented custom solutions; monitor announcements.
Post-Fork Risks
- Ongoing Hash Wars: Prolonged attacks could destabilize one chain, rendering its tokens worthless.
- Market Volatility: Avoid trading until both chains prove stable or one concedes.
FAQs
Q1: Will my existing BCH be affected by the fork?
A: No. Your BCH balance was cloned onto both chains post-fork (if held during snapshots).
Q2: How do I claim BCHSV if my exchange only supports BCHABC?
A: Contact the exchange—many distributed SV tokens later or listed trading pairs.
Q3: What’s the main difference between BCHABC and BCHSV?
A: ABC increased blocksize to 32MB; SV prioritizes scalability via other technical changes.
Q4: Can the two chains remerge?
A: Unlikely without consensus. Ongoing hashpower battles may determine dominance.
Q5: Which exchanges supported both chains fastest?
A: HitBTC and other B/D-type platforms enabled trading earliest.
👉 Track real-time BCH fork updates
👉 Compare exchange responses to crypto forks
Note: All non-OKX hyperlinks have been removed per guidelines.