[Flips] Introducing Soul-Bound Token (SBT) to cadence and flow exosystem

[benbackend]

This proposal is to introduce a standard for Soul-Bound Token to the flow ecosystem. Soul-Bound Token means tokens that are Non-Fungible yet not transferrable to the others. Soul-Bound Token (SBT) should be differentiated from NFTs for long-run to faciliate easy integration of SBTs.

[vercel[bot]]

@Bamthelearner is attempting to deploy a commit to the Flow Team on Vercel.

A member of the Team first needs to authorize it.

[bluesign]

I think we need different collection for SBTs, instead of each SBT having its own collection.

So NFT contract as a template can be not the best idea.

I see different parties minting SBTs:

TSSBT, allDaySBT, FLOAT etc but I think users would like to store them in single collection.

Otherwise I can sell my TSSBT collection, and forcing soulblund can be tricky.

[joshuahannan]

Yeah, if we truly want to have a type of token that can't be transferred between accounts, then we'd have to implement some sort of central ledger, or introduce a new feature to Cadence that prevents transfers

[LanfordCai]

I have a question: How to define soul-bound in Flow/Cadence? Token can be transferred, and also, Collection can be transferred, and even the Account itself can be swapped by replacing keys.

[bluesign]

@LanfordCai I think account = identity is good starting point. I mean we can skip account swap scenario. Collection can be swapped, but we can make collection to work only when it is stored in one specific account.

[pgebheim]

Closing as abandoned