Quote from: relm9 on May 12, 2013, 06:21:22 PM

Quote from: eja on May 12, 2013, 06:19:33 PM

Using the nfactor calculating code from the client I get for the coming year (timestamps in UTC):

Wed May 8 05:33:20 2013, factor: 4
Tue May 14 07:11:28 2013, factor: 5
Fri May 17 08:00:32 2013, factor: 6
Mon May 20 08:49:36 2013, factor: 7
Wed May 29 11:16:48 2013, factor: 8
Sat Jun 1 12:05:52 2013, factor: 9
Tue Jun 25 18:38:24 2013, factor: 10
Sun Jul 7 21:54:40 2013, factor: 11
Tue Aug 13 07:43:28 2013, factor: 12
Mon Sep 30 20:48:32 2013, factor: 13
Mon Nov 18 09:53:36 2013, factor: 14

Apparently the N factor allocation is broken...

https://bitcointalk.org/index.php?topic=200170.msg2117745#msg2117745

The N assignment + dynmic hashing looks good to me