SBTs are non-transferable digital tokens containing information about a person or entity.
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 SSI vs. NFTs
Nonetheless, the SBTs offer great utility for many different use-cases, like reputation building and more.
Leveraging the walt.id open-source products, you can mint and verify SBTs and create wallet solutions where users can view their digital tokens.
Deploy SBT smart contracts directly via Java, Kotlin or our REST interface on different EVM chains, thereunder:
Ethereum
Polygon
Shimmer
Deploy your first SBT Smart Contract and start minting SBTs.
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.
Start verifying SBTs here or learn about dynamic verification policies with OPA.
Web2 Login
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 here.
Wallet Solution
Extend your application with SBT viewing capabilities and web3 login using our wallet-kit.