Quote from: Neon~ on September 14, 2017, 02:59:55 PM

If the error is at pool side, the latest update might have changed the block format in any way that the pool code doesn't recognize it?

LOL, like this in cryptonoteconfig.h?

Code:

const uint8_t CURRENT_TRANSACTION_VERSION = 2;

I've turned off mine77 until this gets sorted out, I was able to restart the pool by patching the cryptonote-utils npm module but even when blocks got found they weren't accepted by the network, so I'm not going to waste people's hashpower:

Code:

2017-09-14 15:49:41 (Thread 1) Error submitting block at height 6355 from ir2...., share type: "trusted" - {"code":-7,"message":"Block not accepted"}
2017-09-14 15:49:43 (Thread 1) Error submitting block at height 6355 from ir2...., share type: "trusted" - {"code":-7,"message":"Block not accepted"}
2017-09-14 15:57:09 (Thread 1) Error submitting block at height 6355 from ir2...., share type: "valid" - {"code":-7,"message":"Block not accepted"}