-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add EIP-5773: Multi-Resource Token standard #5773
Conversation
RMRK team has developed a next step in NFTs where one NFT can be tied to multiple resources.
All tests passed; auto-merging...(pass) eip-5773.md
(pass) assets/eip-5773/contracts/IMultiAsset.sol
(pass) assets/eip-5773/contracts/MultiAssetToken.sol
(pass) assets/eip-5773/contracts/library/MultiAssetLib.sol
(pass) assets/eip-5773/contracts/mocks/ERC721ReceiverMock.sol
(pass) assets/eip-5773/contracts/mocks/MultiAssetTokenMock.sol
(pass) assets/eip-5773/contracts/mocks/NonReceiverMock.sol
(pass) assets/eip-5773/contracts/utils/MultiAssetRenderUtils.sol
(pass) assets/eip-5773/hardhat.config.ts
(pass) assets/eip-5773/package.json
(pass) assets/eip-5773/test/multiasset.ts
(pass) assets/eip-5773/test/renderUtils.ts
|
I intend to add discussion link at the same time as I will update the EIP number, to reduce the number of pushes to the initial PR. |
title: Multi-Resource Token | ||
description: An interface for Multi-Resource tokens. | ||
author: Bruno Škvorc (@Swader), Cicada (@CicadaNCR), Steven Pineda (@steven2308), Stevan Bogosavljevic (@stevyhacker), Jan Turk (@ThunderDeliverer) | ||
discussions-to: <URL> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't forget to create a discussion thread :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I intended to add it at the same time as the EIP number was assigned (wanted to include the EIP number in the discussion title). I'll open a discussion now and add it :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done ✅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I intended to add it at the same time as the EIP number was assigned (wanted to include the EIP number in the discussion title). I'll open a discussion now and add it :)
I thought the bot was going to assign the number and create the thread automatically.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I intended to add it at the same time as the EIP number was assigned (wanted to include the EIP number in the discussion title). I'll open a discussion now and add it :)
I thought the bot was going to assign the number and create the thread automatically.
It only reports the missing EIP number and that an editor should assign it. Should I just use the PR number? So 5773?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll use it as this EIP is already being referred to as EIP-5773:
https://weekinethereumnews.com/week-in-ethereum-news-october-15-2022
https://twitter.com/WeekInEthNews/status/1582456945750904832?s=20&t=0H712tazBBqHtRQgD227OA
The number can be changed at any time, if you decide to assign a different one 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought the bot was going to assign the number and create the thread automatically.
Not yet. We're waiting on #5508.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's my review so far.
EIPS/eip-5773.md
Outdated
|
||
## Abstract | ||
|
||
The Multi-Resource NFT standard allows for the construction of a new primitive: context-dependent output of multimedia information per single NFT. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WDYM by primitive?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We were referring to a simple, clearly defined, structure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Multi-Resource NFT standard allows for the construction of a new primitive: context-dependent output of multimedia information per single NFT. | |
The Multi-Resource NFT standard allows for the construction of a new simple, clearly defined structure for context-dependent output of multimedia information per single NFT. |
"Primitive" is very often associated with language features. I suggest this wording.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense. Thank you 😄
Thank you for the comments, I applied the changes based on them and pushed them |
Co-authored-by: Pandapip1 <45835846+Pandapip1@users.noreply.github.com>
EIPS/eip-5773.md
Outdated
@@ -0,0 +1,362 @@ | |||
--- | |||
eip: 5773 | |||
title: Multi-Resource Token |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably a bit too vague. Try to expand a tiny bit about what resources are, or what you can do with these tokens while staying under the character limit.
EIPS/eip-5773.md
Outdated
--- | ||
eip: 5773 | ||
title: Multi-Resource Token | ||
description: An interface for Multi-Resource tokens. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Try not to make this just a rewording of the title. It should expand a little beyond what's in the title.
EIPS/eip-5773.md
Outdated
|
||
RMRK MultiResource lego block and documentation | ||
|
||
- Compatible with the original version of the standard | ||
|
||
Neon Crisis, by CicadaNCR | ||
|
||
- A NFT game utilizing RMRK MultiResource lego block | ||
|
||
Snake Soldiers, by Steven Pineda | ||
|
||
- A NFT game utilizing RMRK MultiResource lego block |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please include the reference implementation in the assets
directory if you have a compatible license (free to redistribute and doesn't place additional restrictions on downstream projects like Apache, MIT, or preferably CC0.)
If you cannot include them, just remove these projects.
Applied the changes based on feedback received on the EIP Editing Office Hour Meeting ethereum#5. This commit includes changes to the proposal as well as adds an exaple implementation to assets/ directory.
Co-authored-by: Sam Wilson <57262657+SamWilsn@users.noreply.github.com>
The proposal was renamed to Context-Dependent Multi-Asset Tokens to better illustrate its function. Another example was added to represent the possible IoT usecase and the explanation on the naming decision was added to the rationale. The examples were relicensed to CC0, to conform to the requirements of EIP repository.
a privitive is generally a building block, and isn't necessarily limited to programming languages
This EIP draft proposal includes RMRK team's work on developing an NFT standard where a single NFT can be tied to multiple resources.