Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC-0013: Soulboud Token Standard #25

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

Conversation

kantp
Copy link
Contributor

@kantp kantp commented Feb 15, 2024

🚀 Introduction to the Innovation

Soulbound tokens are an interesting concept with a variety of potential applications. This rfc aspires to be a first step towards establishing a standard for how to create and interact with them on Mina.

🤔 Why This Is Important

Creating a standard for soublound tokens will make it easier for developers to create them, and, perhaps more importantly, ease integration for third party contracts and wallets.

💭 Seeking Your Input

Your expertise, feedback, and perspective are needed to make sure we end up with a suitable standard.

@kantp kantp requested a review from a team as a code owner February 15, 2024 14:31
@kantp kantp changed the title Kantp/soulbound tokens RFC-0013: Soulboud Token Standard Feb 15, 2024
rfc 11 and 12 were submitted while I drafted this one.
@kantp kantp marked this pull request as draft February 28, 2024 14:28
@kantp
Copy link
Contributor Author

kantp commented Feb 28, 2024

Moving this to draft for now, as we want to unify this with the other token standards that are being worked on.

@kantp kantp self-assigned this Apr 23, 2024
@mazito
Copy link

mazito commented Jul 11, 2024

I think this is really needed sooner than later.
We could use it for issuing Socialcap credentials.
Currently we are issuing them with our own contract, but would be really good to be bounded to a standard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants