Sismo Docs
  • Welcome to Sismo
    • What is Sismo?
  • Build with Sismo Connect
    • Overview
    • Installation
    • Sismo Connect Cheatsheet
    • Tutorials
      • Get Your appId - Create a Sismo Connect App
      • Onchain Tutorial (1/2): Code Your Airdrop Contract With Privately-Aggregated Data
      • Onchain Tutorial (2/2): Deploy Your Airdrop Contract
    • Technical Documentation
      • Sismo Connect Configuration
      • Auths
      • Claims
      • Signature
      • Packages
        • Sismo Connect Client: Request
        • Sismo Connect React: Request
        • Sismo Connect Server: Verify Offchain
        • Sismo Connect Solidity Library: Verify Onchain
    • FAQ
  • Data Groups
    • Overview
    • Tutorials
      • Factory Guide: Create a Data Group in 5 Minutes
      • Sismo Hub Guide: Create Data Groups Programmatically
      • Sismo Hub Guide: Add a Data Provider to the Sismo Factory
    • Sismo Hub
      • Sismo Hub Repository
        • Group Generators
        • Data Providers
        • Data Operators
        • Command Line Interface
      • Accounts Registry Tree
  • Data Vault
    • Overview
    • Vault Identifiers
    • Proving Schemes
      • Hydra-S1
      • Hydra-S2
    • Commitment Mapper
  • Resources
    • Deployed Contract Addresses
    • Sismo API
      • API Links
      • Query From a Client
      • Group
        • Get groups
        • Get group snapshots
      • Common Parameters
      • Advanced Filtering
      • Transaction
  • Links
    • Sismo Landing Page
    • Sismo Factory
    • Sismo App Store
    • Sismo Builder Resources
    • GitHub
    • Discord
    • Twitter
    • Blog
Powered by GitBook
On this page
  1. Data Vault
  2. Proving Schemes

Hydra-S1

The Hydra-S1 proving scheme is the first proving scheme in the Hydra family:

  • Hydra = using Hydra Proof of Ownership via the Commitment Mapper

  • S1 = single source, version 1: verifying membership in a single Data Group

Currently, the proving scheme is utilized by the ZK Badge protocol, which is no longer maintained. It allows users to verify membership in a Data Group from a single Data Source and mint a ZK Badge on an unlinked Ethereum address.

Sismo’s ZK Badge protocol uses Hydra S1 proving schemes to issue ZK Badges. You can see them here. While the contracts are still deployed, Sismo no longer maintains the ZK Badge protocol. Read more in this blog post.

Hydra Proof of Ownership

The Hydra-S1 proving scheme allows participants to establish, in one ZK proof, that for a given Proof Identifier:

  • They own 2 accounts (source and destination)

  • The source account is part of an Accounts Registry Tree

  • The source account was registered in the Accounts Registry Tree with a specific value

  • A claim about their source account value is true

    • e.g: "my account value is superior to 5" (non-strict claim)

    • or "my account value is strictly equal to 5" (strict claim)

  • They correctly generated a Proof Identifier

A Proof Identifier functions as a nullifier for the Hydra-S1 proving scheme, preventing the same user from minting a certain ZK Badge more than once.

PreviousProving SchemesNextHydra-S2

Last updated 1 year ago