-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove unlock wallet #3424
remove unlock wallet #3424
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does't really fix the issue. One way you can try it out is to create a new account, then sign a message with an address from that account: you'll get an "account not encrypted" error.
This also affects LN wallet creation when creating a new account is chosen (vs using an existing account). |
695b77b
to
cf06cd1
Compare
You are right. This should fix it now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Manually creating new account and new LN account are working, but it seems DEX and Mixer accounts are still not encrypted after creation.
Mixer and DEX account creation are using wallet.getNextAccount
directly instead of the one from control actions
RIght, I change them to use the getNextAccountAttempt, instead. Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The four account creation triggers (new account, LN account, dex account and mixer account) are now working as intendend.
Thanks!
closes #3420.
The unlock is not necessary as we sent the passphrase through the grpc request so dcrwallet can make the unlock.