-
Notifications
You must be signed in to change notification settings - Fork 173
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
chore(inactivity): Rename inactive
flag to sluggish
, add queries, events, and metrics
#714
Conversation
…reverting inactive flag (#689)
…bylonchain/babylon into base/jail-inactive-finality-providers
// provider is no longer considered sluggish | ||
message EventSluggishFinalityProviderReverted { | ||
// public_key is the BTC public key of the finality provider | ||
string public_key = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we also add the bbn address of the fp to the events
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I woudn't mind but what would be the use case?
@@ -225,3 +225,51 @@ func (k Keeper) ListEvidences(ctx context.Context, req *types.QueryListEvidences | |||
} | |||
return resp, nil | |||
} | |||
|
|||
// SigningInfo returns signing-info of a specific finality provider. | |||
func (k Keeper) SigningInfo(ctx context.Context, req *types.QuerySigningInfoRequest) (*types.QuerySigningInfoResponse, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a test for this and return a different structure than the one stored in the db?
related #537
It could be done in another PR also ^^
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice find. Should've added tests for queries there. Done in 8be91d4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sluggish seems funny to me kkk but I like the change 🎉
Some suggestions but no impediments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great work! Sluggish
sounds a bit weird, but I agree inactive
may be super confusing so 👍
Yeah, tbh it's werid to me, too, but it's just temporal and will be changed to |
The
inactive
flag of a finality provider is confused with the finality providers that are not in the active set. So, this PR is to rename the flag tosluggish
, which is a common concept in the BFT world to describe validators who should vote but the votes are delayed for some reason thus committing sluggish faults.This PR also made the following additions: