<p>Several options:</p>

<ul>
<li>Don't use bitcoind</li>
<li>Use bitcoind to interface the p2p network but ignore accounts and other abstractions</li>
<li>Hack bitcoind to use by-account indices</li>
</ul>

CC BY-SA 3.0
2014-01-14T18:00:43.690Z
2014-01-14T18:00:43.690Z
kaoD
<p>It is said in the <a href="https://en.bitcoin.it/wiki/Accounts_explained" rel="nofollow">bitcoin wiki</a> that:</p>

<blockquote>
  <p>The accounts code does not scale up to thousands of accounts with tens of thousands of transactions, because by-account (and by-account-by-time) indices are not implemented.
  So many operations (like computing an account balance) require accessing every wallet transaction.</p>
</blockquote>

<p>so my question is, what solution would be acceptable to implement a program who would be in charge of thousands of account (like an e-wallet).</p>

<p>My first guess would be to run multiple bitcoind instances, in order to keep the account by daemon ratio under a certain limit.</p>

<p>Any other idea ?</p>

CC BY-SA 3.0
2014-01-14T19:15:40.920Z
Don't use accounts and use database rows instead?
John T
<bitcoind><json-rpc><e-wallet><bitcoin-core-accounts><scalability>
Howto scale thousands of bitcoin accounts properly with bitcoind deamon?
Nihau
# Howto scale thousands of bitcoin accounts properly with bitcoind deamon?

(Asked by: username_0 on 2014-01-14)

It is said in the [bitcoin wiki](https://en.bitcoin.it/wiki/Accounts_explained) that:

> The accounts code does not scale up to thousands of accounts with tens of thousands of transactions, because by-account (and by-account-by-time) indices are not implemented.
> So many operations (like computing an account balance) require accessing every wallet transaction.

so my question is, what solution would be acceptable to implement a program who would be in charge of thousands of account (like an e-wallet).

My first guess would be to run multiple bitcoind instances, in order to keep the account by daemon ratio under a certain limit.

Any other idea ?

**Tags:** bitcoind, json-rpc, e-wallet, bitcoin-core-accounts, scalability

> **Comments:**
> **username_1**: Don't use accounts and use database rows instead?  

---

## 1 answers

### Answer by username_2 on 2014-01-14. Score: 1

Several options:

* Don't use bitcoind
* Use bitcoind to interface the p2p network but ignore accounts and other abstractions
* Hack bitcoind to use by-account indices


---

