An interface for soulbound tokens (SBT), which are non-transferable tokens representing a person’s identity, credentials, affiliations, and reputation.
Our interface can handle a combination of fungible and non-fungible tokens in an organized way. It provides a set of core methods that can be used to manage the lifecycle of soulbound tokens, as well as a rich set of extensions that enables DAO governance, delegation, token expiration, and account recovery.
This interface aims to provide a flexible and extensible framework for the development of soulbound token systems.
Motivation
The current Web3 ecosystem is heavily focused on financialized, transferable tokens. However, there’s a growing need for non-transferable tokens to represent unique personal attributes and rights. Existing attempts within the Ethereum community to create such tokens lack the necessary flexibility and extensibility. Our interface addresses this gap, offering a versatile and comprehensive solution for SBTs.
Our interface can be used to represent non-transferable ownerships, and provides features for common use cases including but not limited to:
Lifecycle Management: Robust tools for minting, revocation, and managing the subscription and expiration of SBTs.
DAO Governance and Delegation: Empower community-driven decisions and operational delegation for SBT management.
Account Recovery: Advanced mechanisms for account recovery and key rotation, ensuring security and continuity.
Versatility in Tokens: Support for both fungible and non-fungible SBTs, catering to a wide range of use cases like membership cards and loyalty programs.
Token Grouping: Innovative slot-based system for organizing SBTs, ideal for complex reward structures including vouchers, points, and badges.
Claimable SBTs: Streamlined distribution of SBTs for airdrops, giveaways, and referral programs.
This interface not only enriches the Web3 landscape but also paves the way for a more decentralized and personalized digital society.
Specification
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
A token is identified by its tokenId, which is a 256-bit unsigned integer. A token can also have a value denoting its denomination.
A slot is identified by its slotId, which is a 256-bit unsigned integer. Slots are used to group fungible and non-fungible tokens together, thus make tokens semi-fungible. A token can only belong to one slot at a time.
Core
The core methods are used to manage the lifecycle of SBTs. They MUST be supported by all semi-fungible SBT implementations.
/**
* @title ERC5727 Soulbound Token Interface
* @dev The core interface of the ERC5727 standard.
*/interfaceIERC5727isIERC3525,IERC5192,IERC5484,IERC4906{/**
* @dev MUST emit when a token is revoked.
* @param from The address of the owner
* @param tokenId The token id
*/eventRevoked(addressindexedfrom,uint256indexedtokenId);/**
* @dev MUST emit when a token is verified.
* @param by The address that initiated the verification
* @param tokenId The token id
* @param result The result of the verification
*/eventVerified(addressindexedby,uint256indexedtokenId,boolresult);/**
* @notice Get the verifier of a token.
* @dev MUST revert if the `tokenId` does not exist
* @param tokenId the token for which to query the verifier
* @return The address of the verifier of `tokenId`
*/functionverifierOf(uint256tokenId)externalviewreturns(address);/**
* @notice Get the issuer of a token.
* @dev MUST revert if the `tokenId` does not exist
* @param tokenId the token for which to query the issuer
* @return The address of the issuer of `tokenId`
*/functionissuerOf(uint256tokenId)externalviewreturns(address);/**
* @notice Issue a token in a specified slot to an address.
* @dev MUST revert if the `to` address is the zero address.
* MUST revert if the `verifier` address is the zero address.
* @param to The address to issue the token to
* @param tokenId The token id
* @param slot The slot to issue the token in
* @param burnAuth The burn authorization of the token
* @param verifier The address of the verifier
* @param data Additional data used to issue the token
*/functionissue(addressto,uint256tokenId,uint256slot,BurnAuthburnAuth,addressverifier,bytescalldatadata)externalpayable;/**
* @notice Issue credit to a token.
* @dev MUST revert if the `tokenId` does not exist.
* @param tokenId The token id
* @param amount The amount of the credit
* @param data The additional data used to issue the credit
*/functionissue(uint256tokenId,uint256amount,bytescalldatadata)externalpayable;/**
* @notice Revoke a token from an address.
* @dev MUST revert if the `tokenId` does not exist.
* @param tokenId The token id
* @param data The additional data used to revoke the token
*/functionrevoke(uint256tokenId,bytescalldatadata)externalpayable;/**
* @notice Revoke credit from a token.
* @dev MUST revert if the `tokenId` does not exist.
* @param tokenId The token id
* @param amount The amount of the credit
* @param data The additional data used to revoke the credit
*/functionrevoke(uint256tokenId,uint256amount,bytescalldatadata)externalpayable;/**
* @notice Verify if a token is valid.
* @dev MUST revert if the `tokenId` does not exist.
* @param tokenId The token id
* @param data The additional data used to verify the token
* @return A boolean indicating whether the token is successfully verified
*/functionverify(uint256tokenId,bytescalldatadata)externalreturns(bool);}
Extensions
All extensions below are OPTIONAL for ERC-5727 implementations. An implementation MAY choose to implement some, none, or all of them.
Enumerable
This extension provides methods to enumerate the tokens of a owner. It is recommended to be implemented together with the core interface.
/**
* @title ERC5727 Soulbound Token Enumerable Interface
* @dev This extension allows querying the tokens of a owner.
*/interfaceIERC5727EnumerableisIERC3525SlotEnumerable,IERC5727{/**
* @notice Get the number of slots of a owner.
* @param owner The owner whose number of slots is queried for
* @return The number of slots of the `owner`
*/functionslotCountOfOwner(addressowner)externalviewreturns(uint256);/**
* @notice Get the slot with `index` of the `owner`.
* @dev MUST revert if the `index` exceed the number of slots of the `owner`.
* @param owner The owner whose slot is queried for.
* @param index The index of the slot queried for
* @return The slot is queried for
*/functionslotOfOwnerByIndex(addressowner,uint256index)externalviewreturns(uint256);/**
* @notice Get the balance of a owner in a slot.
* @dev MUST revert if the slot does not exist.
* @param owner The owner whose balance is queried for
* @param slot The slot whose balance is queried for
* @return The balance of the `owner` in the `slot`
*/functionownerBalanceInSlot(addressowner,uint256slot)externalviewreturns(uint256);}
Metadata
This extension provides methods to fetch the metadata of a token, a slot and the contract itself. It is recommended to be implemented if you need to specify the appearance and properties of tokens, slots and the contract (i.e. the SBT collection).
/**
* @title ERC5727 Soulbound Token Metadata Interface
* @dev This extension allows querying the metadata of soulbound tokens.
*/interfaceIERC5727MetadataisIERC3525Metadata,IERC5727{}
Governance
This extension provides methods to manage the mint and revocation permissions through voting. It is useful if you want to rely on a group of voters to decide the issuance a particular SBT.
/**
* @title ERC5727 Soulbound Token Governance Interface
* @dev This extension allows issuing of tokens by community voting.
*/interfaceIERC5727GovernanceisIERC5727{enumApprovalStatus{Pending,Approved,Rejected,Removed}/**
* @notice Emitted when a token issuance approval is changed.
* @param approvalId The id of the approval
* @param creator The creator of the approval, zero address if the approval is removed
* @param status The status of the approval
*/eventApprovalUpdate(uint256indexedapprovalId,addressindexedcreator,ApprovalStatusstatus);/**
* @notice Emitted when a voter approves an approval.
* @param voter The voter who approves the approval
* @param approvalId The id of the approval
*/eventApprove(addressindexedvoter,uint256indexedapprovalId,boolapprove);/**
* @notice Create an approval of issuing a token.
* @dev MUST revert if the caller is not a voter.
* MUST revert if the `to` address is the zero address.
* @param to The owner which the token to mint to
* @param tokenId The id of the token to mint
* @param amount The amount of the token to mint
* @param slot The slot of the token to mint
* @param burnAuth The burn authorization of the token to mint
* @param data The additional data used to mint the token
*/functionrequestApproval(addressto,uint256tokenId,uint256amount,uint256slot,BurnAuthburnAuth,addressverifier,bytescalldatadata)external;/**
* @notice Remove `approvalId` approval request.
* @dev MUST revert if the caller is not the creator of the approval request.
* MUST revert if the approval request is already approved or rejected or non-existent.
* @param approvalId The approval to remove
*/functionremoveApprovalRequest(uint256approvalId)external;/**
* @notice Approve `approvalId` approval request.
* @dev MUST revert if the caller is not a voter.
* MUST revert if the approval request is already approved or rejected or non-existent.
* @param approvalId The approval to approve
* @param approve True if the approval is approved, false if the approval is rejected
* @param data The additional data used to approve the approval (e.g. the signature, voting power)
*/functionvoteApproval(uint256approvalId,boolapprove,bytescalldatadata)external;/**
* @notice Get the URI of the approval.
* @dev MUST revert if the `approvalId` does not exist.
* @param approvalId The approval whose URI is queried for
* @return The URI of the approval
*/functionapprovalURI(uint256approvalId)externalviewreturns(stringmemory);}
Delegate
This extension provides methods to delegate (undelegate) mint right in a slot to (from) an operator. It is useful if you want to allow an operator to mint tokens in a specific slot on your behalf.
/**
* @title ERC5727 Soulbound Token Delegate Interface
* @dev This extension allows delegation of issuing and revocation of tokens to an operator.
*/interfaceIERC5727DelegateisIERC5727{/**
* @notice Emitted when a token issuance is delegated to an operator.
* @param operator The owner to which the issuing right is delegated
* @param slot The slot to issue the token in
*/eventDelegate(addressindexedoperator,uint256indexedslot);/**
* @notice Emitted when a token issuance is revoked from an operator.
* @param operator The owner to which the issuing right is delegated
* @param slot The slot to issue the token in
*/eventUnDelegate(addressindexedoperator,uint256indexedslot);/**
* @notice Delegate rights to `operator` for a slot.
* @dev MUST revert if the caller does not have the right to delegate.
* MUST revert if the `operator` address is the zero address.
* MUST revert if the `slot` is not a valid slot.
* @param operator The owner to which the issuing right is delegated
* @param slot The slot to issue the token in
*/functiondelegate(addressoperator,uint256slot)external;/**
* @notice Revoke rights from `operator` for a slot.
* @dev MUST revert if the caller does not have the right to delegate.
* MUST revert if the `operator` address is the zero address.
* MUST revert if the `slot` is not a valid slot.
* @param operator The owner to which the issuing right is delegated
* @param slot The slot to issue the token in
*/functionundelegate(addressoperator,uint256slot)external;/**
* @notice Check if an operator has the permission to issue or revoke tokens in a slot.
* @param operator The operator to check
* @param slot The slot to check
*/functionisOperatorFor(addressoperator,uint256slot)externalviewreturns(bool);}
Recovery
This extension provides methods to recover tokens from a stale owner. It is recommended to use this extension so that users are able to retrieve their tokens from a compromised or old wallet in certain situations. The signing scheme SHALL be compatible with EIP-712 for readability and usability.
/**
* @title ERC5727 Soulbound Token Recovery Interface
* @dev This extension allows recovering soulbound tokens from an address provided its signature.
*/interfaceIERC5727RecoveryisIERC5727{/**
* @notice Emitted when the tokens of `owner` are recovered.
* @param from The owner whose tokens are recovered
* @param to The new owner of the tokens
*/eventRecovered(addressindexedfrom,addressindexedto);/**
* @notice Recover the tokens of `owner` with `signature`.
* @dev MUST revert if the signature is invalid.
* @param owner The owner whose tokens are recovered
* @param signature The signature signed by the `owner`
*/functionrecover(addressowner,bytesmemorysignature)external;}
Expirable
This extension provides methods to manage the expiration of tokens. It is useful if you want to expire/invalidate tokens after a certain period of time.
/**
* @title ERC5727 Soulbound Token Expirable Interface
* @dev This extension allows soulbound tokens to be expirable and renewable.
*/interfaceIERC5727ExpirableisIERC5727,IERC5643{/**
* @notice Set the expiry date of a token.
* @dev MUST revert if the `tokenId` token does not exist.
* MUST revert if the `date` is in the past.
* @param tokenId The token whose expiry date is set
* @param expiration The expire date to set
* @param isRenewable Whether the token is renewable
*/functionsetExpiration(uint256tokenId,uint64expiration,boolisRenewable)external;}
Rationale
Token storage model
We adopt semi-fungible token storage models designed to support both fungible and non-fungible tokens, inspired by the semi-fungible token standard. We found that such a model is better suited to the representation of SBT than the model used in ERC-1155.
Firstly, each slot can be used to represent different categories of SBTs. For instance, a DAO can have membership SBTs, role badges, reputations, etc. in one SBT collection.
Secondly, unlike ERC-1155, in which each unit of fungible tokens is exactly the same, our interface can help differentiate between similar tokens. This is justified by that credential scores obtained from different entities differ not only in value but also in their effects, validity periods, origins, etc. However, they still share the same slot as they all contribute to a person’s credibility, membership, etc.
Recovery mechanism
To prevent the loss of SBTs, we propose a recovery mechanism that allows users to recover their tokens by providing a signature signed by their owner address. This mechanism is inspired by ERC-1271.
Since SBTs are bound to an address and are meant to represent the identity of the address, which cannot be split into fractions. Therefore, each recovery should be considered as a transfer of all the tokens of the owner. This is why we use the recover function instead of transferFrom or safeTransferFrom.
This EIP does not involve the general transfer of tokens, and thus there will be no security issues related to token transfer generally.
However, users should be aware of the security risks of using the recovery mechanism. If a user loses his/her private key, all his/her soulbound tokens will be exposed to potential theft. The attacker can create a signature and restore all SBTs of the victim. Therefore, users should always keep their private keys safe. We recommend developers implement a recovery mechanism that requires multiple signatures to restore SBTs.