Terminada

In case it was an intentional decision (to randomise slot battle outcomes) the following is worth noting: * Leader VRF value is something independent of block contents. * Whereas (I...

I think you might be missing the point @reqlez. Slot battles used to be determined in favour of the lowest VRF score (which would favour smaller pools), but now the...

It was a deliberate design feature to determine slot battles in preference of the lower VRF score. But the changes in the most recent version 1.35.3, resulted in the removal...

@cardanoinvest I assume that a fix for this will be unlikely to be rolled out separately. This is because the larger stake pools will have no incentive to upgrade since...

@cardanoinvest If you update your node and the majority doesn't then your node might produce a block on the non-consensus fork causing your block to become orphaned.

Another problem with using the block VRF to deterministically settle "fork battles" is that a malicious pool that is the next valid leader can deliberately choose to cause a fork...

Please stay as an open feature request.

That sort of log information would absolutely suit my needs. I wasn't aware we could get the "tieBreakVRF" values logged ordinarily. What do I need to configure in my node...

I don't actually separately configure an extra .json file output for logging but instead use the normal journal output. I would appreciate a normal log message stating the reason for...

In node version 10.4.1 I have configured MachineFormat for Stdout backend in TraceOptions: ``` "TraceOptions": { "": { "backends": [ "Stdout MachineFormat", ``` MachineFormat provides information like this for each...