ERC-6147: Semi-Mandatory NFT Property Separation New Standard

On March 7, 2023, the EIP-6147 proposal officially entered the final version (Final) stage. This standard is an extension of ERC-721, aimed at separating the ownership and transfer rights of NFTs and SBTs, and introduces a new "Guardian" (Guard) role. This innovation makes applications such as anti-theft, lending, leasing, and SBTs for NFTs more flexible.

Background

One of the main challenges of NFTs is insufficient liquidity. This issue arises not only from the NFT protocols themselves but more importantly from how to provide NFTs with actual use value, rather than relying solely on market operations. The main problems currently faced by NFTs include:

1. Property coupling: High-value NFTs tend to seek safe havens, but existing anti-theft solutions often affect the usability of NFTs.

2. When lending an NFT, the owner needs to transfer the ownership of the NFT and loses the right to use it.

3. SBT( Soulbound Token ) is bound to an Ethereum address, and when the user loses their private key, recovering the SBT becomes very complicated.

The Operating Mechanism of ERC-6147

Guard character

ERC-6147 defines a role named Guard(, similar to UserInfo in ERC-4907:

solidity struct GuardInfo { address guard; // Guardian address uint64 expires; // Expiration time }

Only the current owner of the NFT or an authorized address can set the Guard. The setting of the Guard has the following restrictions:

• Guard cannot be set to the 0 address
• Only the Guard can modify themselves.
• Only NFT owners or authorized persons can set the Guard.

The identity of the Guard can only be removed by the Guard themselves or automatically upon expiration.

![Interpretation of the latest Final ERC-6147: A minimalist semi-mandatory NFT property separation standard])https://img-cdn.gateio.im/webp-social/moments-defb8f4e51869ee996ce467b7fde5ea0.webp(

) Guard's permissions

1. Forced Transfer Rights: For NFTs with a Guard set, only the guard address can perform transfer operations.

2. The original holder only retains the right of possession and loses the right of transfer ### and the right of use (.

3. Other Dapps can still query the original owner of the NFT, but the original owner cannot execute the transfer.

4. The signature on the trading platform is valid, but ) cannot be actually transferred because protocols like Seaport require withholding authorization for the transfer of (.

5. The Guard can use the transferAndRemove method to clear the guardian information after the transfer.

6. The Guard can transfer the guard authority through the changeGuard method.

) Guard's restrictions

1. Guard cannot set up withholding authorization.

2. The Guard cannot set Approve to prevent the transfer of the NFT through approve after the transfer of rights has been returned.

![Interpretation of the latest Final ERC-6147: A minimalist semi-mandatory NFT property separation standard]###https://img-cdn.gateio.im/webp-social/moments-8e992e191f2263857a2c65baade8a108.webp(

Advantages of ERC-6147

1. Compatibility Optimization: Compared to ERC-4907, ERC-6147 does not require the project to actively acknowledge new roles, only the owner needs to be acknowledged. This makes it easier to adapt to the existing application ecosystem.

2. Introduce the concepts of "manageable SBT" and "effective SBT": this addresses the problem that the existing SBT design overly emphasizes the "non-transferable" characteristic while neglecting potential management scenarios such as social recovery, reclaiming SBT, etc.

3. Flexibility: Applicable to various scenarios, such as NFT anti-theft, leasing, SBT social recovery, etc.

The emergence of ERC-6147 provides more possibilities for the application of NFT and SBT, and is expected to promote the NFT ecosystem towards a more mature and diversified direction.

![Interpretation of the latest Final ERC-6147: A minimalist semi-mandatory NFT property separation standard])https://img-cdn.gateio.im/webp-social/moments-bfff8d0061eaaf89e711e7ade2cf99a6.webp(