Best way to handle multiple accounts (like a bank)?

[wslh]

I am developing a virtual bank using bitcoins using the reference client multiple accounts capability. My main concern is scaling it to hundreds of thousands of accounts and transactions fired all the time.

What are other alternatives to this approach? I read that using multiple address assigned to different users is one way to handle it but would like to hear your opinion about other alternatives.

Thanks,
wslh

[doge94]

If you don't know what you are doing PLEASE don't develop banking software, especially for bitcoin. That being said assigning each user an address in a DB and checking transactions as they come in seems to be a good approach.

[gmaxwell]

If you don't know what you are doing

To make this solid advice more useful, I'll add... How do you know when you don't know what you're doing?  If you think you know what you're doing thats a strong indicator that you don't.

[cbeast]

One word: Ripple.
It claims to do everything you could ever dream of.

[doof]

If you don't know what you are doing

To make this solid advice more useful, I'll add... How do you know when you don't know what you're doing?  If you think you know what you're doing thats a strong indicator that you don't.

I lol'd!

[doof]

What are other alternatives to this approach? I read that using multiple address assigned to different users is one way to handle it but would like to hear your opinion about other alternatives.

MS SQL Enterprise will handle alot of load.

[BitcoinPappi]

If you don't know what you are doing

To make this solid advice more useful, I'll add... How do you know when you don't know what you're doing?  If you think you know what you're doing thats a strong indicator that you don't.

^^^This

[newIndia]

What are other alternatives to this approach? I read that using multiple address assigned to different users is one way to handle it but would like to hear your opinion about other alternatives.

MS SQL Enterprise will handle alot of load.

For god's sake, DO NOT get trapped by MS. Once you are in, there is no way out.

[dsly]

I am developing a virtual bank using bitcoins using the reference client multiple accounts capability. My main concern is scaling it to hundreds of thousands of accounts and transactions fired all the time.

What are other alternatives to this approach? I read that using multiple address assigned to different users is one way to handle it but would like to hear your opinion about other alternatives.

Thanks,
wslh

Maybe if bitcoin had a POS , it would also be like a bank. But, I seriously doubt, a virtual bank for bitcoins would be preferred by most.

[altcoinex]

"Don't you think If I were wrong, Id know it?"

[throwingbones1]

What are other alternatives to this approach? I read that using multiple address assigned to different users is one way to handle it but would like to hear your opinion about other alternatives.

MS SQL Enterprise will handle alot of load.

For god's sake, DO NOT get trapped by MS. Once you are in, there is no way out.

i agree totally, there are plenty of other alternatives.

[mlferro]

the topic idea is good! I liked ... but I do not particularly have the courage to invest, because nowadays, there is no security on the Internet

[wslh]

If you don't know what you are doing

To make this solid advice more useful, I'll add... How do you know when you don't know what you're doing?  If you think you know what you're doing thats a strong indicator that you don't.

I always have someone in my team that knows what he is doing. Anyway, the main question was about a bitcoin implementation that can handle multiple accounts.

I wonder why nobody suggested Copay, BitcoinJS-Lib, or a fork of BTCWallet handling multiple accounts.

[BITMIXER.IO]

In case of "bank" no way than use unique address for every customer. Combined with no-sql-database it should work pretty fast.

[noobtrader]

One word: Ripple.
It claims to do everything you could ever dream of.

wow... it can take me to the moon LOL

[lontivero]

In case of "bank" no way than use unique address for every customer. Combined with no-sql-database it should work pretty fast.

I think that is the more natural approach but it is not a good idea.
1) reuse addresses is never a good idea
2) all eggs together sound dangerous if they are in a reused address

It could be an acceptable approach if he can move the biggest part to a cold wallet

[wslh]

I just published a way to do this using Copay.

I hope it helps.

[daviswilla]

I dont it work

[nambich]

I am developing a virtual bank using bitcoins using the reference client multiple accounts capability. My main concern is scaling it to hundreds of thousands of accounts and transactions fired all the time.

What are other alternatives to this approach? I read that using multiple address assigned to different users is one way to handle it but would like to hear your opinion about other alternatives.

Thanks,
wslh

The topic idea is good! I liked ... but I do not particularly have the courage to invest,

because nowadays, there is no security on the Internet