Using multiple wallet files with bitcoind

ISibboI commented at 1:12 pm on October 19, 2013: none

It should be possible to make bitcoind use multiple different wallet files without having to restart, so that public and private eWallet services don’t have to put everything into one big bucket. Especially for private eWallets, that’d be useful, because you can easily seperate which coins belong to which person without having to use a DB or something like that.

laanwj commented at 2:28 pm on October 19, 2013: member

There are some pull requests that implemented multi-wallet support, but they never made it because more work is needed. If you (or someone else) feel like picking this up, see:

#2124 Dynamically Loadable Multiple Wallet Support Complete!!!
#2407 Added CWalletManager class to support loading of multiple wallets.

super3 commented at 6:30 pm on October 21, 2013: contributor

If you are looking for this functionality, Bitcoin Armory has already implemented multiple wallets.

o-jasper commented at 9:39 pm on February 18, 2014: none

I second bitcoind and bitcoin-qt should support this. While at it, I suggest creation a few random inaccessible ones, which can be replaced with accesible ones. For plausible deniability that those wallets are actual ones in case of threat. (edit: maybe passwords should automatically try all the coin, so people cant whine about forgetting which wallet had which password..)

int03h commented at 0:39 am on February 19, 2014: none

Bitcoin “the project” should be the blockchain. Wallets and all sorts of other stuff should be something else. I am fully aware that at the moment they are mashed together. They shouldn’t be. IMHO. –disable-wallet should be the default.

laanwj commented at 7:44 am on February 19, 2014: member

@o-jasper The reference client cannot be everything to everyone; if you need specific tools, use the appropriate tool for the job. Mashing together everything only results in an unmaintanable project.

o-jasper commented at 2:43 pm on February 20, 2014: none

@ laanwj: I like that you try to modularize the project, but maybe people should be disuaded from using reference implementations as actual-use ones a bit?

At this point it probably doesnt hold back bitcoin at all. But for instance if there was some awesome transaction, like ‘kickstarter’. Which people were trying to popularize, it would be shame if the clients people use didnt support it. In such case, a list of scripts to recommend support for migh be a good idea.

Dont think the current scripting allows for something like kickstarter though!.. I do kindah hold that against some of the altcoins a bit, not at all innovating on transactions.(excepting ethereum, of course! but altcoins wouldnt have to go that far) The starting altcoins dont need to deal with a live blockchain, so they dont have much excuse..

laanwj added the label Wallet on Apr 29, 2014

laanwj added the label Feature on May 18, 2015

laanwj removed the label Improvement on May 18, 2015

laanwj removed the label Priority Medium on May 18, 2015

luke-jr commented at 6:03 am on September 10, 2016: member

Implemented in #8694 (but note that it is NOT a good practice to use multiple wallets for each user in an eWallet setting)

markasoftware commented at 6:34 pm on October 28, 2017: none

@luke-jr what makes it bad to use a separate wallet for each user in a web wallet?

MarcoFalke closed this on Oct 28, 2017

fanquake moved this from the "Issues" to the "Done" column in a project

Bushstar referenced this in commit b2c6b48031 on Apr 8, 2020

MarcoFalke locked this on Sep 8, 2021

Using multiple wallet files with bitcoind #3113