Bitcoin Forum
April 27, 2017, 09:01:52 PM *
News: Latest stable version of Bitcoin Core: 0.14.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Regarding wallet sites  (Read 826 times)
bitcoinsarefun
Member
**
Offline Offline

Activity: 98



View Profile
February 28, 2012, 12:19:06 PM
 #1

This may be a silly question but I'm wondering, do wallet sites ( like instawallet )  use:

* a separate instance of the bitcoin for each user, giving them each a wallet.dat file

or

* have a few different bitcoin instances running and assign the users addresses from one of them? so funds are essentially intermingled with others.
1493326912
Hero Member
*
Offline Offline

Posts: 1493326912

View Profile Personal Message (Offline)

Ignore
1493326912
Reply with quote  #2

1493326912
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1493326912
Hero Member
*
Offline Offline

Posts: 1493326912

View Profile Personal Message (Offline)

Ignore
1493326912
Reply with quote  #2

1493326912
Report to moderator
Herodes
Hero Member
*****
Offline Offline

Activity: 868


View Profile
February 28, 2012, 01:24:30 PM
 #2

There's possible to run a bitcoind with funds assigned to accounts. So if you look at bitcoind as a bank, the accounts would be much like accounts in a normal bank. They can be numbered like 0,1,2,3 and so on.

So in a database, you could have user with UID (User Identificator) 123456 being associated with account 9 for instance, so if you log in as 'AvgJoe', the UID is fetched from the Users-db table and your account number is fetched from a database table as well. Thus the site could determine how much you have available in your account, and do any other action that's possible with your account.

Another thing is that a lot of sites don't have the bitcoind running at the same server as the webserver, and there are different methods to keep track of the balance a user has, and how bitcoins are received and sent.

The safest option would probably be to run the bitcoind on a different server, so even if the webserver was compromised, the attacker could not run away with the wallet right away.

Also some sites do offline storage of coins, so say the total available balance of an online webwallet provider was 200K BTC, perhaps they only kept 15K available to the system at any time.

You can read more about the API calls here: https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls_list

And no, it wasn't a silly question. The only way to learn more is to be curious and hungry for more knowledge. Unfortunately there's quite a few developers in this community that laugh at you if you have a level of expertise lower than theirs. I don't think this is something that's just in this community, but something that you you will find anywhere.

And as always, always try to find the answer to your questions by googling and searching this forum etc, and if you don't find the answer, don't be afraid to ask, even though it might be a 'stupid' question. At least, there's always someone wanting to help.

weex
Legendary
*
Offline Offline

Activity: 1099


Give me your tired, your poor, your huddled...


View Profile
March 03, 2012, 08:45:28 AM
 #3

For anything more than very low volume usage, you're much better off building your own accounting system in a database rather than use the built-in bitcoind accounts.

There's not really much need to run multiple instances of bitcoind unless you want a more comprehensive view of the Bitcoin network or want extra redundancy.

Keeping addresses/keys synced between multiple instances is an interesting problem to tackle but either way, you will want to store only what you need to on the most vulnerable servers. Thing is, the "only what you need to" part tends to scale linearly with total holdings whereas your profit may not.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!