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.

Sign up for GitHub

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

Jump to bottom

Update EIP-5192: Change name to "Lockable tokens" #6330

Closed
wants to merge 2 commits into from
Closed

Update EIP-5192: Change name to "Lockable tokens" #6330

wants to merge 2 commits into from

Commits on Jan 14, 2023

  1. Change name to "Lockable tokens" 

    When this standard was created, the term "Soulbound tokens" was cool and new. Many people understood that a Soulbound token is "bound to a soul" and so it is a permanently locked token of an account. But since then, it has become clear that a Soulbound token is an umbrella term for all kinds of tokens that break conventional norms around private property assumptions. And besides, EIP-5192 implements dynamic locking of a token. So "Lockable Tokens" is a much better term for this specification and also for developers arriving at it in the future.

I'm hence asking the EIP editors to make an exception regarding changing the contents of this EIP. The interface has not changed. Developers can still rely on using this token standard. The only change is an improvement in terms of accuracy in identifying what it is: A lockable token.
    @TimDaub
    TimDaub committed Jan 14, 2023
    Copy the full SHA
    2ddef53 View commit details
    Browse the repository at this point in the history

  2. Replace SBT term

    @TimDaub
    TimDaub committed Jan 14, 2023
    Copy the full SHA
    43eb8eb View commit details
    Browse the repository at this point in the history