Release priorities for v0.4?
4 messages, 13 to 15 Jun 2011. Started by Jeff Garzik.
Jeff Garzik (2), Mark Visser, Theodore Witkamp
With increased reports of stolen wallets, I humbly submit that wallet crypto should be a top priority for the next version. https://github.com/bitcoin/bitcoin/pull/232
Anyway... start pulling :)
[n00b alert]
I humbly suggest allowing the wallet.dat location to be specified in the preferences. Being able to easily physically disconnect a wallet by unplugging a USB key seems like a good idea.
cheers, Mark
On Wed, Jun 15, 2011 at 10:27 AM, Mark Visser <mjmvisser@gmail•com> wrote:
Quoted text (1 line)
> I humbly suggest allowing the wallet.dat location to be specified in the preferences. Being able to easily physically disconnect a wallet by unplugging a USB key seems like a good idea.
That's what -datadir is for. Unfortunately -all- databases must be in the datadir, because wallet.dat is a berkeley db, and we need a transactional environment. That makes it difficult to move just one file.
On Wed, Jun 15, 2011 at 9:50 AM, Jeff Garzik <jgarzik@exmulti•com> wrote:
Quoted text (7 lines)
> On Wed, Jun 15, 2011 at 10:27 AM, Mark Visser <mjmvisser@gmail•com> wrote: >> I humbly suggest allowing the wallet.dat location to be specified in the preferences. Being able to easily physically disconnect a wallet by unplugging a USB key seems like a good idea. > > That's what -datadir is for. Unfortunately -all- databases must be in > the datadir, because wallet.dat is a berkeley db, and we need a > transactional environment. That makes it difficult to move just one > file.
I am a Berkley DB ignoramus , but how is specifying the wallet file path different than using a symlink?
Also I think that allowing the user to open more than one wallet helps the user develop an intuition for the system. A simple task like opening transferring coins from one to the other is currently very awkward on the same installation.
Ted