[FR] - Log reason when node switches tip to a fork #6014
Labels
needs triage
Issue / PR needs to be triaged.
type: enhancement
An improvement on the existing functionality
Internal/External
External: Stake pool operator
Area
Other: Logging
Describe the feature you'd like
Please log the reason why the node preferred another fork
Describe alternatives you've considered
The independent tool
cncli
provides logging of block data including the block VRF value into a sqlite database. This database can be queried for insight into whether the likely reason the node preferred another fork was because the other fork terminal block had a lower block VRF and the tie break rule was applied.Additional context / screenshots
The node knows the reason for switching tip to a competing fork but this reason isn't logged. Rather the logs only confirm that the tip was switched. But, was the reason due to the competing fork being longer? Or was it due to the other fork's terminal block having a lower VRF causing the tie-break rule to be applied? Or did the node prefer another fork some other reason?
This information would be really helpful when trying to identify what caused your own block to not be adopted.
The text was updated successfully, but these errors were encountered: