Title: Technical handle 25000 address Post by: noreplybatam on September 14, 2017, 06:40:34 PM Hi ..
i try want to build website with API service provider like Quote block.io so i compile bitcoin-cli daemon in 1 vps. and created 1 vps more for backend using phpand i connected with Quote EasyBitcoin .now i have a 25k address in my bitcoin wallet.dat . and now i feel the proccess is slow . what the best technical for this case ?? any help ??? Title: Re: Technical handle 25000 address Post by: noreplybatam on September 15, 2017, 06:36:21 AM up
Title: Re: Technical handle 25000 address Post by: CarlOrff on September 15, 2017, 05:56:05 PM Hi .. OK...i try want to build website with API service provider like Quote block.io so i compile bitcoin-cli daemon in 1 vps. and created 1 vps more for backend using phpand i connected with Quote EasyBitcoin .now i have a 25k address in my bitcoin wallet.dat . and now i feel the proccess is slow . what the best technical for this case ?? any help ??? All these words, but what is your question ? Are you sure you have 25k adresses in your wallet.dat ? Have a look at the github sources documentation about the eventual wallet.dat limitations. If this not a limitation, take care about the validity of all these addresses. Title: Re: Technical handle 25000 address Post by: noreplybatam on September 15, 2017, 06:06:30 PM Hi .. OK...i try want to build website with API service provider like Quote block.io so i compile bitcoin-cli daemon in 1 vps. and created 1 vps more for backend using phpand i connected with Quote EasyBitcoin .now i have a 25k address in my bitcoin wallet.dat . and now i feel the proccess is slow . what the best technical for this case ?? any help ??? All these words, but what is your question ? Are you sure you have 25k adresses in your wallet.dat ? Have a look at the github sources documentation about the eventual wallet.dat limitations. If this not a limitation, take care about the validity of all these addresses. yes, now i have 30k addresses in my daemon cli . my question is what is the best solution for handle much addresses in wallet . must be more setup server ?? or what the other solutions ?? thanks Title: Re: Technical handle 25000 address Post by: noreplybatam on September 16, 2017, 01:33:15 PM up
Title: Re: Technical handle 25000 address Post by: cr1776 on September 16, 2017, 04:13:21 PM Hi .. OK...i try want to build website with API service provider like Quote block.io so i compile bitcoin-cli daemon in 1 vps. and created 1 vps more for backend using phpand i connected with Quote EasyBitcoin .now i have a 25k address in my bitcoin wallet.dat . and now i feel the proccess is slow . what the best technical for this case ?? any help ??? All these words, but what is your question ? Are you sure you have 25k adresses in your wallet.dat ? Have a look at the github sources documentation about the eventual wallet.dat limitations. If this not a limitation, take care about the validity of all these addresses. yes, now i have 30k addresses in my daemon cli . my question is what is the best solution for handle much addresses in wallet . must be more setup server ?? or what the other solutions ?? thanks Create a database and manage it yourself is probably the best solution Title: Re: Technical handle 25000 address Post by: noreplybatam on September 16, 2017, 04:44:44 PM Hi .. OK...i try want to build website with API service provider like Quote block.io so i compile bitcoin-cli daemon in 1 vps. and created 1 vps more for backend using phpand i connected with Quote EasyBitcoin .now i have a 25k address in my bitcoin wallet.dat . and now i feel the proccess is slow . what the best technical for this case ?? any help ??? All these words, but what is your question ? Are you sure you have 25k adresses in your wallet.dat ? Have a look at the github sources documentation about the eventual wallet.dat limitations. If this not a limitation, take care about the validity of all these addresses. yes, now i have 30k addresses in my daemon cli . my question is what is the best solution for handle much addresses in wallet . must be more setup server ?? or what the other solutions ?? thanks Create a database and manage it yourself is probably the best solution what about transaction ?? what the logic Title: Re: Technical handle 25000 address Post by: maeusi on September 16, 2017, 06:56:13 PM I would transfer my funds to another wallet instead of handling 30000+ addresses. How did that happen? Did you get 30000 payments?
Title: Re: Technical handle 25000 address Post by: noreplybatam on September 16, 2017, 07:02:27 PM I would transfer my funds to another wallet instead of handling 30000+ addresses. How did that happen? Did you get 30000 payments? yes now is like that im used method Title: Re: Technical handle 25000 address Post by: noreplybatam on September 17, 2017, 04:06:42 PM up
Title: Re: Technical handle 25000 address Post by: jackg on September 18, 2017, 07:01:04 PM Do you need the 25000 addresses or can you send all of the coins to one address?
What is the exact problem here? Can you not just keep making a new wallet, say, add to your script to send the coins to a wallet in another vps/your pc or a cold wallet to empty those addresses and recreate you a new wallet.dat. Storing the old wallet.dat in a different folder under the current date. You only need about a 5sats/byte fee in order to get a confirmation within a few days (I've done it quite a bit with that size fee). Title: Re: Technical handle 25000 address Post by: noreplybatam on September 18, 2017, 11:39:58 PM Do you need the 25000 addresses or can you send all of the coins to one address? What is the exact problem here? Can you not just keep making a new wallet, say, add to your script to send the coins to a wallet in another vps/your pc or a cold wallet to empty those addresses and recreate you a new wallet.dat. Storing the old wallet.dat in a different folder under the current date. You only need about a 5sats/byte fee in order to get a confirmation within a few days (I've done it quite a bit with that size fee). the problem is, i store 30k address now in 1 wallet.dat and 1k transaction /day . and now i see my daemon is broken for showing info - slowly getinfo cli - slowly getbalance cli - slowly using sendfrom cli (sometimes transaction reject) Title: Re: Technical handle 25000 address Post by: noreplybatam on September 18, 2017, 11:44:03 PM Do you need the 25000 addresses or can you send all of the coins to one address? What is the exact problem here? Can you not just keep making a new wallet, say, add to your script to send the coins to a wallet in another vps/your pc or a cold wallet to empty those addresses and recreate you a new wallet.dat. Storing the old wallet.dat in a different folder under the current date. You only need about a 5sats/byte fee in order to get a confirmation within a few days (I've done it quite a bit with that size fee). and i want to know how blockchain.info handle all member wallet, what type server they using or how many server they using Title: Re: Technical handle 25000 address Post by: cr1776 on September 19, 2017, 12:52:05 AM Do you need the 25000 addresses or can you send all of the coins to one address? What is the exact problem here? Can you not just keep making a new wallet, say, add to your script to send the coins to a wallet in another vps/your pc or a cold wallet to empty those addresses and recreate you a new wallet.dat. Storing the old wallet.dat in a different folder under the current date. You only need about a 5sats/byte fee in order to get a confirmation within a few days (I've done it quite a bit with that size fee). and i want to know how blockchain.info handle all member wallet, what type server they using or how many server they using Like I said above, the reports say they have a database and manage the wallet themselves. They don't use the wallet functionality of Core. You might look at this if you wish to see something similar: https://wildbunny.co.uk/blog/2014/03/18/watch_only_wallet/ This is for watching only, but the same logic would apply. It is a few years old, but could be useful. |