Topic:   (Read 2170 times)
I would never delete any private key of any address that I handed to a customer (or anyone really). Just in case someone discovers it one year later and make a payment. E.g. repeated customer who lost his current payment address but somehow has saved the address from his last years' transaction.
But this is an interesting topic of bitcoind performance. Have you heard of any bitcoind problems related to too big wallet? At what size they might start happening? If they're not happening, how big wallets have you seen that were running smoothly? Was it hundreds of thousands addresses? Millions? Dozens of millions?
Do sites like MtGox, which are handling (or are prepared to handle) hundreds of thousands user accounts, have their bitcoin deposit/withdraw features built on top of bitcoind wallet? Or rather they create and manage addresses in other way and use bitcoind only to sign raw transactions (and as block explorer API, but they parse incoming transactions and manage keys and unspent outputs in their own software)? What's the practice in here? Is bitcoind suited for and working well with such a large scale?
But this is an interesting topic of bitcoind performance. Have you heard of any bitcoind problems related to too big wallet? At what size they might start happening? If they're not happening, how big wallets have you seen that were running smoothly? Was it hundreds of thousands addresses? Millions? Dozens of millions?
Do sites like MtGox, which are handling (or are prepared to handle) hundreds of thousands user accounts, have their bitcoin deposit/withdraw features built on top of bitcoind wallet? Or rather they create and manage addresses in other way and use bitcoind only to sign raw transactions (and as block explorer API, but they parse incoming transactions and manage keys and unspent outputs in their own software)? What's the practice in here? Is bitcoind suited for and working well with such a large scale?
I plan on using an individual BTC address per order... but my question is that if I create a new address in bitcoind, and say give the customer 24 hours to pay for this order.... is it possible for me to then delete / archive this address if the customer never pays?
I'm just thinking over time, there could build up a massive amount of addresses ... which will never be used..etc is this even an issue ?
Addresses are cheap in every way imaginable. That is why it is recommended to generate a new one for every single transaction. So don't worry about it.
FYI if you deleted the private key associated with the address you might save a few bytes of disk space but would loose any coins sent to the address. So don't do it.
hmmm, You mean create key for user receive payment, transfer payment or let them sweep the key then destroy it. Or user has account which is a gpg key/encrypted seed key or something similar uses it to create a address which they receive payment then transfer sweep then archive it for them? and they can recover it by using the key made it with?
If it is something similar, interesting idea, could be used for anonymous payments maybe if it was sitting on tor, or semi anon if not.
If it is something similar, interesting idea, could be used for anonymous payments maybe if it was sitting on tor, or semi anon if not.
The above post is right on the BTC 
If someone pays you late or accidently to a old address and you have deleted it no getting it back. Unless you use a deterministic wallet ? Like Armory?
You could always just archive them by dumping the addresses out and putting them into a encrypted file, with a identifier for each one so you know which customer its linked to.
If someone pays you late or accidently to a old address and you have deleted it no getting it back. Unless you use a deterministic wallet ? Like Armory?You could always just archive them by dumping the addresses out and putting them into a encrypted file, with a identifier for each one so you know which customer its linked to.
5. Import priv keys of relevant addressess to new wallet.
Just make sure when doing this one to use the new argument to prevent a complete rescan from happening with each address (i.e. just do the rescan once at the end).
I think you can "vacuum" the wallet once in a while:
1. Create brand new wallet with new address.
2. Transfer all funds from old wallet to new address.
3. Export relevant private keys of addressees you need active in new wallet.
4. Archive rest of the addressess.
5. Import priv keys of relevant addressess to new wallet.
Bticoin gurus: correct me if I'm wrong.
1. Create brand new wallet with new address.
2. Transfer all funds from old wallet to new address.
3. Export relevant private keys of addressees you need active in new wallet.
4. Archive rest of the addressess.
5. Import priv keys of relevant addressess to new wallet.
Bticoin gurus: correct me if I'm wrong.
One drawback with creating more and more addresses is the size of your wallet.dat file (which is probably not much of a concern in reality) - the other one would be if there are any performance issues that will arise from a bigger and bigger wallet (due to a lack of indexing say).
I do recall reading a thread about the latter (with a huge wallet) so you might want to do a bit more research about that (it may be an old problem that was already solved).
I do recall reading a thread about the latter (with a huge wallet) so you might want to do a bit more research about that (it may be an old problem that was already solved).
Jump to: