Add EIP: Versioned TokenIDs for Dynamic NFTs #6912
Conversation
github-actions
bot
added
c-new
File
|
eth-bot
changed the title
eth-bot
added
e-consensus
eth-bot
changed the title
|
The commit e1169f6 (as a parent of 76681f6) contains errors. |
github-actions
bot
added
w-ci
emo-eth
force-pushed
the
emo.eth/versioned-token-ids
branch
from
9715d77
to
5b36079
Compare
| --- | ||
| eip: 6912 | ||
| title: Versioned TokenIDs for Dynamic NFTs | ||
| description: A minimal, backwards-compatible specification for versioned token IDs for dynamic NFTs. |
There was a problem hiding this comment.
Your description doesn't really add any information over the title. Answering the question of "what is a versioned token ID" would be a reasonable goal for your description.
|
|
||
| This EIP proposes an extension to the [ERC-721](./eip-721.md) non-fungible token standard by introducing a Versioned TokenId standard for "dynamic" NFTs with on or offchain properties that may change over time. The new "versioned tokenId" is meant to track both the "identifier" of a token as well as its current "version number" so that old outstanding orders and approvals for updated tokens are automatically invalidated. | ||
|
|
||
| A `uint256 versionedTokenId` MUST encode both the true token "identifier" along with a "version number". Encoding, storage, and retrieval specific details should be left up to individual token implementations, and this EIP does not make specific recommendations. |
There was a problem hiding this comment.
You shouldn't introduce any requirements ("MUST") outside of the Specification section. Give an overview in the abstract, but don't use the RFC 2119 keywords.
|
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. |
When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md
We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met: