Score Weight Update Documentation

[erichfi]

User Story:

As a member of the Passport project team, I aim to efficiently implement and communicate the recent score weight changes within our platform. This will ensure that all stakeholders, including our users and integration partners, are well-informed and can smoothly transition to these updates.

Acceptance Criteria

GIVEN the introduction of planned score weight changes,
WHEN these updates are deployed in the forthcoming platform update,
THEN the adjustments are precisely incorporated into the scoring model. Additionally, extensive support documentation and resources are made available to all parties impacted by these changes.

Product & Design Links:

[Placeholder for links to documentation, FAQs, and change logs detailing the score weight changes]

Tech Details:

The upcoming update will introduce several adjustments to the weight of credentials available in Passport. These changes aim to refine the scoring model, enhancing its effectiveness and equity. The detailed list of score weight changes includes both increments and reductions, underpinned by thorough analysis and deliberation. Below is the updated list of credentials and their new weights:

• CoinbaseDualVerification: 16.042
• HolonymGovIdProvider: 16.026
• NFTScore#50: 10.033
• ETHScore#50: 10.012
• IdenaState#Newbie: 6.028
• CivicUniquenessPass: 6.005
• GitcoinContributorStatistics#totalContributionAmountGte#1000: 5.018
• TrustedCitizen: 4.041
• SelfStakingGold: 3.037
• githubContributionActivityGte#120: 3.019
• CivicLivenessPass: 3.004
• ExperiencedCommunityStaker: 2.515
• SelfStakingSilver: 2.038
• NFTScore#90: 2.035
• NFTScore#75: 2.034
• IdenaState#Verified: 2.029
• IdenaState#Human: 2.027
• githubContributionActivityGte#60: 2.021
• githubContributionActivityGte#30: 2.020
• GitcoinContributorStatistics#totalContributionAmountGte#100: 2.017
• ETHScore#90: 2.009
• ETHScore#75: 2.001
• Linkedin: 1.531
• BeginnerCommunityStaker: 1.513
• SelfStakingBronze: 1.036
• NFT: 1.032
• CivicCaptchaPass: 1.014
• ETHGasSpent#0.25: 1.003
• Lens: 0.93
• SnapshotProposalsProvider: 0.839
• GnosisSafe: 0.822
• Brightid: 0.802
• GuildAdmin: 0.724
• ZKsyncEra: 0.606
• GuildPassportMember: 0.54
• Google: 0.525
• GitcoinContributorStatistics#totalContributionAmountGte#10: 0.523
• Discord: 0.516
• TrustaLabs: 0.511
• ETHnumTransactions#100: 0.51
• ETHDaysActive#50: 0.507
• Ens: 0.408
• zkSyncScore#5: 1.67 points
• zkSyncScore#20: 1.67 points
• zkSyncScore#50: 1.67 points

Open Questions:

• How will we track the effect of these weight changes on overall user engagement and the distribution of scores across the platform?
• What feedback mechanisms will be established to collect responses from users and integration partners regarding these updates?

Notes/Assumptions:

• These adjustments are predicated on extensive analysis, aiming to enhance the precision, fairness, and relevance of the scoring system.
• A well-structured communication and support strategy is essential for facilitating a smooth adaptation process for all stakeholders involved in the Passport ecosystem.

[erichfi]

Pessimistic 2 Points

[lucianHymer]

Hey @erichfi ! What exactly does this ticket include from an engineering perspective? Should I just be updating the default weights and then running the rescore after merging? The UI updates have been addressed here #2330

[lucianHymer]

These new scores add to 125.913
Is that fine? Are some of these mutually exclusive now?

It doesn't really matter from a scoring logic perspective. But it does make the progress ring in the UI potentially a poor representation of the score.

[erichfi]

Hey @erichfi ! What exactly does this ticket include from an engineering perspective? Should I just be updating the default weights and then running the rescore after merging? The UI updates have been addressed here #2330

@lucianHymer, yes, making sure everything gets scored as planned.

These new scores add to 125.913
Is that fine? Are some of these mutually exclusive now?

It doesn't really matter from a scoring logic perspective. But it does make the progress ring in the UI potentially a poor representation of the score.

Yes the total >100 is fine

[lucianHymer]

Will handle re-scoring after deployment