BIP-110 has activated. What now?
This post assumes you do not care about the BIP-110 fork coins.
The hashrate on BIP-110 is extremely low, and it is unlikely that these coins will have any value or be sellable.
Sending “fork coins”
Assume that any transaction you make on the BIP-110 fork will also execute on the main Bitcoin network. For this reason, avoid any transactions on the fork.
An example is someone might offer to buy your BIP-110 coins. DO NOT DO THIS! If you send them 0.1 BTC on the fork, they can also get 0.1 BTC on the main chain and scam you!
“Replay protection” tools
I would strongly recommend avoiding any “replay protection” tools. These tools may not be tested and can put your funds or privacy at risk.
Care also needs to be taken to not link your stack if you transact on both chains.
Onchain funds
Your onchain funds will not be affected by BIP-110. There is no action required.
My bitcoin node
Your bitcoin node does not require any change. Whether you run the newest or an old version, this fork will not affect you in any way.
LN nodes
Your LN node will not lose any funds by design.
If you have any BIP-110 enabled peers, the channel will stop routing, and may eventually go offline or force close itself.
You should immediately cooperatively close these channels to avoid force close fees and locks! If you don’t, you will have to force close, but you will not lose funds (only more costs).
In your local routing logs, look for the EXPIRY_TOO_SOON error. This indicates that there is a disagreement on the block height.
Only close the channel if this error is occurring more than usual, alongside little routing, not because of a few errors.
Miners
If you use Ocean or another pool that supports BIP-110, you will want to use the non-BIP-110 endpoint to ensure you earn mining rewards.
Write a comment