Steve is not interested in approximately half the hashrate of the network? Sure that hashrate can go elsewhere. The idea that the developer doesn't seem to care about breaking major chunks of the ecosystem is concerning.

I've re-implemented the pool several times now, with several different forks (including the exact forks other running pools use), with several different forks of the back-end used by the pool forks.

All error messages, and research into them indicate a problem with a hardfork. I will continue my search for the secret fix the developer is withholding (probably located within node-cryptonote-util) for a bit more.

I can attempt to re-implement with entirely new pool software (not the same pool software all current IRD pools run) but this would involve migrating to a completely new DB schema.

I said earlier in this thread when mine77 was shutting down I would continue to run irdpool.tk on the condition it wasn't a major time sink. It now is. I have a actual development work I need to be doing, not reverse engineering someone else's patches.