There are several other things we could consider as well. If this was implemented properly we could probably break most of the records from 7 to 13 or 14. I could probably write this part of the code. I'm also willing to help out with the upgrade but I'm much less familiar with the wallet core. Let me know what you think.
I think we should first complete the upgrade -- making *more* changes to the old code before we get updated will just make future integration harder.
Thank you clo1.
I agree with dga, the priority should be updating the client. After that we can do a hard fork for larger prime sets.
I do have an idea for implementing this, it's no secret. It basically works analogous to shares like in mining, allowing for larger numbers. My plan is to implement that and also rotate between different constellation sizes. So for some blocks it would be 6-tuples, then move to 7-tuples, 8, 9, and so on. It can be done in one chain.
If you can't help with the update, maybe you can work with me on the mining algo update, but I don't want to start coding it until we have an updated version.