On May 15, 2014 7:09 PM, Brian May br...@microcomaustralia.com.au wrote:
Hello,
Is this bug still relevant?
My understanding is that upstream switched from bdb to leveldb:
https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki
The blockchain uses leveldb but the wallet still uses
What happened with 0.8 was this: rather than keeping an index of every
transaction, with its position in each block, etc, in BDB, a LevelDB is
created, and it's used to maintain what's called the UTXO set, short for
Unspent Transaction Output set. Basically, this contains all unspent
transaction
severity 731952 wishlist
tags 731952 wontfix
thanks
In the bitcoin_0.8.6-1.dsc file, the Build-Depends: section includes the
entry libdb++-dev | libdb4.8++-dev. This results in the package potentially
being built with BDB version 5.1. The recommended version, and the one that
the upstream
The problem is not easily worked around by importing/exporting private
keys, as there will potentially be many different keys that need to be
exported and reimported, some of which aren't even exposed to the user due
to the mechanics of change addresses and the keypool. Additionally, users
expect
And additionally, if you attempt to run a 4.8-built binary with a 5.1
wallet, the error isn't clear about the problem, as it's a BDB failure and
not a Bitcoin one, that can be very confusing to troubleshoot.
On Wed, Dec 11, 2013 at 6:51 PM, Micha Bailey michabai...@gmail.com wrote:
The problem
5 matches
Mail list logo
