Skip to content
This repository has been archived by the owner on Sep 8, 2020. It is now read-only.

FEATURE REQUST: Signing newly created addresses #69

Open
ChristopherA opened this issue Nov 30, 2017 · 0 comments
Open

FEATURE REQUST: Signing newly created addresses #69

ChristopherA opened this issue Nov 30, 2017 · 0 comments

Comments

@ChristopherA
Copy link

This is based on a conversation with @gmaxwell yesterday:

There have in the past been a number of bugs in code in the creation of addresses, many of which are intermittent (one in 256 in one of his examples, in other the Electrum wallet would create a bad address if a block was received at exactly the same time). Thus as a general practice, he signs an address with its own private key and then verifies that its signature is valid. He says that bitcoind now does this internally every time it creates a new address.

I'd like confirm that the ledger bitcoin app does best practice this like bitcoind app does, i.e. double checking that the address is valid. Secondly, I'd like to see that this entire package (signed address) be sent to the chrome app, and that the chrome app also checks it. Finally, a small user interface icon next to an address can be clicked on to open a popup with the signed address text, allowing this signed address to be verified by other apps besides the chrome app (for instance, verifiable by the person sending me funds).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant