TL;DR: This document gathers the rules that a badge should comply with to be considered for deployment on the Curated protocol.
Sismo is an open and modular Attestations Protocol enabling anyone to create ZK badges allowing users to prove their reputation or identity without compromising their privacy. To foster the development of composable bricks on top of ZK badges and increase the builder community engagement, Sismo allows anyone to create and deploy their own ZK badges freely through the Factory or by building them themselves.
In addition, the “Curated” badge tag has been created to provide a more curated experience for users and applications looking for carefully assessed and verified ZK Badges. The Sismo community is in charge of vetting which ZK Badge can be tagged as “Curated” by accepting them through a governance vote if they deem them compliant with the following guidelines.
The following guidelines’ objectives are to establish a high-level set of rules and recommendations for the community to take into account in their badge curation activities.
It serves one main purpose:
<aside> 📜 Ensuring the Sismo “Curated” ZK Badges have been assessed and verified by the community and that they hold a sufficient level of quality, transparency, fairness, and alignment with Sismo’s values.
</aside>
The criteria listed below are not exhaustive and have been designed to be purposely open and are to be constructed as a quality filter and not a complete endorsement of the badges.
| Title | Description | Example |
|---|---|---|
| ✅ Clear description & requirements | The badge description and requirements should clearly communicate the eligibility parameters for the group and should match the associated list of eligible accounts and group generator. | A badge whose description and requirements say that it proves an address is registered in Proof of Humanity should only be accepted in the Sismo Curated environment if the associated list of eligible accounts (and group generator) contains all addresses registered PoH and not any other addresses. |
| ✅ Explicit privacy tradeoffs | The badge minting flow should explicitly present the tradeoffs in privacy and confidentiality when they exist. | The minting flow of a badge proving that you signed up to a centralized app should explain that some user data is shared with this app. |
| ✅ Aligned with Sismo’s values | The badge should not be in complete opposition to the values shared in Sismo’s values. | A badge proving that you successfully doxxed an individual should NOT be accepted in the Sismo Curated environment. |
| ✅ Minimum group size | The badge group should have a minimum size of 20 accounts to ensure the anonymity set is not too small. | A badge proving that you are one of the 6 multisig signatories of a DAO treasury should NOT be accepted in the Sismo Curated environment. |
| ✅ Compliant artwork | The badge artwork should follow the https://sismo.notion.site/921d853497fb45efb17459c1ed30c24b and ensure a minimum level of quality (very low-quality or repetitive artwork should be rejected.) | A badge artwork displaying non-readable words should NOT be accepted in the Sismo Curated environment. |
| ❌ No low-quality / engagement badges | The badge should NOT prove overly superficial forms of engagement farming or promotional activities (like generic social media engagement, or simply joining a community) | A badge proving that you liked a Twitter post should NOT be accepted in the Sismo Curated environment. |
| ❌ No clone badge | A badge with the exact same parameters is NOT already hosted on the “Curated” environment (= no clone badges). | A new PoH badge using the exact same group generator, title, description, and artwork as a PoH Badge already deployed on the Sismo Curated environment should NOT be accepted. |
A new PoH badge using a slightly different group generator, title, description, or artwork as a PoH Badge already deployed on the Sismo Curated environment (because it targets another use case) can be accepted. | | ❌ No malicious badges | The badge should NOT prove malicious, scamming, hacking, or immoral intent from the minter and should NOT be directly and positively associated with a malicious, scam, or Ponzi project. | A badge proving that you were one of the exploiters of the Nomad Bridge should NOT be accepted in the Sismo Curated environment.
A badge proving that you were part of the Bitconnect Core Team Multisig should NOT be accepted in the Sismo Curated environment.
A badge proving that you were one of the victims of a specific hack or rug can be accepted in the Sismo Curated environment. | | ❌ No copyrighted/porn/gore badges | The badge should NOT include copyrighted content, pornographic or sexually explicit content, profanity or inflammatory content, hateful or discriminatory content, politically radicalized content, or content encouraging illegal activities | A badge artwork displaying sexual or gore imagery should NOT be accepted in the Sismo Curated environment. |