At some point, a website or person accepting a transaction must take this risk. It is unavoidable, whether you use listreceivedbyaddress or listtransactions. This is why listtransactions reluctance seems so unusual. Almost every exchange or website accepting bitcoins achieves a binary decisionpoint, where the transaction is accepted, and goods are […]
Read moreAuthor: Satoshi Nakamoto
Re: JSON-RPC method idea: list transactions newer than a given txid
It would be great to have a JSON-RPC method for listing new transactions that are newer than a particular transaction id. This would enable developpers to watch new transactions easily, by just keeping track of the latest known txid and polling that method at the rate of their choice. A […]
Read moreRe: Wikileaks contact info?
Quote from: RHorning on December 04, 2010, 22:17:44 Basically, bring it on. Let’s encourage Wikileaks to use Bitcoins and I’m willing to face any risk or fallout from that act. No, don’t “bring it on”. The project needs to grow gradually so the software can be strengthened along the way. […]
Read moree: RFC: ship block chain 1-74000 with release tarballs?
I timed two runs with clean data directories (no contents), -noirc, -addnode=10.10.10.1, Linux 64-bit. Hardware: SATA SSD Mainline, no patches: 32 minutes to download 94660 blocks. Mainline + TxnBegin/TxnCommit in AddToBlockIndex(): 25 minutes to download 94660 blocks. That’s a good optimisation. I’ll add that next time I update SVN. More […]
Read moreRe: Incompatible wallet format with latest bitcoin-git ?
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 moreRe: 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 more