Hi all, just built the latest bitcoin-git source, seems like the wallet or database format has changed ************************ EXCEPTION: NSt8ios_base7failureE CDataStream::read() : end of data bitcoin in AppInit() terminate called after throwing an instance of ‘std::ios_base::failure’ what(): CDataStream::read() : end of data Could it be 84d7c981dc52cc738053 that broke something ? […]
Read moreMonth: November 2010
Re: RFC: ship block chain 1-74000 with release tarballs?
The following code in AddToBlockIndex(main.cpp) is horribly inefficient, and dramatically slows initial block download: Code: CTxDB txdb; txdb.WriteBlockIndex(CDiskBlockIndex(pindexNew)); // New best if (pindexNew->bnChainWork > bnBestChainWork) if (!SetBestChain(txdb, pindexNew)) return false; txdb.Close(); This makes it impossible to use […]
Read moreRe: Is safe running bitcoins with the same wallet on more computers simultaneously?
Quote Will it be synchronized automatically? Very much not. Using multiple copies of wallet.dat is not recommended or supported, in fact all of Bitcoin is designed to defeat that. Both copies will get screwed up. If you’re trying to consolidate your generated coins into one wallet, a better solution now […]
Read moreRe: RFC: ship block chain 1-74000 with release tarballs?
It appears that blk0001.dat, where bitcoin stores block chain information, is compatible across Windows, Linux, 32-bit and 64-bit. Therefore, why not save new users some time by shipping blocks 1-74000 with each release? Presumably, indexing and verifying a local file would be faster, and use fewer network resources, than downloading […]
Read moreRe: Cooperative mining
Quote from: grondilu on November 27, 2010, 22:21:27 To me it seems that cooperative mining is a tough task, because the honnesty of participants has to be checked. What’s preventing someone to run a modified version of the client, that would just keep generated bitcoin for himself, while receiving bitcoins […]
Read moreRe: New demonstration CPU miner available
A new CPU miner is now available, making use of the new ‘getwork’ RPC command. In the beginning, this is intended largely to demonstrate a ‘getwork’ miner. It is written in straight C, with minimal dependencies (libcurl, jansson). It has successfully generated blocks on testnet, mainnet and almost all pools. […]
Read moreRe: New getwork
Quote from: satoshi on November 24, 2010, 17:21:01 – It does not return work when you submit a possible hit, only when called without parameter. It would be immensely useful if you’d return if what I sent to the client actually was an actual hit. It makes it easier to […]
Read moreRe: Version 0.3.17
Who’s in charge of the OSX build? Given it usually lags behind I assume it is done by someone not using OSX as the primary OS. I can help with this if that’s the case, just point me to how things are done right now. Laszlo does them, but I […]
Read moreVersion 0.3.17
Version 0.3.17 is now available. Changes: – new getwork, thanks m0mchil – added transaction fee setting in UI options menu – free transaction limits – sendtoaddress returns transaction id instead of “sent” – getaccountaddress <account> The UI transaction fee setting was easy since it was still there from 0.1.5 and […]
Read moreRe: RFC: ship block chain 1-74000 with release tarballs?
It appears that blk0001.dat, where bitcoin stores block chain information, is compatible across Windows, Linux, 32-bit and 64-bit. Therefore, why not save new users some time by shipping blocks 1-74000 with each release? Presumably, indexing and verifying a local file would be faster, and use fewer network resources, than downloading […]
Read more