Closed obycode closed 3 weeks ago
This seems to be due to the miner submitting an invalid block commit built off of 129 and not successfully rbf'ing it before 130 is mined. Therefore it always keeps trying to rebuild off the wrong commit and signers correctly reject it.
Running in naka-3 with branch
fix/5136-signer-block-state-tracking
(as of commit 3047b5f10f9aa1e0ea0464433956ff6455574122), I am seeing some strange behavior from the Nakamoto miner. In the first tenure of epoch 3.0, burn block 131, the canonical tip is block 128, but the miner is attempting to reorg this block and mine another block 128. The signers correctly reject these block proposals, so we end up with no blocks in tenure 131. Complete logs can be found here.Miner Logs:
Signer logs: