-
Notifications
You must be signed in to change notification settings - Fork 462
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
4a5fcc8
commit 33232b0
Showing
1 changed file
with
6 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| --- | ||
| erc: 5521 | ||
| eip: 5521 | ||
| title: Referable NFT | ||
| description: An ERC-721 extension to construct reference relationships among NFTs | ||
| author: Saber Yu (@OniReimu), Qin Wang <[email protected]>, Shange Fu <[email protected]>, Yilin Sai <[email protected]>, Shiping Chen <[email protected]>, Sherry Xu <[email protected]>, Jiangshan Yu <[email protected]> | ||
|
|
@@ -13,9 +13,9 @@ requires: 165, 721 | |
|
|
||
| ## Abstract | ||
|
|
||
| This standard is an extension of [ERC-721](./erc-721.md). It proposes two referable indicators, referring and referred, and a time-based indicator `createdTimestamp`. The relationship between each NFT forms a directed acyclic graph (DAG). The standard allows users to query, track and analyze their relationships. | ||
| This standard is an extension of [ERC-721](./eip-721.md). It proposes two referable indicators, referring and referred, and a time-based indicator `createdTimestamp`. The relationship between each NFT forms a directed acyclic graph (DAG). The standard allows users to query, track and analyze their relationships. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ## Motivation | ||
|
|
||
|
|
@@ -108,17 +108,17 @@ This standard is intended to establish the referable DAG for queries on cross-re | |
|
|
||
| *Incentive Compatibility*: This standard clarifies the referable relationship across different NFTs, helping to integrate multiple up-layer incentive models for both original NFT owners and new creators. | ||
|
|
||
| *Easy Integration*: This standard makes it easier for the existing token standards or third-party protocols. For instance, the rNFT can be applied to rentable scenarios (cf. [ERC-5006](./erc-5006.md) to build a hierarchical rental market, where multiple users can rent the same NFT during the same time or one user can rent multiple NFTs during the same duration). | ||
| *Easy Integration*: This standard makes it easier for the existing token standards or third-party protocols. For instance, the rNFT can be applied to rentable scenarios (cf. [ERC-5006](./eip-5006.md) to build a hierarchical rental market, where multiple users can rent the same NFT during the same time or one user can rent multiple NFTs during the same duration). | ||
|
|
||
| *Scalable Interoperability* From March 26th 2023, this standard has been stepping forward by enabling cross-contract references, giving a scalable adoption for the broader public with stronger interoperability. | ||
|
|
||
| ## Backwards Compatibility | ||
|
|
||
| This standard can be fully [ERC-721](./erc-721.md) compatible by adding an extension function set. | ||
| This standard can be fully [ERC-721](./eip-721.md) compatible by adding an extension function set. | ||
|
|
||
| ## Test Cases | ||
|
|
||
| Test cases are included in [ERC_5521.test.js](../assets/erc-5521/ERC_5521.test.js) | ||
| Test cases are included in [ERC_5521.test.js](../assets/eip-5521/ERC_5521.test.js) | ||
|
|
||
| ## Reference Implementation | ||
|
|
||
|
|
||