I probably have time to complete one more BIP-110 related project before mandatory signaling starts. I have two projects started that could help, but can probably only deliver one of them at most (and only if I focus solely on it). I thought I’d get input from the forum on which one you think I should complete first.
-
The first one is a custom Lightning watchtower which observes the status-quo chain, and if there is a chain split it protects your channels from the channel partner cheating you on the opposite chain (if they know you are running BIP-110 and construct the attack in a way that the offending transaction is rejected by your mempool so your lightning node never sees it). It would submit the dispute to the status-quo chain on your node’s behalf and sweep the channel funds in your favor. Then if BIP-110 were to fail and you switch back to the status-quo chain, your lightning funds would be sitting safely in your on-chain wallet.
-
The second one is a fork of Datum Gateway that addresses the “difficulty” problem with Mining Rig Rentals, which results in a fair amount of sats lost due to rigs not being able to mine up to their advertised hashrate. Any time the reason for a degraded hash rate is related to the difficulty adjustment on the pool (Datum Gateway in this case), MRR decides in favor of the rig owner and does not refund the difference. A custom Datum Gateway that communicates with each rig on their own terms would make Pickhash a more realistic alternative to Braiins Hashpower.
If you are interested in voting on this, pick one here:
- Lightning chain-split watchtower
- Datum Gateway fork for MRR