EIP-5516: Soulbound, Multi Token Standard


Co-Authored with: @MatiArazi

This is the discussion thread for EIP-5516 (Currently in Review):

This EIP proposes a standard interface for non-fungible double signature Soulbound multi-tokens. Previous account-bound token standards face the issue of users losing their account keys or having them rotated, thereby losing their tokens in the process. This EIP provides a solution to this issue that allows for the recycling of SBTs.

This EIP was inspired by the main characteristics of the EIP-1155 token and by articles in which benefits and potential use cases of Soulbound/Accountbound Tokens (SBTs) were presented. This design also allows for batch token transfers, saving on transaction costs. Trading of multiple tokens can be built on top of this standard and it removes the need to approve individual token contracts separately. It is also easy to describe and mix multiple fungible or non-fungible token types in a single contract.


It was great working with you @lucasgrasso on this one, feedback is appreciated!

An honor to work with you @MatiArazi.

I am refering this thread in my work of implementation and use cases for SBT. I would like to share the concept before post the thread.


Thank you!
Any doubts comment here

1 Like

How does a lost account(lost key) recycle a SBT?

The token, being compliant to the ERC-1155 Standard, has the feature of it being able to be trabsferred to multiple accounts. Taking this into consideration, you could send the SBT to a multi-sig contract, or if you can prove that you own both the lost account and your new account, the issuer may re-transfer the token. Despite this, the standard does not provide a methodology to recover the SBTs, it just gives these recommendations.