Quote from: mine77 on September 19, 2017, 08:07:24 PM

Quote from: Speedie on September 19, 2017, 07:32:04 PM

Dev, with all due respect you seem to be rather disengaged from your project. There have been ongoing problems for more than a day now, yet all we have from you is one post 12 hours ago (and more than 12 hours AFTER the blockchain got stuck) saying that the pool operators need to restart / resync, and the code needs fixing.

I have to agree. What I can share from the mine77 pool server logs is that people are mining blocks, but then the iridiumd daemon is rejecting them. It seems very similar to what is reported here from another CryptoNote coin, as the sequence of messages in my daemon log are the same (too-big-block, then repeated block not accepted due to bad tx).

Code:

DAEMON 2017-Sep-19 19:00:06.899784 INFO [Blockchain] Block is too big: 25507 bytes, exptected no more than 25199 bytes
POOL:: 2017-09-19 19:15:52 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:15:52.326135 INFO [Blockchain] Block has at least one transaction with wrong inputs:
POOL:: 2017-09-19 19:18:17 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "valid" - {"code":-7,"message":"Block not accepted"}
DAEMON 2017-Sep-19 19:18:17.977028 INFO [Blockchain] Block <4eb47cab000946155c1d5ccf171c2aa5caaa7db29eecfb3246f5bd187fdd0221> has at least one transaction with wrong inputs:
POOL:: 2017-09-19 19:25:37 (Thread 2) Error submitting block at height 8305 from xxx@xxx, share type: "trusted" - {"code":-7,"message":"Block not accepted"}
etc.

Blobsize from transactions exceeding limit.
https://github.com/cryptonotefoundation/cryptonote/blob/master/src/CryptoNoteCore/Blockchain.cpp#L373