[PROPOSAL] Removal of proposal to make CSV delay symmetric



Summary:

In a conversation about bruteforcing on the CSV delay, Pierre asks how it would differ from a BIP32 wallet with look ahead keys, noting that they could try with the most probable values first. The response is that the use of CSV can be specified by the counterparty and therefore offers a big multiplier in terms of the number of variants to look for per key. However, restricting CSV delays to be multiples of 144 between 144 and 2016 would only be 14 variants. It is suggested that one of 6, 36, 144, 432 or 1008 would probably be more than enough choice. The discussion then moves on to the issue of normal bitcoin wallets not being able to deal with this, which is unfortunate. Rusty notes that funds are still recoverable with just the seed, which is a huge improvement compared to what is currently the case. Local commitments are not usually in play, but if your node drops out, remote commitments certainly will be. Finally, it is noted that being able to rescue some funds from a pre-lightning wallet is a nice thing to have at this stage, although in five years' time it might not be as useful.


Updated on: 2023-06-02T19:30:38.117177+00:00