Add EIP: NFT Dynamic Ownership #7158
Conversation
github-actions
bot
added
c-new
File
|
eth-bot
added
e-consensus
Co-authored-by: Andrew B Coathup <[email protected]>
hiddenintheworld
force-pushed
the
EIP-7110
branch
from
c538f24
to
6c01dbc
Compare
| --- | ||
| eip: 7110 | ||
| title: NFT Dynamic Ownership | ||
| description: An innovative extension to NFT token that introduces dynamic ownership and nesting capabilities. |
There was a problem hiding this comment.
| description: An innovative extension to NFT token that introduces dynamic ownership and nesting capabilities. | |
| description: An extension to non-fungible tokens that introduces dynamic ownership and nesting capabilities. |
|
|
||
| ## Abstract | ||
|
|
||
| A standard interface for non-fungible tokens (NFTs) with dynamic ownership, which extends the capabilities of the original `ERC-721` standard by enabling NFTs to be owned by either addresses or other NFTs. The proposed `ERC-721D` standard introduces dynamic ownership in the world of NFTs. Instead of a token being owned solely by an address, as it is in the `ERC-721` standard, tokens following the `ERC-721D` standard can be owned by either an address or another token. This opens up new possibilities and adds an extra layer of complexity and opportunity in the NFT space. This EIP outlines the rules and functions needed to support this dynamic ownership model while maintaining compatibility with `ERC-721` standards. |
There was a problem hiding this comment.
When you're referring to another proposal, don't enclose it in backticks. You have to use a link the first time (per proposal), but after that you can just reference the proposal as normal.
When referring to your interfaces, however, you should use backticks.
| A standard interface for non-fungible tokens (NFTs) with dynamic ownership, which extends the capabilities of the original `ERC-721` standard by enabling NFTs to be owned by either addresses or other NFTs. The proposed `ERC-721D` standard introduces dynamic ownership in the world of NFTs. Instead of a token being owned solely by an address, as it is in the `ERC-721` standard, tokens following the `ERC-721D` standard can be owned by either an address or another token. This opens up new possibilities and adds an extra layer of complexity and opportunity in the NFT space. This EIP outlines the rules and functions needed to support this dynamic ownership model while maintaining compatibility with `ERC-721` standards. | |
| A standard interface for non-fungible tokens (NFTs) with dynamic ownership, which extends the capabilities of the original [ERC-721](./eip-721.md) standard by enabling NFTs to be owned by either addresses or other NFTs. The proposed `ERC721D` interface introduces dynamic ownership in the world of NFTs. Instead of a token being owned solely by an address, as it is in the ERC-721 standard, tokens following the `ERC721D` interface can be owned by either an address or another token. This opens up new possibilities and adds an extra layer of complexity and opportunity in the NFT space. This EIP outlines the rules and functions needed to support this dynamic ownership model while maintaining compatibility with ERC-721 standards. |
|
|
||
| ## Abstract | ||
|
|
||
| A standard interface for non-fungible tokens (NFTs) with dynamic ownership, which extends the capabilities of the original `ERC-721` standard by enabling NFTs to be owned by either addresses or other NFTs. The proposed `ERC-721D` standard introduces dynamic ownership in the world of NFTs. Instead of a token being owned solely by an address, as it is in the `ERC-721` standard, tokens following the `ERC-721D` standard can be owned by either an address or another token. This opens up new possibilities and adds an extra layer of complexity and opportunity in the NFT space. This EIP outlines the rules and functions needed to support this dynamic ownership model while maintaining compatibility with `ERC-721` standards. |
There was a problem hiding this comment.
I think you can probably cut a bit from your abstract and move it into motivation. The abstract should be a terse technical summary of the proposal that gives the reader a general idea of how the proposal works.
|
|
||
| ## Motivation | ||
|
|
||
| Non-fungible tokens (NFTs) have paved the way for unique digital assets. However, they are inherently restricted by their static ownership. `ERC-721D` aims to innovate the concept of NFT ownership by allowing tokens to have dynamic ownership chains. This could unlock an entirely new dimension for tokenized digital assets and decentralized applications (dApps). |
There was a problem hiding this comment.
| Non-fungible tokens (NFTs) have paved the way for unique digital assets. However, they are inherently restricted by their static ownership. `ERC-721D` aims to innovate the concept of NFT ownership by allowing tokens to have dynamic ownership chains. This could unlock an entirely new dimension for tokenized digital assets and decentralized applications (dApps). | |
| NFTs have paved the way for unique digital assets. However, they are inherently restricted by their static ownership. `ERC721D` aims to innovate the concept of NFT ownership by allowing tokens to have dynamic ownership chains. This could unlock an entirely new dimension for tokenized digital assets and decentralized applications (dApps). |
|
|
||
| ### Overview | ||
|
|
||
| `ERC-721D` is a standard interface for NFTs with dynamic ownership. It provides essential functionalities to manage, transfer, and track the ownership of tokens. It is an extension of the `ERC-721` standard. |
There was a problem hiding this comment.
| `ERC-721D` is a standard interface for NFTs with dynamic ownership. It provides essential functionalities to manage, transfer, and track the ownership of tokens. It is an extension of the `ERC-721` standard. | |
| `ERC721D` is a standard interface for NFTs with dynamic ownership. It provides essential functionalities to manage, transfer, and track the ownership of tokens. It is an extension of the ERC-721 standard. |
|
|
||
|
|
||
| ```solidity | ||
| // SPDX-License-Identifier: MIT |
There was a problem hiding this comment.
Code contained within the EIP itself must be CC0-1.0 licensed. Code in the assets/ directory may have other open source licenses that don't impose too much of implementers. MIT would be fine there.
|
|
||
| The `ERC-721D` standard defines a set of functions for interacting with tokens. It includes existing functions from the `ERC-721` standard, like **```balanceOf```** and **```ownerOf```**, with necessary modifications to support dynamic ownership. It also introduces new functions like **```setOwnership```** to manage dynamic ownership. The **```mint```** and **```burn```** functions have been overridden to account for changes in the balance of dynamic owners. The **```_transfer```** function has been updated to handle transfers involving dynamic owners. | ||
|
|
||
| ### Implementation |
There was a problem hiding this comment.
Please move any implementations to the reference implementation section. The specification section should only really contain an interface.
|
|
||
| ## Rationale | ||
|
|
||
| The `ERC-721D` standard seeks to expand the potential of NFTs by introducing dynamic ownership. This innovation could open up new use cases in the fields of digital assets, dApps, digital identity, and more. As the digital economy evolves, the need for complex and dynamic relationships between tokens will become increasingly relevant, and the `ERC-721D` standard addresses this need. |
There was a problem hiding this comment.
This reads more like motivation. The Rationale section should justify technical choices made within the EIP itself, while the Motivation section justifies the EIP as a whole.
An example of something you may want to explain in the Rationale section is why you chose EIP-721 as the base of your extension and not EIP-1155.
|
|
||
| ## Backwards Compatibility | ||
|
|
||
| `ERC-721D` is fully backward compatible with the `ERC-721` standard. It extends the `ERC-721` standard by adding dynamic ownership while maintaining all existing functionalities. Any existing `ERC-721` token can be upgraded to an `ERC-721D` token while retaining its original capabilities. |
There was a problem hiding this comment.
| `ERC-721D` is fully backward compatible with the `ERC-721` standard. It extends the `ERC-721` standard by adding dynamic ownership while maintaining all existing functionalities. Any existing `ERC-721` token can be upgraded to an `ERC-721D` token while retaining its original capabilities. | |
| `ERC721D` is fully backward compatible with the ERC-721 standard. It extends ERC-721 by adding dynamic ownership while maintaining all existing functionalities. Any existing ERC-721 token can be upgraded to an `ERC721D` token while retaining its original capabilities. |
| ### Data Structures | ||
|
|
||
| The `ERC-721D` standard introduces a new data structure, **```Ownership```**. Each token has an **```Ownership```** associated with it that consists of the **```ownerAddress```** and the **```tokenId```**. The **```ownerAddress```** is the address of the token owner, which can be an EOA or a contract address. If the owner is another NFT, then tokenId represents the ID of the owner token. | ||
|
|
There was a problem hiding this comment.
Your specification section doesn't include enough detail to be implementable. You'll need more in-depth explanations of the changes to, for example, ownerOf so that someone reading your standard can make those changes.
|
I am closing this pull request because we are in the process of separating EIPs and ERCs into distinct repositories. Unfortunately, as far as we are aware, GitHub does not provide any tools to ease this migration, so every pull request will need to be re-opened manually. As this is a PR to create / modify an ERC, I will kindly ask you to redirect this to the new repository at ethereum/ERCs. We have prepared a guide to help with the process. If there is relevant history here, please link to this PR from the new pull request. On behalf of the EIP Editors, I apologize for this inconvenience. |
|
I will update and start another pull request |
Discussion at: https://ethereum-magicians.org/t/erc-7110-erc-721-dynamic-ownership/14516
Renamed from EIP-8192 to EIP-7110 in all sections.