Open jp1ac4 opened 5 months ago
What's the issue with the current behaviour?
Perhaps it's not a problem as such, but it's currently possible to pass 0, for example, as the timelock value and get a transaction spending all confirmed coins. Without any check, there's more chance to make a mistake with the value passed in and select more coins than expected.
If passing a
timelock
value to thecreaterecovery
command, we should check if the value corresponds to one of the wallet's recovery paths.