Soulbound Token (SBT)

What Is a Soulbound Token?

A soulbound token (SBT) is a type of non-fungible token that cannot be transferred once it has been issued to a wallet. The wallet that holds soulbound tokens is referred to as a "Soul." Unlike traditional NFTs that can be freely traded on marketplaces, SBTs are permanently bound to the receiving address, making them suitable for representing things that should be earned or verified rather than purchased.

The concept draws its name from "soulbound" items in the video game World of Warcraft: gear that binds to a player's character upon pickup and cannot be traded to others. Vitalik Buterin, along with economist E. Glen Weyl and lawyer Puja Ohlhaver, formalized this idea for blockchain in their May 2022 paper "Decentralized Society: Finding Web3's Soul." The paper argues that Web3 lacks primitives for representing social identity, trust, and reputation: things that inherently should not be transferable.

By anchoring non-transferable credentials to wallets, SBTs introduce a reputation layer to blockchain ecosystems. A wallet accumulating SBTs from universities, employers, community organizations, and financial institutions builds a verifiable on-chain identity without relying on centralized identity providers.

How It Works

Soulbound tokens are built on existing token standards with a critical modification: the transfer function is disabled. When someone attempts to transfer an SBT, the transaction reverts. The token remains locked to the wallet that originally received it.

The issuance process typically involves two parties: an issuer (a university, employer, or protocol) and a recipient (the wallet owner). Depending on the implementation, issuance may require consent from both parties, ensuring that unwanted tokens cannot be forced onto a wallet.

1. An issuer (institution, protocol, or individual) creates an SBT smart contract defining the credential type and metadata
2. The recipient provides their wallet address and, in some standards, signs a message consenting to receive the token
3. The contract mints the SBT to the recipient's address with transfer functions disabled
4. The SBT remains permanently at that address: it can be verified by anyone but moved by no one

Technical Standards

Several Ethereum standards define how soulbound tokens work at the contract level. Each takes a slightly different approach to non-transferability:

ERC-5192 is the most widely adopted standard due to its simplicity. It extends the familiar ERC-721 NFT interface with a single function that signals whether a token is locked:

// ERC-5192: Minimal Soulbound NFT Interface
interface IERC5192 {
    // Emitted when a token is locked (becomes soulbound)
    event Locked(uint256 tokenId);

    // Emitted when a token is unlocked
    event Unlocked(uint256 tokenId);

    // Returns true if the token is non-transferable
    function locked(uint256 tokenId) external view returns (bool);
}

When locked() returns true, any call to transferFrom() or safeTransferFrom() must revert. Wallets and marketplaces can query this function to determine whether a token can be listed for sale or transferred, preventing accidental attempts at trading soulbound items.

Issuance and Revocation

Different standards handle issuance and revocation differently. ERC-4973 uses a two-party consent model with give() and take() functions that require cryptographic signatures from both issuer and recipient. EIP-5484 introduces burn authorization: predetermined rules specifying who can destroy an SBT (issuer only, holder only, both, or neither).

Revocation is important for credentials that can expire or be rescinded. A university might revoke a degree SBT if fraud is discovered. A professional certification body might burn an SBT when a license lapses. The holder should also have the ability to remove unwanted tokens from their wallet, particularly given privacy concerns around permanently visible on-chain data.

Use Cases

Credentials and Certifications

Academic institutions can issue SBTs representing diplomas, degrees, and professional certifications. Unlike paper credentials that can be forged, an SBT is cryptographically verifiable: anyone can confirm it was issued by the institution's official contract address. This reduces the cost and friction of credential verification while making fraud significantly harder.

Professional certifications (medical licenses, engineering credentials, financial advisor registrations) can be represented as SBTs with built-in expiration logic. When a license lapses, the issuing body can revoke the SBT, ensuring that on-chain credential status always reflects reality.

KYC and Identity Attestations

Exchanges and financial institutions can issue SBTs attesting that a wallet owner has completed KYC verification. Other protocols can then check for the presence of a KYC SBT rather than requiring users to re-verify their identity at every new service. Binance pioneered this approach with its Account Bound (BAB) token, issued to users who have completed KYC on the exchange. Projects use BAB tokens to restrict airdrops, NFT mints, and DAO voting to verified individuals, providing a measure of Sybil resistance.

DAO Governance

Traditional DAO governance relies on governance tokens, which can be purchased by anyone with enough capital. This creates plutocratic dynamics where wealthy participants can buy outsized voting power. SBTs offer an alternative: non-transferable voting credentials issued based on participation, contribution, or reputation rather than financial investment.

A DAO could issue SBTs to members who have contributed code, written proposals, or participated in governance for a minimum period. These SBTs grant voting weight that cannot be bought or delegated to a whale. Projects like Otterspace (built on ERC-4973) enable DAOs to mint non-transferable badges for roles and achievements that inform incentive systems and permissions.

Reputation-Based Lending

