split-bip110

A tool to split BIP110 coins from BTC by transferring UTXOs one-to-one to new addresses of a separate wallet.

How it works

Each UTXO is sent to a unique receive address on the destination wallet. UTXOs are not consolidated, except when:

• They share the same address (automatic grouping)
• They are surrounded by [ ] brackets in the UTXO file

Every input is signed with the unified sighash (SIGHASH_ALL | SIGHASH_UNIFIED, hash type 0x21), which is specific to the BIP110 chain. A transaction signed this way is invalid on the regular BTC chain (Bitcoin Core rejects it with "Signature hash type missing or not understood"), and therefore cannot be replayed onto it.

To check your transactions, you can verify, for example, they are valid on BIP110's mempool.guide and invalid on BTC's mempool.space.

Setup

1. Export UTXO list from Sparrow Wallet

Export your UTXO list as a CSV file. The expected format matches Sparrow's export:

Date (UTC),Output,Address,Label,Value
2024-12-14 06:40:21,7c87ca...:2,tb1qt35r...,label,0.00333454

To consolidate specific UTXOs into one transaction, wrap them with brackets:

[
2024-12-14 06:40:21,7c87ca...:2,tb1qt35r...,,0.00333454
2024-12-14 06:40:21,af378d...:1,tb1q5ecv...,,0.00103000
]
2024-12-14 06:42:21,a00ab5...:0,tb1qgu3r...,,0.00077221

In the example above, the first 2 UTXOs will be joined into a single transaction.

2. Set up your wallets

Source wallet. This is the wallet you are migrating from. It can be a regular HD wallet (single seed) or an m-of-n multisig wallet. For multisig, you need the seed words (and optional passphrases) of all co-signers. The tool uses BIP48 derivation (m/48'/coin'/0'/2'/0|1/index) with BIP67-sorted pubkeys, matching Sparrow's multisig wallet format.

Destination wallet. Create a new wallet to host only your BIP110 coins (Sparrow, Electrum, Iancoleman's BIP39, etc.) and take note of the xpub. Alternatively, if you want all coins sent to a single address (for example, an exchange), you can skip the xpub and set address in the config instead.

3. Configure config.toml

Fill in the following fields:

# Path to the exported UTXO CSV file
utxo_file = "your-utxos.csv"

# Network: mainnet or testnet
network = "mainnet"

[source_wallet]
# Option 1: single-sig:
# Fill seed with the seed words and optional BIP39 passphrase
seed = "word1 word2 ... wordN"
passphrase = ""

# Option 2: multisig (m-of-n):
# Fill all seeds and the threshold. If 2-of-3, there will be 3 seeds/passphrases and threshold = 2.
seed1 = "word1 word2 ... wordN"
passphrase1 = ""
seed2 = "word1 word2 ... wordN"
passphrase2 = ""
seed3 = "word1 word2 ... wordN"
passphrase3 = ""
threshold = 2

# Max addresses to derive when searching for UTXO private keys (default: 2000)
address_limit = 2000

[destination_wallet]
# Option 1: xpub of the receiving wallet
xpub = "xpub..."
# Address type: segwit, taproot, legacy, or p2sh
type = "segwit"

# Option 2: send all transactions to a single address (ignores xpub/type/initial_index)
# address = "bc1q..."

[transaction]
# Fee rate in sat/vb (minimum: 1, default: 1)
fee_rate = 1.03
# Random fee variation in basis points (default: 0)
fee_variation = 50

4. Run

Download the binary for your platform from the releases page. Place config.toml and your UTXO CSV file alongside the binary, then run it.

This produces two files:

• raw-txs.txt — raw transaction hex (one per line)
• tx-report.txt — summary report with fees and amounts

Compiling from source

npm install
npm run pkg

Warning

Always verify the generated transactions before broadcasting. For example, make sure the destination addresses are what you expect.

Important warning about legacy (P2PKH) wallets: since this program runs offline, it has to fully trust the UTXO CSV file and cannot check if the UTXO value is correct. This is not a problem for segwit (including taproot) UTXOs, because the values are signed, but for legacy UTXOs, you have to make sure the values are correct or part of the UTXO could be wasted in fees. Sparrow will export the CSV file with correct values, but keep in mind this warning if you're editing the CSV file!

This software comes with no warranty. You are solely responsible for verifying that the transactions are correct. Bugs could result in loss of funds.

Donation

If this project helped you earn something and you are feeling grateful, you can share a bit with:

• Lightning: fiscalhawk44@walletofsatoshi.com
• Silent Payments: sp1qqdx6zdc0guc4ncu2wv74hhy2ql8wnxhas0hl9q8sxdxhz253c6xq5quj7kedy36lfl4yau7cph0dtzxvltzwwdutw4ct5x9clrvpkz8nxv0kpwdt
• BIP47: PM8TJgutCtE1GK1Lf6WUTRLzVNcBvNRXjKueKgpQ36dc6Dry3w5oCYz5NEVk7GvNpXAMdrioi6DVytk1P4RBGjXpLw1VFfTm2dNrdtTUWQCQtcjDwPVm or PayNym: +otto
• XMR: 84ASExDrrRGBgmYFCzFf6sKK4Q3gwynpzBqp3ZZfNUb4WpbAGJUJ2nrSAEfNLv3FacD5suRMLUzNCAL6XkR7bhe9QKfchu7
• Or ask for an address on cautious_uncrown054@simplelogin.com.

License

This project is free to use, copy, and modify. The author is not responsible for any bugs or issues that may cause financial loss. Use at your own risk.