July 17

Download links available now on bitcoin.org. Everyone should upgrade to this version. - Added a simple security safeguard that locks-in the block chain up to this point. - Reduced addr messages to save bandwidth now t…

Quote from: singpolyma on July 17, 2010, 10:19:48 PM My coins disappeared, but I assume they'll come back when it's up to current? Right, they'll re-appear when it's finished downloading all the blocks.

Quote from: llama on July 17, 2010, 09:56:25 PM However, it's important that you don't lock all the way up the very latest block. Otherwise, the attacker could generate a fake block (or a few) right before you happen…

I believe it'll be possible for a payment processing company to provide as a service the rapid distribution of transactions with good-enough checking in something like 10 seconds or less. The network nodes only accept…

It must be a rounding error when getinfo converts to floating point to return the JSON-RPC result. The only place where it uses floating point to represent money is returning a value in JSON-RPC. 1.139999999999 is lon…

0.3.2 has some security safeguards to lock in the block chain up to this point and limit the damage a little if someone gets 50%. But if someone has 50%+ of the CPU power and malicious intent, they can prove what it a…

Quote from: NewLibertyStandard on July 17, 2010, 10:22:09 PM Version 0.3 was supposed to reduce the number of outgoing connections on non-port forwarded clients from 15 to 8, but I don't think it really happened. I'm…

We should queue up a supply of pre-made addresses in the wallet to use when a new address is needed. They aren't very big, so it wouldn't hurt to have a lot of them. This would more generally cover the case also where…

I didn't realize you were going to document all the intentionally undocumented commands. They're unsupported and not intended to be used by users. All the user-facing commands are listed in the -? help.