don't worry, I read some people had problems compiling my fork so I'll review that and try to generate all the binaries.


This is the final implementation that I have for the superblocks:
Difficulty adjustments were performed every 288 blocks which should take 12 hs, so once every 14 adjustments (ie once a week) we will have a special interval. In these special intervals the difficulty will be adjusted a little bit down for all blocks except one which will be the superblock. The expected behavior is that 287 blocks will be shorter (136 seconds instead of 150), lending 14 seconds each to the superblock which will in total accumulate almost 70 minutes. This is the most elegant solution I could find since every interval will still have 288 blocks and be targeted to last 12hs.
So, if in a few days you get blocks with a reward of 45,33333333 instead of 50, then it is expected behavior. Don't complain: your block had less reward because it was easier to find, it's still fair. And if you get a block with 1389,33333333 RIC, then congratulations: you solved the superblock.


This is implemented, under testing, and working fine so far. Now what remains is to decide the block number for the hard fork (around 135000?), generating all the binaries and issuing alerts for everyone to upgrade.

Regards!
Gatra

Wow, 11 cores running for 1 month, that needs patience man, cong!

Not yet, but it's on my to do list


I'm currently on the hardfork. After some analysis and testing, I think that the best is to start with one superblock of (about one hour) per week and break the record for sextuplets. We would add an entry to the top ten once per week.
After that and with more time we can think of breaking the others. I've been thinking on how to work with much larger tuplets that would take hours or days to find, without the need for superblocks. It would work similar to how pooled mining works: blocks would allow tuplets with one or two composites until we finally find the record tuple of all primes. Doing this we could obliterate all records for tuples of size 6 and onwards!

Tuplets of fewer primes, like twin primes or even single primes are still out of reach until we have more ideas because block verification would take too long.