aaronbuchwald

This is a known issue. If the node does not shut down cleanly, this means that it does not have time to write the last accepted block's state to disk...

This can happen if the node times out while shutting down as mentioned above. Does this happen consistently for you? cc @hexfusion looks like the `signal terminated` log is a...

The JS tracer has been deprecated as of v1.7.10 and we do not plan to re-introduce support for it. You can find similar functionality in the existing call tracer (here's...

Sirron Kcuhc https://math.dartmouth.edu/~carlp/73talk.pdf

Could you confirm that it's not calling `BuildBlockWithContext` either? It may call this instead after the Durango activation to provide the P-Chain context for Warp verification. I see that this...

Hmm the VM is wrapped by the ProposerVM as well, which passes the notification through only when it is that node's turn to propose a block. This ensures the VM...

Hmm `MinDelayForProposer` should not be returning a duration of 242h on the node that is the only validator of the network. The value returned from `MinDelayForProposer` should return the minimum...

Could you share a zip of the validator's log directory? I'd be interested to see the debug logs from the ProposerVM to see the path that it takes to returning...

In `MinDelayForProposer`, what P-chain height is being referenced? The parent P-Chain height determines the validator set to produce the next block, so if the validator set has changed and that...

Yup, as of the DUpgrade, only validators are allowed to propose blocks via the ProposerVM. There's already an assumption that your validator set should never be empty because this makes...