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

Warn when sending to already-used Bitcoin addresses #562

Closed
wants to merge 14 commits into from

Conversation

luke-jr
Copy link
Member

@luke-jr luke-jr commented Mar 1, 2022

Entering a used address in the GUI Send tab makes the field turn yellow. Sending to a used address from the GUI prompts with detailed information about prior usage, as well as a note about best practices to avoid address reuse.

Continued from bitcoin/bitcoin#15987 (significantly modified/rewritten - no more bloom filter)

Depends on bitcoin/bitcoin#22693 for non-GUI changes

@luke-jr luke-jr marked this pull request as draft March 1, 2022 19:45
@DrahtBot
Copy link
Contributor

DrahtBot commented Mar 2, 2022

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews

See the guideline for information on the review process.

Type Reviewers
Concept ACK RandyMcMillan, Rspigler

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

Conflicts

Reviewers, this pull request conflicts with the following ones:

  • #555 (Restore Send button when using external signer by Sjors)
  • #553 (Change address / amount error background by w0xlt)
  • #537 (Point out position of invalid characters in Bech32 addresses by luke-jr)
  • #536 (Add address error location to GUI by meshcollider)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

@DrahtBot
Copy link
Contributor

🐙 This pull request conflicts with the target branch and needs rebase.

Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

@RandyMcMillan
Copy link
Contributor

Concept ACK

@Rspigler
Copy link
Contributor

Concept ACK. Can test when taken out of Draft

@katesalazar
Copy link
Contributor

Great idea, thanks. Hope doesn't break anything.

@DrahtBot
Copy link
Contributor

There hasn't been much activity lately and the patch still needs rebase. What is the status here?
  • Is it still relevant? ➡️ Please solve the conflicts to make it ready for review and to ensure the CI passes.
  • Is it no longer relevant? ➡️ Please close.
  • Did the author lose interest or time to work on this? ➡️ Please close it and mark it 'Up for grabs' with the label, so that it can be picked up in the future.

@DrahtBot
Copy link
Contributor

There hasn't been much activity lately and the patch still needs rebase. What is the status here?

  • Is it still relevant? ➡️ Please solve the conflicts to make it ready for review and to ensure the CI passes.
  • Is it no longer relevant? ➡️ Please close.
  • Did the author lose interest or time to work on this? ➡️ Please close it and mark it 'Up for grabs' with the label, so that it can be picked up in the future.

@hebasto
Copy link
Member

hebasto commented Mar 27, 2023

Closing this due to lack of activity. Feel free to reopen.

@hebasto hebasto closed this Mar 27, 2023
@bitcoin-core bitcoin-core locked and limited conversation to collaborators Mar 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants