LogoLogo
ProductsCommunityGitHubShare Feedback
NFT Kit
NFT Kit
  • What is the NFT KIT?
    • Introduction
    • Non-Fungible Tokens (NFTs)
      • NFT | Basics
      • Technologies & Concepts
    • NFT Kit
      • NFT Kit | Basics
        • Overview
        • Functionality
      • NFT Flavors & Ecosystems
      • Architecture
        • Low-Level Service Abstraction
        • Ecosystem Abstraction
        • High-Level Interfaces / APIs
      • Use Cases
  • Getting started
    • Quick Start
  • Ecosystems
    • Ethereum | Polygon | Shimmer
      • Setup
      • NFT | Creation & Management
        • Smart Contract Deployment
        • Minting NFTs
        • Get NFT Metadata
        • Get Account Balance
        • Get Token Owner
        • Get Collection Info
        • Get NFTs by Account
      • NFT | Ownership Verification
        • Ownership Verification
        • Ownership Verification With Traits
      • Smart Contract | Extensions
        • Pausable
        • Burnable
      • Smart Contract | Access Control
        • Ownership
        • Role-Based Access Control
    • Ocean Protocol
      • Setup
      • NFT | Verification
      • NFT | Wallet
      • Architecture
    • Tezos
      • Architecture
      • NFT | Creation & Management
        • Smart Contract
        • Add Minter
        • NFT Minting
        • Fetch NFT metadata
        • Get account NFTs
        • Get contract metadata
      • NFT | Ownership Verification
        • NFT Ownership Verification
        • NFT Ownership Verification Within A Collection
        • NFT Ownership Verification With Traits
      • NFT | Wallet
      • Tutorials
        • Minting NFTs on Tezos
          • Setup
          • New Collection
          • First NFT
          • Verification
          • Wallet
    • Near Protocol
      • Architecture
        • Smart Contract
        • Blockchain NFTs operations
        • NFTs Queries
      • NFT | Creation & Management
        • NEAR Sub-Account
        • Deploy NFT Contract
        • NFT | Minting
      • Querying NFT information controller
        • Get NFTs for account
        • Get NFT By Token Id
        • Get NFT contract metadata
      • NFT | Wallet
      • Tutorials
        • Minting NFT on Near Protocol
          • Near Wallet Creation
          • Setup NFT-Kit
          • Create Sub-account
          • Smart Contract ( Collection )
          • Minting your first NFT
        • NFT Ownership Verification
        • Wallet
    • Polkadot
      • Architecture
      • Query NFTs
        • Unique network
          • Fetching Token id & Collection id
          • Fetching NFT metadata
        • Parachain Networks
          • Fetching Tokens by subscan
          • Fetching EVM ERC721 Collectibles by subscan
      • NFT | Ownership Verification
        • NFT ownership verification
        • NFT ownership verification within a collection
        • NFT ownership verification with traits
      • NFT | Wallet
        • Polkadot parachains
        • Polkadot EVM compatible parachains
    • Flow
      • Architecture
        • Cadence Scripts
        • NFT Operations (FCL)
      • Querying NFT information Controller
        • Get NFTs for an account
        • Get NFTs in Collection
        • Get NFT by Token Id
      • NFT | Ownership Verification
        • NFT ownership verification on Flow
        • NFT ownership verification in collection on Flow
      • NFT | Wallet
        • Flow Blockchain
    • Algorand
      • Architecture
        • Algorand Standard Assets (ASAs)
      • NFT | Creation & Management
        • Account Creation
        • NFT Creation (ARC3)
      • Querying Asset information
        • Get Assets for account
        • Get Asset Details
        • Get NFT Metadata by asset id
        • Get NFT by Asset id
      • NFT | Ownership Verification
        • NFT ownership verification
        • NFT ownership verification with traits
        • NFT ownership verification Based on Creator
        • NFT Metadata verification against a dynamic policy
      • NFT | Wallet
        • Algorand Blockchain
    • IPFS
  • Concepts
    • Soulbound Tokens (SBTs)
    • NFT verification with OPA
  • Configurations
    • Configuration Files
    • Gas Provider
  • Community
    • Discord
    • Twitter
    • Newsletter
    • GitHub Discussions
  • DEVELOPER RELATIONS
    • Roadmap
    • Contribute
    • Share Feedback
    • Contact
  • Product Editions
    • Open Source | Always Free
    • Enterprise | Self-Managed
    • Cloud Platform | Managed
Powered by GitBook
On this page
  • What are SBTs
  • How you can use SBTs with walt.id

Was this helpful?

Export as PDF
  1. Concepts

Soulbound Tokens (SBTs)

SBTs are non-transferable digital tokens containing information about a person or entity.

PreviousIPFSNextNFT verification with OPA

Last updated 1 month ago

Was this helpful?

What are SBTs

SBTs are non-transferable unique digital tokens. They are issued once to an address, which could be owned by an individual or entity, stating information or accomplishments about the address owner.

Use-Cases of SBTs:

  • Proof Of Personhood, e.g through verification of a phone number.

  • Proof Of Attendance, e.g. proofing that an individual attended an event.

  • Proof Of Steps Completed e.g. that the owner went through an KYC process successfully.

However, the data stored in SBTs should never include sensible personal information. For that, Verifiable Credentials and mdocs are a much better fit, because here, no sensible data is stored on the blockchain. A privacy requirement in many countries. Read more about it our post about

Nonetheless, the SBTs offer great utility for many different use-cases, like reputation building and more.

How you can use SBTs with walt.id

Leveraging the walt.id open-source products, you can mint and verify SBTs and create wallet solutions where users can view their digital tokens.

Minting Solution

Deploy SBT smart contracts directly via Java, Kotlin or our REST interface on different EVM chains, thereunder:

  • Ethereum

  • Polygon

  • Shimmer

Verification Solution

Verify SBT ownership, metadata and more using REST endpoints for common use-cases or more complex ones by creating dynamic verification policies with the Open-Policy-Agent (OPA) and the REGO language.

Web2 Login

Wallet Solution

Deploy your first and start .

Start verifying SBTs or learn about dynamic verification policies with .

You can also enable Login In Web2 by launching your own decentralised identity provider that can be integrated with popular identity and access management tools like Keycloak or Auth0. Read more about it .

Extend your application with SBT viewing capabilities and web3 login using our .

SSI vs. NFTs
SBT Smart Contract
minting SBTs
here
OPA
here
wallet-kit