back to home

sismo-core / sismo-badges

Contracts of the Sismo Badge Minting Protocol

15,961 stars
532 forks
8 issues
TypeScriptSolidityDockerfile

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing sismo-core/sismo-badges in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/sismo-core/sismo-badges)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Sismo Protocol Contracts Made by Sismo This repository contains the smart contracts of the Sismo Protocol. There are three core contracts: • : The registry stores all attestations. It is owned by the governance that authorizes/unauthorize issuers to record in it • The standard abstract contract must be inherited by attesters. Attesters are issuers of attestations. They verify user requests and build attestations that will be recorded in the registry • Reads the registry. Stateless Non Transferable Token view of attestations (ERC1155) It also contains implementations of attester in : • : ZK Attester using the Hydra S1 Proving Scheme and the notion of nullifiers. Users must provide a ZK Proof along with their request to generate attestations • : Accountbound version of the Simple Hydra S1 Simple Attester. (Users can update at will where the attestation is stored) Sismo protocol A complete overview of the protocol is available in our documentation Deployed contracts Deployed contracts can be found here Usage Installation Compile contracts Compile contracts using hardhat Test Launch all tests Print storage layout Deploy on local chain Terminal tab 1 Terminal tab 2 Create a new Attester To develop a new attester, you must inherit the abstract contract and implement the following functions: • : You must implement the user request verification against the proof provided by the user • : You must build the attestations that will be recorded from a verified user request Other optional hook functions that can be implemented: • • The is a good example of an attester implementing those functions. A guide is offered in our documentation. Feel free open a PR with your new attester in ! License Distributed under the MIT License. Contribute Please, feel free to open issues, PRs or simply provide feedback! Contact Prefer Discord or Twitter