Frequently asked questions
A Badge is a non-transferable token (ERC1155) that represents an attestation. Badges prove facts about a user's identity and can be used to access gated applications and services.
Behind each Badge is a group of eligible accounts. You must prove that you own an eligible account to mint a Badge on a destination account.
An eligible account is the source that Badges are derived from. To mint a Badge, users prove that they own an eligible account. Ethereum, GitHub, and Twitter accounts can be used as eligible accounts.
A destination account is where a user mints a Badge. Destination accounts are Ethereum or Ethereum-derived addresses.
Badges are particularly useful for gated services, reputation systems, and decentralized identity curation. When integrated into applications, Badges act as an access tool in the web3 social space.
ZK Badges are privacy-preserving Badges that do not create any link between the eligible and destination account. Users generate ZK Badges by providing the Sismo protocol with zero-knowledge proofs (ZKPs)—cryptographic proofs that verify claims without revealing how they are true.
You can use any account as a source for ZK Badges. During the ZK Badge minting process, the source account is NOT revealed. Whether your eligible account is a public account or a private wallet, no one will be able to infer what eligible account you used.
There are multiple effective use cases for ZK Badges. For example:
- You can use an empty, fresh address as a destination. It will allow you to prove your reputation or leverage personal data from one of your accounts without revealing it.
- You can use your public address (e.g ENS Address that you share on Twitter). It will allow you to import your reputation from your private wallets without revealing them to the world.
No. Badges are non-transferable ERC-1155 tokens.
No, even if you are no longer eligible for a Badge, you will still hold it.
Some applications may require you to renew your Badge, which you will be unable to do if you are no longer eligible.
Badges are timestamped attestations. Depending on Badges and on use cases, applications may require their users to renew their Badge.
The Sismo Vault is an encrypted stash of secrets—accessible only to its owner. Users can privately import accounts into the Vault and store the cryptographic secrets necessary to generate ZK Badges. In essence, the Sismo Vault is analogous to an encrypted password manager—functioning as a UX tool that preserves user privacy. Where password managers store passwords, the Sismo Vault stores cryptographic signatures used for private identity verification on web3.
The Sismo protocol only supports MetaMask and Wallet Connect compatible wallets (e.g: Rainbow).
Smart contract wallets (e.g: Argent, Gnosis Safe Multisig) are not compatible yet, but we are actively working on making them so.
A Vault Owner is an imported account that can decrypt your Vault.
By default, all eligible and destination accounts imported into the Vault are set up as owners. This can be modified in the Vault's settings.
By signing in to Sismo with an owner account, you retrieve your entire Vault and all its imported accounts.
Importing an account in your Sismo Vault means storing the cryptographic tools necessary to generate ZK Badges.
Whether an account is used as an eligible or destination account, you must generate cryptographic tools (a seed and a commitment) as a first step to later generate the ZK proof required to mint a ZK Badge. The Vault stores these cryptographic secrets to give users a seamless experience when using Sismo.
- The seed is generated by signing a message on an account. The seed is used to generate secrets (such as the encryption key of your vault if the account is set as owner or such as commitments needed to generate ZK Badges).
It is to generate your seed and commitment—both required to generate ZK proofs
The Sismo Contributor ZK Badge has 3 different levels:
- Level 1 (Users): 1 voting point per proposal
- Mainly all of the addresses who already interacted with the Sismo main application, as well as some .sismo.eth ens holders.
- Level 2 (Impactful contributors): 50 voting points per proposal
- Holders of specific badges, Sismo Gitcoin donors, Sismo events attendees, and carefully selected .sismo.eth ens holders.
- Level 3 (Builders): 500 voting points per proposal
- Active contributors to Sismo and all the members of the Sismo Core Team.
When connecting to Snapshot, make sure to select the correct wallet owner of the Sismo Contributor ZK Badge.
The ZK Badge's window will open, showing if you are eligible for the ZK Badge or not (refer to the Blue box in the image below).
To know the eligibility criteria for the ZK Badge, click on the badge image or "Badge details" (refer to the Red box in the image below).
The below pop-up will appear.
A brief description of the badge is given under the ZK Badge's name.
For further details, you can click on the Specifications section (please refer to the Purple box in the image above), which will show you the precise eligibility criteria for the ZK Badge.
For further details, you can click on the more button (Red box):
Now you are able to see the precise eligibility criteria of the ZK Badge in the Specifications section (Red box):
Select the More section and click on Hidden. Your ZK Badges will appear.
Now, if you want to make them visible to everyone:
Go to one of your badges and click on Unhide, then sign the message with your wallet.
The minting of sismo.eth ENS Subdomains has been put on hold for now.
To be eligible for a Badge, your address has to be in a group of eligible addresses.
To keep the Badge updated, the creator has multiple choices concerning the update frequency ("refresh") of the group:
- Once: The group will be only be generated one time
- Daily: The group will be updated daily
- Weekly: The group will be updated weekly
- Monthly: The group will be updated monthly
So if you have just completed all the requirements for a Badge, you need to wait for its next group update to become eligible.
To see the next group update for a Badge: click on the badge image or "Badge details" (refer to the Red box in the image below):
Then click on the "more" button (Red box):
Finally, you'll see the next update date at "Next" (Red box):
Note: If the group update frequency is Once, you'll see None written instead of the date.
You just minted the GR15 Gitcoin Contributor ZK Badge, and this allows you to mint the Sismo Contributor ZK Badge. In order to mint it, the address that holds the GR15 Gitcoin Contributor ZK Badge has to be imported into your vault, then you will have to wait for the next update regarding the Contributor ZK Badge group.