Hello everyone! I'm Nanjo, an engineering intern. This article summarizes my research findings about separating BSV and BCH - two cryptocurrencies born from a fork approximately one month ago.
Table of Contents
- Understanding Bitcoin SV (BSV)
- The Separation of BCH and BSV
- Dust Transaction Method
- Key Takeaways
- FAQs
- References
Understanding Bitcoin SV (BSV)
"BSV represents the original Bitcoin. It restores the original Bitcoin protocol while maintaining stability and enabling massive scaling. BSV continues to uphold Satoshi Nakamoto's 2008 vision."
(Source: Bitcoinsv.io)
BSV is a BCH fork announced by nChain on August 16, 2018. The project aims to return closer to Satoshi Nakamoto's original Bitcoin protocol design through these key modifications:
- Restoring original opcodes: OP_MUL, OP_LSHIFT, OP_RSHIFT, OP_INVERT
- Removing the 201-opcode per script limit
- Increasing maximum block size to 128MB
(Reference: Bitcoin SV Full Node Implementation)
The Separation of BCH and BSV
Following the November 16, 2018 hard fork, each private key controls both BCH and BSV balances simultaneously. Since replay protection wasn't implemented, transactions get mirrored across both chains - creating inconvenience for users who want to send currencies separately.
๐ Learn more about cryptocurrency forks
Splitting Using nLockTime
What is nLockTime?
"Locktime is a transaction attribute that prevents validation until specified time. Transactions with locktime remain cancelable until the locktime expires."
(Source: Bitflyer Glossary)
How It Works
- Identify the longer chain (currently BCH)
- Broadcast a transaction with current BCH block height as nLockTime
- BCH (longer chain) will confirm the transaction
- BSV (shorter chain) won't confirm due to nLockTime
- Modify and rebroadcast the unconfirmed BSV transaction to a new address
Note: This method requires at least 3 blocks difference between chains.
Dust Transaction Method
This alternative approach uses dust transactions (small UTXOs existing only on BCH chain post-fork):
- Acquire new BCH-only UTXOs from faucets
- Create a transaction combining old (both chains) and new (BCH-only) UTXOs
- BCH chain will confirm the transaction
- BSV chain rejects it due to invalid inputs
- Send BSV balance to a new address
๐ Understanding UTXO management
Key Takeaways
While both methods effectively split BCH and BSV balances, they remain temporary solutions until proper replay protection gets implemented. For most users, waiting for official replay protection might be preferable.
FAQs
Q: Why separate BCH and BSV?
A: Without separation, transactions get mirrored across both chains, limiting flexibility in managing each currency independently.
Q: Which method is better?
A: The nLockTime method is more technical but cleaner. Dust transactions are simpler but require finding suitable UTXOs.
Q: When will replay protection be implemented?
A: While announced by CoinGeek, the implementation timeline remains uncertain. Monitor official BSV channels for updates.
Q: Are there risks in splitting?
A: Both methods carry minor risks if not executed properly. Consider consulting technical documentation or experienced users.
Q: Where can I learn more about blockchain forks?
A: Reputable cryptocurrency exchanges and developer forums often provide excellent educational resources about forks and chain splits.
References
- Bitcoin SV Official Site
- nChain Development Blog
- Bitflyer Glossary
- Bitcoin.com Faucet
- CoinGeek Announcements
Key SEO improvements made:
1. Natural keyword integration ("cryptocurrency fork", "UTXO management", "blockchain forks", etc.)
2. Clear hierarchical structure with optimized headings
3. Added valuable FAQs
4. Strategic anchor text placement
5. Removed promotional content while preserving core information
6. Professional yet accessible language