One of the most ambitious applications of SBTs is enabling under-collateralized lending in DeFi. Today, DeFi lending protocols require overcollateralization because blockchain addresses reveal little about the borrower's creditworthiness. There is no on-chain equivalent of a credit score.

SBTs could change this. If a wallet accumulates credible attestations from educational institutions, employers, previous lenders, and community organizations, lending protocols could use these SBTs to assess creditworthiness without a centralized credit bureau. A borrower's repayment history from previous loans could itself be represented as SBTs, creating a decentralized credit record.

This remains an active research area. The reliability of SBT-based credit scoring depends on the trustworthiness of issuers, defenses against gaming, and the maturity of the broader identity ecosystem.

Community Recovery

The original DeSoc paper proposes using SBTs for social recovery of wallets. A Soul's SBTs represent its social graph: affiliations with communities, institutions, and individuals. If a user loses access to their wallet, recovery could require attestations from a qualified majority of the Soul's SBT issuers, similar to social recovery wallets but with the recovery set determined by verifiable on-chain relationships.

Privacy Concerns and Solutions

The most significant challenge facing soulbound tokens is privacy. Because SBTs are on-chain, anyone can inspect a wallet's credentials, affiliations, and history. This visibility could expose sensitive information: employment records, medical certifications, political affiliations, or financial history. Chain analysis firms could correlate SBT-holding wallets with transaction patterns, potentially de-anonymizing users.

The permanence of blockchain data compounds this concern. A credential issued years ago might reveal information the holder no longer wishes to be public. Unlike traditional databases where records can be deleted, on-chain SBTs persist indefinitely unless the contract includes a burn mechanism.

Selective Disclosure with Zero-Knowledge Proofs

Zero-knowledge proofs (ZKPs) offer the most promising solution to SBT privacy. With ZKPs, a holder can prove they possess a specific credential without revealing the credential itself. For example, a user could prove they hold a valid medical license without disclosing which state issued it, or prove they are over 21 without revealing their exact date of birth.

Projects like Sismo Protocol have implemented this approach, issuing non-transferable "ZK Badges" that allow users to selectively disclose personal data to applications. The proof is public but the underlying data remains private: a pattern that preserves the verifiability benefits of SBTs while addressing the surveillance risks of fully transparent on-chain credentials. For a deeper look at how zero-knowledge proofs work, see the ZKP applications research article.

Why It Matters

Soulbound tokens address a fundamental gap in blockchain ecosystems: the absence of non-financial identity. Today, wallets are essentially anonymous containers for transferable assets. There is no native way to represent who someone is, what they have accomplished, or why they should be trusted: only what they own.

This identity gap limits what can be built on-chain. Without verifiable reputation, DeFi must rely on overcollateralization. Without non-transferable membership, DAOs default to plutocratic governance. Without portable credentials, users re-verify their identity at every new service. SBTs provide a primitive for encoding these social relationships on-chain, opening new design spaces for protocols and applications.

For Bitcoin-native ecosystems like Spark, the principles behind SBTs are relevant even outside Ethereum. As layer-2 networks expand the capabilities of Bitcoin, identity and reputation primitives will become increasingly important for enabling trust-minimized interactions in stablecoin payments, lending, and decentralized applications.

Risks and Considerations

Wallet Loss and Key Management

If a user loses access to their wallet, they lose all associated SBTs: their credentials, memberships, and reputation. Unlike transferable tokens that can be recovered by moving them to a new address before losing access, SBTs are permanently bound. This makes robust key management and wallet recovery mechanisms especially critical for SBT holders.

Unwanted Tokens and Spam

Without consent mechanisms, malicious actors could mint unwanted SBTs to a wallet: effectively tagging someone with undesirable labels that cannot be removed. Standards like EIP-5484 address this by requiring mutual consent before issuance and defining burn authorization rules, but not all implementations enforce these safeguards.

Standardization Fragmentation

Multiple competing standards (ERC-5192, ERC-4973, EIP-5484, ERC-6239) create interoperability challenges. An SBT issued under one standard may not be recognized by platforms expecting another. This fragmentation complicates the vision of a unified, portable on-chain identity. The ecosystem is still converging on which approaches will become dominant.

Issuer Trust and Centralization

SBTs are only as trustworthy as their issuers. A fraudulent institution could issue fake credentials, and verifiers must decide which issuers to trust. This reintroduces a form of centralization: someone must curate lists of trusted issuers, creating gatekeepers in a system designed to be decentralized. Reputation systems for issuers themselves remain an unsolved problem.

Regulatory Uncertainty

The legal status of on-chain credentials is unclear in most jurisdictions. Whether an SBT-based KYC attestation satisfies regulatory requirements varies by country and context. While some jurisdictions like Curaçao have begun formally recognizing blockchain-based identity attestations (as of April 2026 for gaming regulation), broad regulatory acceptance remains limited.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.