The Regen Score team understands that the Regen Score can be difficult to interpret. The team is committed to making as easy to understand as possible. Some actions to facilitate this include:
Explaining the criteria for listing tokens and attestations in its current documentation: The Regen Score team considers multiple factors when selecting attestations, including impact, transparency, feasibility, and public interest. Criteria will evolve as the platform develops."
…
This is too vague, remember that you are building an onchain identity platform, given its success, other projects might choose to build on top it. I firmly believe that anything related to onchain identity must be public and fully transparent.
Please explain the documentation, explain what “factor”, what you consider as “impact”.
Mention each criteria with the score assign to them, if absolute is not possible, give us range.
How would you expect a end user to trust the score if we dont know which factor is impacting the said score ?
The score calculation mechanism is chain-agnostic and pulls data from multiple chains and other sources. The attestation mechanism (using https://attest.sh/) is implemented on both Sepolia and mainnet. We were undergoing final checks of the minting system to make sure it’s secure and ready for wide release. It’s coming to the Mainnet today
What we considered impact was arbitrary and nebulous (at this point) but intuitively it can be thought of as a “benefit”. With this framing, we sought to assess how beneficial each action was to the ecosystem before assigning a weight to it. We considered impact both in isolation and in relation to each other as we sought to develop weights that would properly rank order behaviours in a reasonable fashion. Holding all other things equal, we’d expect that the score would highlight a person participating in governance as being more beneficial than someone who only held the token or that a person deploying a contract could be more beneficial to the ecosystem than a person just claiming an airdrop. Though there are plenty of other ways to conceptualize impact, it was this framing that we settled on to derive the weights that generate our regen score.
Second, is the code base public?
Sure, here’s Github, the link is also in the footer
Thanks for the update @maxsemenchuk! Please not that all Missions will be able to showcase their work tomorrow during a dedicated Mission demo day on September 28th, at 16:00 GMT on the Discord mainstage!