Add ERC: Privileged Non-Fungible Tokens Tied To RWA

[frankmint2024]

This EIP defines an interface to carry a real world asset with some privileges that can be exercised by the holder of the corresponding NFT. The EIP standardizes the interface for non-fungible tokens representing real world assets with privileges to be exercised, such as products sold onchain which can be redeemed in the real world.

[eip-review-bot]

File ERCS/erc-7765.md

Requires 1 more reviewers from @axic, @g11tech, @SamWilsn, @xinbenlv

[SamWilsn]

I don't think anything in your proposal is specific to RWAs, so you can drop that from your title and description. It's also possible that I just missed something, so feel free to disagree 🤣

Suggested change

	title: Privileged Non-Fungible Tokens Tied To RWA
	description: An interface extending ERC-721 representing real world assets that users can exercise privileges with NFTs.
	title: Non-Fungible Tokens with Privileges (NFTP)
	description: Extending ERC-721 with privileges exercisable by the token owner.

[frankmint2024]

This standard is designed specifically for RWA NFT. We are going to keep no change for the title. Thanks for your suggestion. You can look at rare.shop to meet the first use case for ERC-7765.

[SamWilsn]

I'd like to see a succinct definition of a "privilege" in your abstract. You already have an example, which is good, but I think adding that definition would make your abstract great.

[frankmint2024]

I have added the specific definition of the "privilege" in the newest commit.

[SamWilsn]

Suggested change

	1. The function `exercisePrivilege` performs the exercise action to a specific privilege of a token. If succeeds, it is expected to emit a PrivilegeExercised event. With this event emitted onchain, we can determine that the user has confirmed the exercise of this privilege, so as to implement the privilege in the real world.
	1. The function `exercisePrivilege` performs the exercise action to a specific privilege of a token. If succeeds, it is expected to emit a `PrivilegeExercised` event. With this event emitted onchain, we can determine that the user has confirmed the exercise of this privilege, so as to implement the privilege in the real world.

[frankmint2024]

Updated in the newest commit.

[SamWilsn]

The function exercisePrivilege performs the exercise action to a specific privilege of a token. If succeeds, it is expected to emit a PrivilegeExercised event.

This text is describing the behaviour of the exercisePrivilege function, and so belongs in the Specification section.

The latter half of this point is perfect to keep in the Rationale.

[frankmint2024]

Updated in the newest commit.

[SamWilsn]

Similarly, these points are describing behaviour. They should be in the Specification section.

[frankmint2024]

Updated in the newest commit.

[SamWilsn]

Suggested change

	5. The function `getPrivilegeIds` provides a way to manage the binding relationship between NFTs and privilegeIds.
	6. EIP-7765Metadata provides specifications for obtaining metadata information of privileges. A contract that implements EIP-7765Metadata **SHALL** also implement EIP-7765.
	6. `IERC7765Metadata` provides specifications for obtaining metadata information of privileges. A contract that implements `IERC7765Metadata` **SHALL** also implement `IERC7765`.

Is this perhaps what you mean?

[frankmint2024]

Updated in the newest commit.

[SamWilsn]

Suggested change

	This standard is an extension of ERC-721. It is fully compatible with both of the commonly used optional extensions (ERC-721Metadata and ERC-721Enumerable) mentioned in the ERC-721 standard.
	This standard is an extension of ERC-721. It is fully compatible with both of the commonly used optional extensions (`IERC721Metadata` and `IERC721Enumerable`) mentioned in the ERC-721 standard.

[frankmint2024]

Updated in the newest commit.

[SamWilsn]

This is still an external link even though you don't use a URL. Please either put a copy of your reference implementation in the assets/ directory or remove this section. We accept most open source non-copyleft licenses.

[frankmint2024]

I have added the reference implementation contracts in the assets/ directory and link to it in the proposal.
But the HTMLProofer check shows this strange error, and i can't find the eip-7765.html. what should i do here ?

[github-actions]

The commit f0d4a82 (as a parent of 7d756f1) contains errors.
Please inspect the Run Summary for details.