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.

Sign up for GitHub

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

Jump to bottom

pcli query chain info does not accurately report jailed/tombstoned/disabled validators #4704

Open
plaidfinch opened this issue Jul 8, 2024 · 1 comment
Open

pcli query chain info does not accurately report jailed/tombstoned/disabled validators #4704

plaidfinch opened this issue Jul 8, 2024 · 1 comment
Labels
A-client Area: Design and implementation for client functionality A-staking Area: Design and implementation of staking and delegation C-bug Category: a bug E-easy Effort: Easy good first issue A good issue for people without existing context on the project. needs-refinement unclear, incomplete, or stub issue that needs work _P-low Priority: low

Comments

@plaidfinch
Copy link
Collaborator

Describe the bug

$ pcli query chain info
Chain Info:
                              
 Current Block Height   36736 
 Current Epoch          1     
 Total Validators       37    
 Active Validators      33    
 Inactive Validators    4     
 Jailed Validators      0     
 Tombstoned Validators  0     
 Disabled Validators    0

This does not show the > 0 jailed validators currently present on the network. This is because the RPC which returns validators changed semantics since this pcli method was written: now it omits all but active/inactive validators.

Expected behavior

Either don't report the statistics about anything other than active and inactive validators, or source the stats another way, but pcli shouldn't give an incorrect stat.
@plaidfinch plaidfinch added A-staking Area: Design and implementation of staking and delegation A-client Area: Design and implementation for client functionality C-bug Category: a bug E-easy Effort: Easy good first issue A good issue for people without existing context on the project. _P-low Priority: low needs-refinement unclear, incomplete, or stub issue that needs work labels Jul 8, 2024
@SkandaBhat
Copy link

Hi @plaidfinch can I work on this? I can check if there is a way to source the stats, if not, I can remove it from the method for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-client Area: Design and implementation for client functionality A-staking Area: Design and implementation of staking and delegation C-bug Category: a bug E-easy Effort: Easy good first issue A good issue for people without existing context on the project. needs-refinement unclear, incomplete, or stub issue that needs work _P-low Priority: low
Projects
Penumbra
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@plaidfinch @SkandaBhat