Guard of NFT/SBT, an Extension of ERC-721

The five-minute read

One action, walked through

1. Open ERC 6147 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: It separates the holding right and transfer right of non-fungible tokens (NFTs) and Soulbound Tokens (SBTs) and defines a new role, guard with expires.
3. Name the object that changes: NFT, SBT.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing ERC 6147 at the status the text itself states: Final.
• The object that has to change is NFT, SBT. A neighbouring document with a similar name is not this one.
• A token standard does not collateralise itself.

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• Who loses money if the assumption in Guard of NFT/SBT, an Extension of ERC-721 is wrong?
• Is redemption specified, or only a transfer function?
• Which terms are actually defined: NFT, SBT?

Terms

ERC 6147

The public text titled Guard of NFT/SBT, an Extension of ERC-721.

Final

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

A claim that something is a dollar, a loan, or a vault is a claim about who is paid when the price moves. The interface is not that claim.

What the design proposes

• It separates the holding right and transfer right of non-fungible tokens (NFTs) and Soulbound Tokens (SBTs) and defines a new role, guard with expires.
• The flexibility of the guard setting enables the design of NFT anti-theft, NFT lending, NFT leasing, SBT, etc.
• NFTs are assets that possess both use and financial value.

How the mechanism is specified

• Taken from the specification, the next constraint is: The flexibility of the guard setting enables the design of NFT anti-theft, NFT lending, NFT leasing, SBT, etc.
• Locate NFT, SBT in ERC 6147 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• Nothing on this page is a yield, a redemption promise, or an offer of credit.
• A token standard does not collateralise itself.
• The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use ERC 6147 when a pitch says 'Guard of NFT/SBT, an Extension of ERC-721' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.