Soulbound token

On this page 7

A soulbound token (SBT) is a non-transferable token that is permanently bound to a single blockchain address, so it can record a credential, membership or attestation about its holder but cannot be sold, traded or given away. Within Tokenization & NFTs, it inverts the usual logic of a token: instead of representing a transferable asset, it represents a fact about an identity.

The idea was popularized in a 2022 paper on a decentralized society, which borrowed the name from soulbound items in online games that stay with the character who earned them. In Crypto & blockchain practice, the term now covers any token whose contract blocks or restricts transfers after minting, whether it follows a dedicated standard or simply disables the transfer functions of an ordinary NFT contract.

How a soulbound token blocks transfers

A soulbound token is enforced entirely by smart contract logic: the contract mints a token to a recipient address and then reverts every attempt to transfer it. In an ERC-721 implementation this usually means overriding the internal transfer hook so that any movement other than minting or burning fails.

Because the blockchain itself has no concept of identity, the binding is to a wallet address, not a person. The token proves that a specific key holder received it from a specific issuer address, and the value of that proof depends on how much a verifier trusts the issuer and how strongly the address is tied to a real holder.

Several community proposals describe the mechanism in standardized form. The table below summarizes the most cited ones and the design choice each makes.

ProposalCore ideaNotable feature
EIP-5192Minimal interface signaling that a token is lockedA locked function and lock events for wallets
EIP-4973Account-bound tokens with consentIssuer and recipient both sign the issuance
EIP-5484Burn authorization fixed at mintDefines who may revoke: issuer, holder, both or neither
ERC-5114Badge bound to another NFTToken is attached to an NFT rather than an address
Standards and proposals for non-transferable tokens

None of these proposals has become as universal as ERC-721 or ERC-1155, so wallets and marketplaces still detect soulbound behavior inconsistently. Many deployed SBTs are ordinary NFT contracts with transfers disabled, which works on chain but may display misleading “list for sale” options in user interfaces.

Typical uses of soulbound tokens

Soulbound tokens suit any record whose meaning would be destroyed by a sale: a diploma, an attendance proof or a governance credential is worthless as evidence if anyone can buy it. The common use cases fall into a few groups, each with its own issuer and verifier.

Use caseTypical issuerWhat the token proves
Event attendanceConference or community organizerThe address was present or registered
Educational credentialsCourse provider or universityCompletion of a program or exam
DAO membership and rolesGovernance contract or multisigVoting rights or a contributor role
KYC attestationRegulated identity providerThe holder passed verification, without the personal data
Reputation and reviewsProtocol or platformRepayment history, contributions or audits completed
Sybil resistanceProof-of-personhood serviceOne address corresponds to one unique human
Common soulbound token use cases

In decentralized finance, researchers have proposed SBTs as a basis for undercollateralized lending, where a borrower’s on-chain record of repaid loans substitutes for part of the collateral. This remains largely experimental, because a reputation token does not by itself give a lender any legal recourse after a default.

Soulbound tokens compared with NFTs and other credentials

A soulbound token is technically an NFT with one property removed: transferability. That single change moves it from the world of collectibles and tradable assets into the world of identity and credentials, where it competes with off-chain approaches such as verifiable credentials.

PropertySoulbound tokenStandard NFTVerifiable credential
TransferableNoYesNot applicable
Secondary marketNoneActive, with possible royaltiesNone
Storage locationPublic blockchainPublic blockchainHolder’s wallet, usually off chain
Privacy by defaultLow, publicly visibleLow, publicly visibleHigh, selective disclosure
RevocationDepends on contract designRarely built inStatus lists maintained by issuer
Main purposeIdentity, reputation, accessOwnership of a unique assetPortable verified claims
Comparison with related token and credential types

Soulbound tokens also differ from security tokens and utility tokens in the same Topic. Those represent economic rights or access that holders expect to trade, while an SBT has no market price by design. This is why SBTs are rarely discussed as investments and almost always discussed as infrastructure for trust.

Designing a soulbound token system

A practical soulbound token design must answer four questions before minting: who may issue, what data goes on chain, who may revoke, and how a holder recovers after losing a key. Each answer creates a trade-off between permanence, privacy and usability.

Design decisionRecommended approachReason
Personal dataStore only a hash or reference on chainPublic ledgers cannot erase data later
Revocation rightsDefine burn authority at mintExpired or fraudulent credentials must be removable
Key loss recoveryAllow issuer reissue or social recoveryA locked token cannot follow the holder to a new wallet
ConsentRequire recipient acceptancePrevents unwanted or defamatory tokens
Wallet signalingImplement the EIP-5192 lock interfaceInterfaces can hide misleading sale options
Key design decisions and recommended approaches

The safest architecture keeps sensitive claims off chain and uses the token only as a pointer or proof. Zero-knowledge proofs can then let a holder demonstrate a property, such as being over a certain age, without revealing the underlying record.

Limitations, risks and misconceptions

The strongest criticism of soulbound tokens is that non-transferability is weaker than it looks. A holder can sell the private key, or the entire wallet, together with every SBT it contains, so the token proves control of a key rather than the identity of a human.

  • Permanent public exposure: negative or sensitive tokens, such as a default record, follow an address indefinitely and may conflict with privacy law such as the GDPR right to erasure.
  • Unsolicited tokens: without consent mechanisms, anyone can mint a token to any address, including spam or reputational attacks.
  • Issuer trust: an SBT is only as credible as its issuer, and the chain cannot verify that an issuer is legitimate.
  • Lost keys: if the wallet is lost, the holder loses every credential unless the issuer supports reissue or recovery.
  • Misconception of anonymity: linking many SBTs to one address builds a detailed on-chain profile that analytics firms can read.

For these reasons, many practitioners treat soulbound tokens as suitable for low-sensitivity, positive credentials such as attendance or contribution badges, and prefer verifiable credentials with selective disclosure for regulated identity data.

A non-technical view

Most tokens on a blockchain work like money or collectibles: you can hand them to someone else or sell them. A soulbound token is different. It works more like a name badge sewn onto a jacket that only you wear. It says something about you, such as that you finished a course or belong to a group, and it cannot be passed on.

The point is trust. If a certificate could be sold, owning it would prove nothing. Because a soulbound token stays in one digital wallet, others can see who gave it and to whom. The weak spot is that the wallet, not the person, is what holds it, and anything placed on a public blockchain is visible to everyone for a very long time.

A concrete example

A developer community runs a twelve-week smart contract security course for about 300 participants each year. Instead of emailing PDF certificates, which are easy to forge, it mints a soulbound token to each graduate’s wallet when they pass the final audit exercise. The contract disables transfers, implements the EIP-5192 lock signal, and gives the community a burn right in case a certificate was obtained through plagiarism.

The token stores no names or grades on chain, only a hash of the certificate record and the cohort number. When a graduate applies to an audit firm, the firm checks that the token sits in the applicant’s wallet and that it was issued by the community’s known address, then asks the applicant to sign a message with the same wallet. Verification takes minutes instead of an email exchange, and when one graduate later loses a wallet, the community revokes the old token and reissues it to the new address after confirming identity off chain.