👩‍💻
Galactica Network Dev Documentation
  • 📙Galactica Network Overview
  • 🧬Galactica Concepts
    • ⛓️Blockchain Base
    • 🧾Zero-Knowledge KYC
      • Holder Commitment
      • DApp specific HumanID
      • Verification SBT
      • KYC Guardian
      • Galactica Investigation Module
      • Privacy Precautions
    • 🌟Reputation
    • 🛂Contingent Transactions
  • ⚙️Galactica Components
    • 🦊Galactica Snap for Metamask
    • 🌳Root Contracts
  • 🏗️Building a Galactica DApp
    • Example DApps
      • Compliant ERC20
      • Cypherbook
      • Compliant DEX
      • Sybil resistant airdrop
    • Front End
      • Guided Example
        • Connect to Galactica Snap
        • Prepare ZK proof generation
        • Generate and submit ZK proof
        • Handle Verification SBTs
      • Galactica Snap JSON-RPC API
    • Smart Contracts
    • Custom Zero Knowledge Disclosures
  • 📝Guardian Guide
    • Setup to become a Guardian
    • Create and issue ZK certificate
      • 🪪zkKYC (GIP-1)
      • Arbitrary ZK data certificate (GIP-2)
      • X/Twitter ZK certificate (GIP-3)
      • REY X/Twitter Score ZK certificate (GIP-4)
      • Decentralised Exchange (DEX) ZK certificate (GIP-5)
      • Centralised Exchange (CEX) ZK certificate (GIP-6)
      • Telegram ZK certificate (GIP-7)
  • ⛏️Validator Guide
    • 🔧Installation
    • 🔗Become a Validator
    • 🚀galacticad CLI Usage Cheat Sheet
    • 🔒Security Best Practices
  • 🧪TestNet: Reticulum
    • Release Notes
  • 🧪DevNet: Andromeda
    • Release Notes
  • 📎Changelog
Powered by GitBook
On this page
  • What it is
  • Purpose
  • Contents

Was this helpful?

  1. Galactica Concepts
  2. Zero-Knowledge KYC

Verification SBT

PreviousDApp specific HumanIDNextKYC Guardian

Last updated 1 year ago

Was this helpful?

What it is

Verification soul-bound tokens (SBTs) are on-chain records. They state successful zkKYC verifications between a wallet addresses and verifier smart contracts corresponding to a DApp. The soul-bound property means that it can not be transferred. Instead it has to be recreated for another wallet with a new ZKP verification.

The on-chain registry is implemented in an EVM smart contract. Galactica provides a standardized system instance defined here: DevNet: Andromeda In general, also custom registries can be deployed and used.

Purpose

  • On-chain record for reference in smart contracts

  • Unlocks using DApps requiring compliance without regenerating a ZKP every time

  • Carries data about verification

Contents

The data contained in a Verification SBT is defined in the .

  • Wallet address of the user

  • Address of the DApp the verification was for

  • Verifier Codehash for tracking what version of the verifier was used. This allows upgrading DApp requirements and migrating previous verifications.

  • KYC Guardian public key

  • Fraud investigation data, see Galactica Investigation Module

🧬
🧾
smart contract