Skip to content

Conversation

Sjors
Copy link
Member

@Sjors Sjors commented Jan 6, 2020

Sorry for bike-shedding, but I find this default confusing:
Schermafbeelding 2020-01-06 om 12 49 15

We don't encrypt the default wallet by default, so I don't think we should do it with new wallets. When creating a watch-only wallet - which I suspect is a more common use case than a second regular wallet - you have to uncheck the box first before you can check the watch-only box.

This PR unchecks the encryption box by default:
Schermafbeelding 2020-01-06 om 12 56 10

@achow101
Copy link
Member

achow101 commented Jan 6, 2020

Concept NACK. I think we should create encrypted wallets by default. It's harder to do that on the command line that it is in the GUI since it requires user interaction.

@instagibbs
Copy link
Member

concept NACK in general. Maybe we should allow "Disable private keys" to be clicked, which unclicks the "Encrypt wallet" checkbox?

@Sjors
Copy link
Member Author

Sjors commented Jan 8, 2020

Maybe we should allow "Disable private keys" to be clicked, which unclicks the "Encrypt wallet" checkbox?

That seems like a reasonable UX compromise.

@Sjors Sjors closed this Jan 8, 2020
@luke-jr
Copy link
Member

luke-jr commented Jan 26, 2020

tbh, this whole dialog looks very user-unfriendly.

What does "Make Blank Wallet" even mean to an end user?? ("Disable Private Keys" is probably borderline confusing itself)

@bitcoin bitcoin locked as resolved and limited conversation to collaborators Feb 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants