Make exotic sat management easier

[casey]

It should be easier to deal with rare and exotic sats.

We should add a locked or special or whatever field to the config file, so that users can mark special UTXOs and sats as not to be used for any transaction.

Users should be able to:

• Prevent a UTXO from being automatically selected
• Prevent a sat from being automatically selected (if you have locked sats but the index doesn't have a sat index, complain and refuse to run, because we don't know where that sat is)
• Prevent a range of sats from being automatically selected

[casey]

We could also call this tracked, or something. Or maybe that should be a separate setting, for things you want to keep track of, but don't want to lock.

[raphjaph]

I think that should probably be done through labels in the Bitcoin Core wallet

[casey]

I was thinking about it, and I think there might be some drawbacks to using labels:

• ord wallet restore accepts a mnemonic or descriptor, which doesn't include any information about special sats. So if a user restores from a mnemonic, they'll lose information about special sats. Of course, a config wouldn't be restored along with the wallet, but at least the config file is user-created, user-managed data, so it's more obvious that they need to back up their config file if they want to keep tracking special sats.
• Bitcoin core labels UTXOs, so if a user does a transaction in sparrow which transfers a special sat to another UTXO controlled by the wallet, the new UTXO won't be labeled, whereas if it's in a config file, the wallet will continue to track it.
• A user might want to mark a sat as special before they've received it, so that when they do receive it, they don't accidentally transfer it. Since you can only label UTXOs that exist, they couldn't do this with bitcoin core wallet labels.
• A user might want to track a range of sats, which exist in more than one UTXO in the wallet. They could label multiple UTXOs, but this would mean multiple labels, when what they're really interested in is a single range of sats, which could be covered by a single config file entry.

[1stBitcoinSent]

looking forward to support for locking specific sat numbers and pre-built lock lists for rare, exotic and historic sat numbers 😁

[1stBitcoinSent]

maybe instead adding a fee wallet arg? as sat management involves much 🤔

[1stBitcoinSent]

Thank you very much @raphjaph 😁 Looking forward to this! 🧡