Topic: Is it a bad idea to have a wallet with 10s of thousands of addresses? (Read 2909 times)
September 27, 2014, 09:08:16 AM
I find the wallet.dat grows very quickly when you have a website generating unique addresses for each order. Then basic functions, like -rescan, start to take a CRAZY HUGE amount of time. Bitcoin really isn't scalable at all
September 27, 2014, 05:09:30 AM
My wallet.dat file is 2.7mb no clue how many new addresses i have in it but it takes a lota time to start
even when it says verifying blocks and loading wallet file takes like 2-3 minutes in it.
So i say probably not the best idea but if you are having no issues in loading and whatnot sure wth.
even when it says verifying blocks and loading wallet file takes like 2-3 minutes in it.
So i say probably not the best idea but if you are having no issues in loading and whatnot sure wth.
September 25, 2014, 12:03:44 PM
Althoug you can have unlimited address, in my opinion it's not a good idea.
I think it is useless have so many address.
I think it is useless have so many address.
September 25, 2014, 10:05:32 AM
what do you mean by active addresses and why it becomes slow?
active address i mean if the address is not empty.
bitcoind is pain in the ass in large scale
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
September 24, 2014, 04:30:46 AM
Are there known cases of people having problems just because of the sheer number of addresses they've generated in their bitcoind wallets?
Any info on actual limits?
Any info on actual limits?
the question is, is it really necessary?
Some persons don't reuse addresses though they might not delete it from the wallet, so if they somehow get any BTC into the old address they can still get it. If the wallet is too old, then it may contain too much addresses. OR if you do something related to company and all, you may have these much addresses. Anyway, that's not the point here.
I didn't hard any limits, yet. I think there is no limit. But if you generate too much addresses in your wallet, it may become slow unless your GHz increases.
~~MZ~~
September 24, 2014, 04:12:30 AM
Are there known cases of people having problems just because of the sheer number of addresses they've generated in their bitcoind wallets?
Any info on actual limits?
Any info on actual limits?
the question is, is it really necessary?
September 22, 2014, 08:07:24 AM
transfering out btc become very very slow (5-20 seconds per tx) when you have >20k active addresses.
I dont think so.
Any decent proof for this ?
September 20, 2014, 08:02:59 PM
transfering out btc become very very slow (5-20 seconds per tx) when you have >20k active addresses.
September 19, 2014, 11:21:09 PM
wallet can have loads of adresses - just look at exchanges
September 19, 2014, 01:09:23 AM
probably fine, it becomes an issue based on the number of transactions per address. I have an old phone with bitcoinj on it (shildenbach's wallet) It was getting ridiculous using the same address for mining payouts so I had to export it to another wallet to deal with it and changed addresses to deal with it (when selling coin in person).
September 18, 2014, 10:27:19 PM
exchanges have 10ks of adresses and work fine
September 18, 2014, 05:17:33 AM
Well rescan is not really a concern here, since we are talking about bitcoind node that's up 24/7 on a dedicated server.
I'm more concerned if it would make using the wallet slower for the front end app or cause other problems.
I'm more concerned if it would make using the wallet slower for the front end app or cause other problems.
That doesn't matter because Armory takes the blockchain data and reprocesses it into the Armory database and that is what takes long. Rescan means Armory is scanning that data for transactions associated with the addresses in the wallet.
Check OP twice, please.
Either way, "dude," scanning and keeping the node updated are 2 different things.
Well nobody is talking about scanning either. You high bro?
I think that's a woman you are talking to. No really.
Anyway, on topic, I did hear about btc-e facing problems because they had 100s of thousands of addresses to track. Most exchanges use custom software because of this sort of thing.
September 18, 2014, 05:01:42 AM
You may have unlimited of bitcoin address on your server
September 18, 2014, 04:58:32 AM
Generating and dealing with tens of thousands of addresses shouldn't cause a problem with bitcoind on a dedicated server, no. Once you hit "millions" and beyond, you might see some slowdown in performance -- this is why you'll see exchanges occasionally moving to new wallets because of bloat.
September 16, 2014, 07:09:38 AM
Well rescan is not really a concern here, since we are talking about bitcoind node that's up 24/7 on a dedicated server.
I'm more concerned if it would make using the wallet slower for the front end app or cause other problems.
I'm more concerned if it would make using the wallet slower for the front end app or cause other problems.
That doesn't matter because Armory takes the blockchain data and reprocesses it into the Armory database and that is what takes long. Rescan means Armory is scanning that data for transactions associated with the addresses in the wallet.
Check OP twice, please.
Either way, "dude," scanning and keeping the node updated are 2 different things.
September 16, 2014, 06:50:19 AM
Well rescan is not really a concern here, since we are talking about bitcoind node that's up 24/7 on a dedicated server.
I'm more concerned if it would make using the wallet slower for the front end app or cause other problems.
I'm more concerned if it would make using the wallet slower for the front end app or cause other problems.
That doesn't matter because Armory takes the blockchain data and reprocesses it into the Armory database and that is what takes long. Rescan means Armory is scanning that data for transactions associated with the addresses in the wallet.
September 16, 2014, 04:17:14 AM
Well rescan is not really a concern here, since we are talking about bitcoind node that's up 24/7 on a dedicated server.
I'm more concerned if it would make using the wallet slower for the front end app or cause other problems.
I'm more concerned if it would make using the wallet slower for the front end app or cause other problems.
September 14, 2014, 09:48:21 AM
Awhile back I imported the private key for "correct horse battery staple" and it had so many transactions it kept crashing Armory when I tried to scan the blockchain. Armory has since updated their wallet but I had already removed the address due to the time it took to open the wallet. That is number of transactions rather than addresses but I expect the same thing would happen.
September 08, 2014, 12:27:17 PM
If you have 1 address and do a rescan it will take X time...
if you hve 50X addresses and do a rescsan it can take 50X time, kinda.
Well I don't think its exactly like that, but along those lines...
I don't have the best laptop... no SSD etc... and a rescan for 1 addy tpok 20 mins recently for me.
then another wallet with 7 addresses took 55 minutes... so ts like not it took X * 20 = total time... X being addresses, 20 minutes being the average scam time... but for me it did make a large difference... but not cant 7x longer.
Why not sending all your coins into a single fresh new wallet if you are concerned?
if you hve 50X addresses and do a rescsan it can take 50X time, kinda.
Well I don't think its exactly like that, but along those lines...
I don't have the best laptop... no SSD etc... and a rescan for 1 addy tpok 20 mins recently for me.
then another wallet with 7 addresses took 55 minutes... so ts like not it took X * 20 = total time... X being addresses, 20 minutes being the average scam time... but for me it did make a large difference... but not cant 7x longer.
Why not sending all your coins into a single fresh new wallet if you are concerned?
September 07, 2014, 01:01:23 AM
That's good to know.
Should we expect performance issues though? For example the wallet grows to 90mb in just few months, and it's being encrypted and decrypted all the time.
Should we expect performance issues though? For example the wallet grows to 90mb in just few months, and it's being encrypted and decrypted all the time.
It may take a bit longer to Decrypt and encrypt.
September 06, 2014, 03:54:51 AM
That's good to know.
Should we expect performance issues though? For example the wallet grows to 90mb in just few months, and it's being encrypted and decrypted all the time.
Should we expect performance issues though? For example the wallet grows to 90mb in just few months, and it's being encrypted and decrypted all the time.
September 05, 2014, 11:06:19 PM
I don't think there are any limits, and I don't think it would crash it, if you're afraid it will however, just avoid it.
It's not worth trying it to find out, and maybe causing trouble with your wallet.
It's not worth trying it to find out, and maybe causing trouble with your wallet.
September 05, 2014, 06:50:06 AM
Are there known cases of people having problems just because of the sheer number of addresses they've generated in their bitcoind wallets?
Any info on actual limits?
Any info on actual limits?
Jump to: