Skip to content
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

qt: Fix wallet encryption dialog #3816

Merged
merged 1 commit into from
Nov 15, 2020
Merged

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Nov 15, 2020

Should not rely on checked status of encryptWalletAction after #3770

Do not rely on `checked` status of `encryptWalletAction`
@UdjinM6 UdjinM6 added this to the 16.1.1 milestone Nov 15, 2020
@xdustinface xdustinface linked an issue Nov 15, 2020 that may be closed by this pull request
Copy link

@xdustinface xdustinface left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK

Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK, tested encrypting a wallet, then unlocking, then locking, then changing password, then unlocking, then locking.

All worked

@UdjinM6 UdjinM6 merged commit 3391bd6 into dashpay:develop Nov 15, 2020
UdjinM6 added a commit to UdjinM6/dash that referenced this pull request Nov 15, 2020
Do not rely on `checked` status of `encryptWalletAction`
UdjinM6 added a commit to UdjinM6/dash that referenced this pull request Nov 15, 2020
Do not rely on `checked` status of `encryptWalletAction`
UdjinM6 added a commit to UdjinM6/dash that referenced this pull request Nov 15, 2020
Do not rely on `checked` status of `encryptWalletAction`
@UdjinM6 UdjinM6 mentioned this pull request Nov 15, 2020
@UdjinM6 UdjinM6 deleted the fix_gui_encryption branch November 26, 2020 13:26
xdustinface pushed a commit to xdustinface/dash that referenced this pull request Dec 18, 2020
…llet

Add label API to wallet RPC.

This is one step towards dashpay#3816 ("Remove bolt-on account system") although it doesn't
actually remove anything yet.

These initially mirror the account functions, with the following differences:

- These functions aren't DEPRECATED in the help
- Help mentions 'label' instead of accounts. In the language used, labels are
  associated with addresses, instead of addresses associated with labels. (unlike
  with accounts.)
- Labels have no balance
  - No balances in `listlabels`
  - `listlabels` has no minconf or watchonly argument
- Like in the GUI, labels can be set on any address, not just receiving addreses
- Unlike accounts, labels can be deleted.
  Being unable to delete them is a common annoyance (see dashpay#1231).
  Currently only by reassigning all addresses using `setlabel`, but an explicit
  call `deletelabel` which assigns all address to the default label may make
  sense.

Thanks to Pierre Rochard for test fixes.
xdustinface pushed a commit to xdustinface/dash that referenced this pull request Dec 18, 2020
Add label API to wallet RPC.

This is one step towards dashpay#3816 ("Remove bolt-on account system") although it doesn't
actually remove anything yet.

These initially mirror the account functions, with the following differences:

- These functions aren't DEPRECATED in the help
- Help mentions 'label' instead of accounts. In the language used, labels are
  associated with addresses, instead of addresses associated with labels. (unlike
  with accounts.)
- Labels have no balance
  - No balances in `listlabels`
  - `listlabels` has no minconf or watchonly argument
- Like in the GUI, labels can be set on any address, not just receiving addreses
- Unlike accounts, labels can be deleted.
  Being unable to delete them is a common annoyance (see dashpay#1231).
  Currently only by reassigning all addresses using `setlabel`, but an explicit
  call `deletelabel` which assigns all address to the default label may make
  sense.

Thanks to Pierre Rochard for test fixes.
xdustinface pushed a commit to xdustinface/dash that referenced this pull request Dec 22, 2020
Add label API to wallet RPC.

This is one step towards dashpay#3816 ("Remove bolt-on account system") although it doesn't
actually remove anything yet.

These initially mirror the account functions, with the following differences:

- These functions aren't DEPRECATED in the help
- Help mentions 'label' instead of accounts. In the language used, labels are
  associated with addresses, instead of addresses associated with labels. (unlike
  with accounts.)
- Labels have no balance
  - No balances in `listlabels`
  - `listlabels` has no minconf or watchonly argument
- Like in the GUI, labels can be set on any address, not just receiving addreses
- Unlike accounts, labels can be deleted.
  Being unable to delete them is a common annoyance (see dashpay#1231).
  Currently only by reassigning all addresses using `setlabel`, but an explicit
  call `deletelabel` which assigns all address to the default label may make
  sense.

Thanks to Pierre Rochard for test fixes.
xdustinface pushed a commit to xdustinface/dash that referenced this pull request Dec 22, 2020
Add label API to wallet RPC.

This is one step towards dashpay#3816 ("Remove bolt-on account system") although it doesn't
actually remove anything yet.

These initially mirror the account functions, with the following differences:

- These functions aren't DEPRECATED in the help
- Help mentions 'label' instead of accounts. In the language used, labels are
  associated with addresses, instead of addresses associated with labels. (unlike
  with accounts.)
- Labels have no balance
  - No balances in `listlabels`
  - `listlabels` has no minconf or watchonly argument
- Like in the GUI, labels can be set on any address, not just receiving addreses
- Unlike accounts, labels can be deleted.
  Being unable to delete them is a common annoyance (see dashpay#1231).
  Currently only by reassigning all addresses using `setlabel`, but an explicit
  call `deletelabel` which assigns all address to the default label may make
  sense.

Thanks to Pierre Rochard for test fixes.
gades pushed a commit to cosanta/cosanta-core that referenced this pull request Jan 28, 2022
Do not rely on `checked` status of `encryptWalletAction`
gades pushed a commit to cosanta/cosanta-core that referenced this pull request Mar 12, 2022
Add label API to wallet RPC.

This is one step towards dashpay#3816 ("Remove bolt-on account system") although it doesn't
actually remove anything yet.

These initially mirror the account functions, with the following differences:

- These functions aren't DEPRECATED in the help
- Help mentions 'label' instead of accounts. In the language used, labels are
  associated with addresses, instead of addresses associated with labels. (unlike
  with accounts.)
- Labels have no balance
  - No balances in `listlabels`
  - `listlabels` has no minconf or watchonly argument
- Like in the GUI, labels can be set on any address, not just receiving addreses
- Unlike accounts, labels can be deleted.
  Being unable to delete them is a common annoyance (see dashpay#1231).
  Currently only by reassigning all addresses using `setlabel`, but an explicit
  call `deletelabel` which assigns all address to the default label may make
  sense.

Thanks to Pierre Rochard for test fixes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Newly generated wallets can not be encrypted (v0.16.1.0)
3 participants