-
Notifications
You must be signed in to change notification settings - Fork 40
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(adr-39): Refactor rewarding #360
Conversation
// skip if finality provider didn't vote | ||
if _, ok := voters[fp.BtcPk.MarshalHex()]; !ok { | ||
continue | ||
} |
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.
Does this mean that the reward for unvoted FPs remains in the feeCollector
account? For example, assuming 4 FPs with equal voting power, 3 of them voted for a block, and 1 did not. Then 3/4 of the reward in the reward gauge is distributed to the 3 FPs, whereas the rest 1/3 remains.
Is this expected or we want to distribute the whole reward to voted FPs?
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.
Good point. I didn't think of that. I think we should split all the rewards to the voted FPs but what happens if the rewards remain in the feeCollector
account?
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 think we should split all the rewards to the voted FPs
Agree with that. We should split the rewards between all fps that voted on finalized block.
cbb211e
to
f17d83e
Compare
f17d83e
to
29c8150
Compare
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.
lgtm!
Implements https://github.com/babylonlabs-io/pm/pull/145 including:
finality_sig_timeout