johnwolf

The formula is based on the time it takes to generate 2016 blocks. The difficulty is multiplied by 14/(actual days taken). For instance, this time it took 9.4 days, so the calculation was 14/9.4 = 1.49. Previous…

The automatic adjustment happened earlier today. 24/02/2010 0000000043b3e500000000000000000000000000000000000000000000000000 24/02/2010 3.78 +49% I updated the first post.

2 seconds of latency in both directions should reduce your generation success by less than 1%. Probably OK, but I'm not sure. The protocol is designed to resync to the next message, and messages get re-requested from…

I thought about that but there wasn't a practical way to do smaller increments. The frequency of block generation is balanced between confirming transactions as fast as possible and the latency of the network. The…

14/02/2010 0000000065465700000000000000000000000000000000000000000000000000 2009 1.00 30/12/2009 1.18 +18% 11/01/2010 1.31 +11% 25/01/2010 1.34 +2% 04/02/2010 1.82 +36% 14/02/2010 2.53 +39% Another big jump in…

The first automatic adjustment for proof-of-work difficulty happened on December 30, 2009. The lowest difficulty is at 32 zero bits, meaning that even if just one person is running a node, it won't get easier than that.…

> Can nodes on the network tell from which and or to which bitcoin > address coins are being sent? Do blocks contain a history of where > bitcoins have been transfered to and from? Bitcoins are sent to and from bitcoin…

bitcoinbitcoin: What's the deal with Bitcoin anonymity? Can network nodes figure out where bitcoins are sent from or to? Do blocks keep a record of all the bitcoin transfers? Can they link bitcoin addresses to specific…