Topic: Multiple instance of bitcoin with the same wallet (Read 15547 times)

It works ok for a while until the number of transactions exceeds the original pre generated addresses of the wallet.dat.  After that the new addresses bitcoin creates for sending change to or whatever are different for each wallet.dat.  I suppose you could get around that by generating 100000 addresses or something before you cloned the wallet.

Is there any updates to this? Anyone see what happens when using ballet on two PC's?

if you switch to another pc do you just need to copy wallet.dat and then copy back over to the old pc to switch back?

Plenty of up-to-date and accurate information in this thread

this is going to be perfectly fine, it's like using 2 credit cards with one shared credit account.

You are quoting me but my subject was unrelated to the FAQ as the FAQ talks about the same wallet on different machines while I am talking about mining to a different wallet than the one on the machine.

Having forks of a wallet is still a problem and most likely will stay a problem with many ways to loose your money. Don't do it. In doubt, generate a new wallet and transfer all coins to it. If an old backup was compromised it is not enough to generate a new address and send all coins there. Just generate a new wallet and stop using the old empty one.

Concerning my question above, sure if my mining machine was compromised, it might already be mining to a different wallet, so now I think having a feature to mine to a different wallet does not add security but even be bad for security as finding blocks for others might go unnoticed.

Is this still considered to be a bad practice / untested?

If it is not, please update the information on this answer.

Yes, please please please do this. It would be much saver having a miner mine to an air gapped wallet than being forced to mine to an online wallet.
My rigs are in a server room and I would feel saver if I could run them without a wallet worth 1000$ at a time on it each time it hits a block.

+1

Better would be a new feature that tells the mining bitcoin "please credit generated bitcoins to THIS address (instead of a new one)."

If you are just mining, you don't need the private key at all, the bitcoin address (or public key) is enough to create the coin generation transaction.

The bitcoin infrastructure doesn't care if you run with multiple instances of the same wallet.  The wallet only contains the private keys you use to spend your coins; the coins themselves exist in the block chain.  In other words, your wallet contains permission to spend your money, and not the money itself.  (Like your physical wallet might contain a debit card, which isn't money itself, but authorizes you to spend money stored somewhere else.)

The problem is that as you spend money out of each wallet, new keys are generated to receive some of the left-over coins.  The other wallets won't have these new keys.  This will cause the balances of each wallet to eventually diverge (after roughly 100 transactions that you send), resulting in coins that you can only spend from a particular wallet.

This will be confusing, since the number of coins you have won't simply be the sum of the balances in all of your wallets.  For example, if wallet A has a balance of 500, and B has a balance of 500, you might only have 700 and not 1000.  (Wallet A and B both have access to the same 300 coins, but they also each have access to 200 coins that the other doesn't have the keys for.  So 300 + 200 + 200 = 700.)

You could always use mybitcoin.com to do this.  The only other option would be to periodically merge all your wallets together so that they all have the same key set and then rescan the block chain.  But no software currently exists to merge wallets.

Hi all thanks for the replies, from what was mentioned I gathered that the bitcoin infrastructure doesn't allow multiple bitcoin clients to connect using the same wallet as there is no central server to synchronize the multiple instances of the same bitcoin wallet.

Initially I was hoping to get similar functionality as let say gmail where emails received while logged into a computer browser would also be updated in the gmail instance running on the phone. This would allow multiple inputs and at the same time remained synchronize among all instances.

Would it work if you used only two copies, one that always only mined, not spending the money, and keeping the same address, and another that has that address, that you use to spend and receive money as usual? Besides the lag 'til mining earnings show up on your spending wallet, is there gonna be any issue?

Maybe I'm missing something here.  Why would the mining rig (which isn't logged into very often) need to know how many bitcoins are in the wallet?  It just makes more.  It doesn't spend any.  Only the workstation where the spending occurs really needs to know how many bitcoins there are.  OH WAIT!  *facepalm*  I GET IT!  You're mining solo.  Otherwise, in a pool, this would make no sense.  In that case, automated transfers from the mining wallet to the spending wallet would publicly show a relationship between the two wallets, but it would be simple to set up.  As an aside, sshd is only a small inconvenience.

Cloning your wallet to do anything besides backing it up is a bad idea.

It might work perfectly for a while... but you are very likely to get weird behavior from bitcoin sooner or later, because doing that is not tested or supported.

Where 'weird behavior' is one clone of the wallet shows one balance, the other clone shows another, and you might end up with bitcoins that you can spend from one wallet but not the other (or, worst case, end up with bitcoins that neither wallet is able to spend).

If you REALLY REALLY REALLY want to do this... then get the latest code from git, pull sipa's 'Spent per txout' patch, and then spend a bunch of time testing to find out what happens when your cloned wallets eventually start using different keys from the keypool.

Sure, I get that, and the coins also lose their freshly minted, unspent shininess and it's a pain waiting for the sent coins to be confirmed. It seems like it's the best (only?) option for kindle, though.

I have thought about the same concept and how to implement but I don't understand the bitcoin wallet storage/protocol enough yet to offer a solution.

My thoughts about how to implement at the moment involve utilizing an alternate DB for the wallet, one of which can be R/W from multiple clients and/or locations and supporting reasonable row/field/etc locking as needed. As I understand from a few forum posts the Berkeley DB used currently opens an exclusive file lock (?) to the wallet DB preventing another process from access. I have not looked into the source as of yet, just been thinking about how to implement such for an alternate project unrelated to the OP question.

If I am heading down the wrong path could someone correct me?

True. My thinking was to protect the wallet, rather than have it on a machine exposed to the 'net, but...

...if the machine is only opening a limited number of trusted ports (8332 and SSH) then I guess the risk is minimal.

OK, the part I was missing was people switch off their machines :-)

Could you have the mining rig automatically send bitcoins to another wallet? Then when your workstation was brought online you'd have access to the sent coins.

Hi LMGTFY thanks for the suggestion, in this situation the workstation has to be on for the entire duration for the mining rig to work. If I were to run the server on the rig itself, it would be self sustainable. In this case if I were to transfer btc using the mining rig wallet, I would have to remote access into the rig and transfer within the bitcoin interface of the mining rig. If it is possible, running another instant of the wallet in a separate work station would allow me to transfer btc without logging into the rig.

I think we get the first part, it's the use case in the second part I'm not sure about.

In my proposal (which may not satisfy your use case) you have a workstation running "bitcoin -server". You use it to send and receive bitcoins, monitor transactions, etc. You also have a separate mining rig which connects to the workstation. Your wallet only needs to be on one machine (the workstation).

I suspect there's some subtlety I'm not getting, which necessitates cloning the wallet...

Oh let me illustrate, for example I kinda want to use bitcoin in a way where anything and everything is sync btw the same wallet.

So if I am mining on one pc with wallet A, I can log in to another pc and with another instance of wallet A. This will allow me to monitor transactions and at the same time transfer the coins on a normal pc without accessing the mining rig.