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

Delete receiving addresses? #27

Closed
voidzero opened this issue Nov 23, 2012 · 4 comments
Closed

Delete receiving addresses? #27

voidzero opened this issue Nov 23, 2012 · 4 comments

Comments

@voidzero
Copy link

I'll admit i'm new to using Bitcoin Armory, even to bitcoin as a whole. I noticed that a new address is added into my wallet each time I press "Receive Bitcoins". I didn't know where else to ask this -- can those "secondary" addresses be deleted; can they be re-used and do I just suck at finding a page that describes this?

Thanks

@etotheipi
Copy link
Owner

Because Armory uses "deterministic wallets", those addresses are part of the address chain, and must be generated in order to get to the next one. Those addresses cannot be deleted. However, in the updated version I'm going to release shortly, there is a button for hiding unused addresses, so that will hide all those receiving addresses that never actually received anything.

Bitcoin addresses are usually only used once. There's no security problems re-using addresses, but re-using addresses links together all transactions made using that address (it's a privacy issue, not a security issue). It's not a big deal for most users, but it's also unnecessary since Armory can produce an infinite number of addresses -- you might as well just use a new one every time (unless you have a public donation address, etc, in which case it will get reused)

Also, right after I make this release (0.85-beta), I will be updating the documentation part of the website. I will try to answer a large variety of questions like this one. It's not finished, but you can read the start of my FAQ at:

http://bitcoinarmory.com/index.php/frequently-asked-questions

@voidzero
Copy link
Author

On 23-11-12 17:11, etotheipi wrote:

(..snip..)

Also, right after I make this release (0.85-beta), I will be updating
the documentation part of the website. I will try to answer a large
variety of questions like this one. It's not finished, but you can read
the start of my FAQ at:

http://bitcoinarmory.com/index.php/frequently-asked-questions

Thanks a lot for your answers. I've just started to learn more about the
offline wallet using an old netbook I didn't use anymore. I'm sure this
will help me grasp the ins and outs. The FAQ will also be helpful,
thanks again :)

Mark

@voidzero
Copy link
Author

Me again,

Over the last few days I learned more about the offline wallet and I'd like to run some of my assumptions by you. Perhaps they can be valuable additions to the FAQ, too.

So, my online Armory now has both an online wallet for itself, and the offline PC's wallet as watch-only. On the online PC I can see the balance of both wallets.

  • I don't see the current balance on my offline PC. Is this correct at all times or is it possible to see the current balance on the offline PC?
  • If it's not 'logical' to see the current balance on the offline account, then am I right in assuming that the offline PC is only used to sign the outgoing transactions from the wallet?
  • Doesn't the offline wallet need to confirm it actually received the transfer?

Cheers, Mark

@etotheipi
Copy link
Owner

Hi Mark,

I assume you saw the page: http://bitcoinarmory.com/index.php/using-offline-wallets-in-armory ?

I need to reduce that page to about half the words, but it does explain the background of offline wallets pretty thoroughly.

The answer to your question is this: your offline computer does not hold the blockchain, and thus does not know anything about any of the addresses in the wallet. There's no way for it to know the balances of any addresses, or how to create transactions.

However, the wallet does recognize its own transactions, and is able to sign those transactions. And because of the way the data structured, the offline wallet is capable of knowing/verifying for sure what it is signing. (it can't be tricked into signing one thing, but making the user believe it's signing something else)

For this reason, you only need to use the offline computer when you are send bitcoins. And only for signing the final transaction. All other operations are done on the online computer -- creating receiving addresses, reviewing balances, verifying payments, etc. Personally, my offline computer is off most of the month, turned on only when I need to refill one of my "hot wallets" from my offline wallet.

TierNolan pushed a commit to TierNolan/BitcoinArmory that referenced this issue Nov 23, 2018
af2da22 Add new tests for invalid Bech32 strings (Clark Moody)

Pull request description:

  Similar updates in the vein of etotheipi#27, etotheipi#29, etotheipi#30, etotheipi#31, etotheipi#32

  Adds invalid Bech32 string test cases.

  Please note: Rust strings are UTF-8, so that the character literal `0xff` [turns into](https://codepoints.net/U+00FF) `0xc3bf` when accessed with the `bytes` function.

Tree-SHA512: 73f85762fc22059acb9c4b382068997fb0341354f1de26ecb2d75ba3c57aee80609fd2839967541c9a9f96ccdc04137140174396f5acfe62a6511fd9f18e703e
TierNolan pushed a commit to TierNolan/BitcoinArmory that referenced this issue Nov 23, 2018
15380f4 Add Python tests (Pieter Wuille)

Pull request description:

Tree-SHA512: fb3c4c441d4ef0b9669d50c408f2a6d0387771477fc49f2574ebbb217b86b4e80ae2a064bcd2a1b70e43cbf8f68ea5474aac506da8c133b343268672c53cf1c6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants