Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] - Log reason when node switches tip to a fork #6014

Open
TerminadaPool opened this issue Oct 15, 2024 · 3 comments
Open

[FR] - Log reason when node switches tip to a fork #6014

TerminadaPool opened this issue Oct 15, 2024 · 3 comments
Labels
needs triage Issue / PR needs to be triaged. type: enhancement An improvement on the existing functionality

Comments

@TerminadaPool
Copy link

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.

@TerminadaPool TerminadaPool added needs triage Issue / PR needs to be triaged. type: enhancement An improvement on the existing functionality labels Oct 15, 2024
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label Nov 15, 2024
@TerminadaPool
Copy link
Author

Please stay as an open feature request.

@rphair
Copy link

rphair commented Nov 15, 2024

Yes, please: if this is considered impractical to add I would like to hear why. Our SPO operation believes this is important for quality assurance purposes.

@carbolymer carbolymer removed the Stale label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Issue / PR needs to be triaged. type: enhancement An improvement on the existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants