Quote from: khal on June 04, 2013, 10:48:47 PM

Quote from: midnightlightning on June 04, 2013, 09:22:14 PM

That's 74 seconds after the timestamp of 24191. My retargeting math has worked for all the previous retargets, so why did this one go wonky? Was there some different logic in place for this block round that allowed a slightly different difficulty retarget? Is this a rounding error (after multiplying the old target by the actual time spent, do I need to truncate it before dividing it out)?

Block 22175 is 74s before block 22176 (time of block 22175 = 1318761208).

It is related to a bug known as "retarget hole"/timetravel due to merged mining :
https://github.com/namecoin/namecoin/commit/436f571d41cc53844d482eeef0069a3ca94e08f8
https://bitcointalk.org/index.php?topic=43719.0
https://bitcointalk.org/index.php?topic=43465.0 (first post erased...)

So, after block 19200, go back 2016 instead of 2015.

Thanks! That seems to have fixed it, but for right now the three hard-coded IP seed nodes for Namecoin are all refusing connections, so my client isn't finding any peers to connect to. Was there a new version adopted that change the ports or magic bits of network communications?