Closed k06a closed 3 years ago
@k06a @Swader
We appreciate your effort to document a (possible) standard for the Ethereum developers. If this is your first EIP, my recommendation would be to follow EIP-1. You may also refer to The New Ethereum Improvement Process.
As per the new process, we recommend author(s) to create a new topic for discussion at Fellowship of Ethereum Magicians instead of creating an issue in this repo to get better visibility of the proposal.
@poojaranjan thx! Will do!
Please drop the FEM discussion link here, update the link "discussion-to" link on the proposal.
I'll start, since this is something we've already built and is working well over at RMRK.app.
In a nutshell, if you allow the owner field of an NFT to be anything (NFT ID or Account ID), you have hierachical NFTs. A common concern is then "stack overflow" with too much nesting, but this is easily avoided by only caring about the next neighbor by default and letting UIs and tools implement recursive treeversal as needed (it's up to them then, but in most cases this should not be necessary).
For an in-depth breakdown of all the functionality this makes possible: https://url.rmrk.app/dawn should be helpful, and our prototype based on this functionality is described here: https://url.rmrk.app/demobird
We intend to write an EVM version of all our logic eventually, so it would be great to fold this effort into that so we don't end up with many hierarchical NFT standards.