Sismo Docs

What is Sismo?

Sismo is a modular Attestations Protocol focused on decentralization, privacy and usability. It issues tokenized attestations: Badges (Non-Transferrable Tokens/SBT).
Two instances of the protocol have been deployed on polygon (contracts)
  • Playground, permisionless protocol: Any team can create ZK Badges for their community (via our factory or using our tutorial)
  • Main, curated protocol: Only features badges that were curated by our governance.
Apps: Main | Playground
Using Sismo, users can generate a wide range of attestations, such as "Donated to Gitcoin grants", "Voted 2 times in the ENS DAO" or "Sent 100+ transactions on Ethereum".
With these attestations, they can gain access to premium features within gated services, or prove their reputation in apps and protocols consuming said attestations.
Attestations are easily accessible via Non-Transferable Token (ERC1155) representations known as Badges.
For each attestation they generate, a user will also receive the associated Badge.
Sismo Badges are especially useful for:
  • Web2/web3 gated services
  • Reputations systems
  • Decentralized Identity curation

ZK Badges

A strong focus of Sismo is on ZK Badges, which do not reveal anything about how they are created. The generation process of ZK Badges relies on zero-knowledge proofs (ZKP) and ensures user and data privacy.

Modular and Interoperable

The Sismo protocol is modular with multiple types of Badges co-existing; these are generated by various Attesters (smart contracts) that make different tradeoffs on privacy, decentralization and/or scalability.
Sismo's end goal is to enable diverse and interoperable Badges that can be meshed together in creative ways, and facilitate real innovation on authentication and reputation systems.
Anyone can propose badges to be attested or build a new attesters with a novel logic for minting badges.

Chat with us!

Are you a community looking to reward your most important members, a project in need of a reliable reputation system or a service that wants to gate some of its features?
Let us show you how do this with an open-source, decentralized, privacy-preserving protocol!
Last modified 17d ago