Oddbean new post about | logout
▲ ▼
thepurpose | 4 months ago (raw) | root | parent | reply | flag 
 nostr:nprofile1qqstu7jjjx6n969erredexq539y2x0f7pks80zxhg9hh8dx8298s3esppemhxue69uhkummn9ekx7mp0rt8eme: I've had the same question from users as well. Why didn't you implement the function to create a new account within the same wallet file with an absolute derivation path as "advanced settings" when creating a new account?
▲ ▼
craigraw | 4 months ago (raw) | root | parent | reply | flag +1 
 You can do this if you create the new account with a watch only keystore, but I haven’t seen a compelling reason to add this as a general feature.
▲ ▼
thepurpose | 4 months ago (raw) | root | parent | reply | flag +2 
 I got asked about this from a not so experienced pleb wanting to experiment/ migrate from Segwit to Taproot and use both in parallel during transition.

Creating a new wallet file by choosing a file name and setting up a password for the Sparrow wallet file was a downturner for him at that moment. Furthermore, confusion arised about the fact that the user then would have one hardware signing device but several wallet files.

A generic reason to add this could be: Lower the barrier for users to test/ use bitcoin protocol uprades.

However I am unsure if resources should be put into this feature, personally.

One could argure that if someone wants to upgrad to a new protocol version, getting comfortable with multiple wallet files is desirable. As well as keeping complexity of wallet files low seems favourable.