-
Notifications
You must be signed in to change notification settings - Fork 209
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
feat: Reputation: CNS-1005 - Reputation pairing score #1626
base: CNS-1004-reputation-qos-score-aggregation
Are you sure you want to change the base?
feat: Reputation: CNS-1005 - Reputation pairing score #1626
Conversation
…5-reputation-pairing-score
…5-reputation-pairing-score
…5-reputation-pairing-score
…5-reputation-pairing-score
…5-reputation-pairing-score
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
…5-reputation-pairing-score
…5-reputation-pairing-score
…5-reputation-pairing-score
…5-reputation-pairing-score
…5-reputation-pairing-score
Description
Closes: #XXXX
In this PR I've implemented the reputation pairing score mechanism. After aggregating QoS score over an epoch, every epoch start we update the QoS score for all providers with the epoch QoS score. After that, we group all the providers with the same chain ID and cluster and compare the QoS scores between them. According to the rank, we convert the QoS score to a reputation pairing score which ranges between 0.5-2. This can be used to affect the pairing chance of providers.
Note, the reputation pairing score is fully implemented but disabled. This will be enabled in the future after further analysis (mainly dependent on data collected from raw QoS excellence reports).
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
in the type prefix if API or client breaking changemain
branchReviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...