Skip to content
This repository has been archived by the owner on Jan 24, 2025. It is now read-only.

Candidacy Blocks should carry HighestSupportedVersion and ProtocolParametersHash #821

Open
alexsporn opened this issue Mar 8, 2024 · 0 comments
Open

Candidacy Blocks should carry HighestSupportedVersion and ProtocolParametersHash #821

alexsporn opened this issue Mar 8, 2024 · 0 comments
Labels
team-consensus Issues for Consensus Team team-node Issues for Node Team
Milestone
v1.0.0-rc

Comments

@alexsporn
Copy link
Member

alexsporn commented Mar 8, 2024 •
edited
Loading

If a potential active validator has never been selected, we don't know which is their highest supported protocol version and the protocol parameters hash they would use if selected for the next epoch.

We should add these informations also in the CandidacyAnnouncement and track them in the validator list so that they can be displayed correctly in the frontends. Else this will show protocol version 0 and the empty hash.
@alexsporn alexsporn added team-consensus Issues for Consensus Team team-node Issues for Node Team labels Mar 8, 2024
@alexsporn alexsporn added this to the v1.0.0-beta milestone Mar 8, 2024
@alexsporn alexsporn moved this to Backlog in iota-core Mar 8, 2024
@muXxer muXxer moved this from Backlog to Product Backlog in iota-core Mar 11, 2024
@muXxer muXxer modified the milestones: v1.0.0-beta, v1.0.0-rc Mar 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
team-consensus Issues for Consensus Team team-node Issues for Node Team
Projects
iota-core
Status: Product Backlog
Milestone
v1.0.0-rc
Development

No branches or pull requests
2 participants
@alexsporn @muXxer