I'd take a look at this thread:
https://bitcointalksearch.org/topic/bitcoind-for-php-25094
This fork makes it easier to poll/import transactions into your own DB and then do whatever you need with them rather than relying on bitcoind to keep accounts straight. I'm using it for my own purposes (though I'm not accessing it from PHP but Python; I still need to keep track of transactions in a RDBMS).
Topic: Scalability of BitCoinD for a wallet service - page 2. (Read 2846 times)
Can I ask why you don't want to use your own code to manage balances and transactions? It seems to me that you need to do those things anyway, at least in most scenarios that I'm familiar with.
Hi Gavin
Thank you for taking the time to reply
Any suggestions as to how one should go about this then for high volume transactions? I've looked at the previous posts and wiki entries, most of these points towards using the "Accounts" feature. If the transactions were recorded to an external database, the biggest issue i see with this is polling the addresses when a payment is expected and also dealing with redundant payments.
Thanks
-MT
Thank you for taking the time to reply
Any suggestions as to how one should go about this then for high volume transactions? I've looked at the previous posts and wiki entries, most of these points towards using the "Accounts" feature. If the transactions were recorded to an external database, the biggest issue i see with this is polling the addresses when a payment is expected and also dealing with redundant payments.
Thanks
-MT
Are there any hard limits of to how far the daemon can scale or is this limited by the underlying hardware?
No hard limits, but the bitcoind "accounts" code hasn't been optimized for that. For example, computing an account's balance loops through all transactions in the wallet, so will take an increasing amount of time the more transactions you have in the wallet.
Hi
I am builing a free wallet service (like instawallet) and would like to know what are your thoughts on solely relying on the bitcoind daemon for storing all transactions as opposed to storing them in an external database for lookups. I have concerns that if we were to run into hundreds of users and transactions that bitcoind would not be able to handle such volumes concurrently.
Are there any hard limits of to how far the daemon can scale or is this limited by the underlying hardware?
Thanks
I am builing a free wallet service (like instawallet) and would like to know what are your thoughts on solely relying on the bitcoind daemon for storing all transactions as opposed to storing them in an external database for lookups. I have concerns that if we were to run into hundreds of users and transactions that bitcoind would not be able to handle such volumes concurrently.
Are there any hard limits of to how far the daemon can scale or is this limited by the underlying hardware?
Thanks
Jump to: