-
Notifications
You must be signed in to change notification settings - Fork 135
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
Feature/supply key adapt metadata of nft #680
Feature/supply key adapt metadata of nft #680
Conversation
✅ Deploy Preview for hedera-hips ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Signed-off-by: Michael Garber <michael.garber@swirldslabs.com>
…adapt-metadata-of-nft
@mgarbs let me know if I need to adapt anything on this PR to get it past the apporvals |
The Engineering team has expressed quite a bit of concern over making a
once immutable NFT mutable by overloading the supply key.
…On Wed, Feb 22, 2023, 7:46 PM Patches ***@***.***> wrote:
@mgarbs <https://github.com/mgarbs> let me know if I need to adapt
anything on this PR to get it past the apporvals
—
Reply to this email directly, view it on GitHub
<#680 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMEGCHW67DVIZ2JFCF5253WY2XNBANCNFSM6AAAAAAU6NUGD4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
What would be the best venue to engage in dialogue about the opposing opinions? I haven't seen any feedback that wasn't responded to in the discussions |
While I empathize with the problem this is trying to solve (the perceived value of an NFT’s serial number is greater than its metadata) I do not believe this HIP should be implemented. This changes the rules for existing NFTs and the tokenomic assumptions around them for both creators and owners. Once the sister HIP (metadata key) is implemented, why not just offer to burn and re-mint fungible metadata NFTs instead. You can always swap serial number for serial number? |
Signed-off-by: Michael Garber <michael.garber@swirldslabs.com>
I would agree with you 95% (could you elaborate on how this would affect tokenomics?) if the only focus and benefit was to create a method for backwards compatibility for adaptation of NFTs without burning. The functionality that Hedera is uniquely positioned to implement is to have trustless immutability in distribution and mutable data in treasury wallet. I believe use cases from gaming to legal contracts to PFP projects would benefit from being able to guarantee no manipulation of data outside of the owner sending their NFT to the treasury wallet. It also is a step closer to secure methods of adaptation than just the boolean with the METADATA key: ALL data can be edited all the time or none of the data can be edited ever. This addition would innovate a new state that's flexabile, and has trustless protection to holders. Addressing the security concerns: That coupled with the fact that almost all token Ids have a supply key since that's required to mint does make this more of a risk. All that said, I see the risks as extremely low. Points of attack from a malicious actor:
This requires the seller to be a malicious creator, to hold the NFT, and to devalue serial numbers of their own project for short term gains. The ramifications of this action would also cause a lot of uncertainty in whatever platform or creator was doing this. My main retort to security issues: A HTTP uri can change any data at any time for any NFT (much like a METADATA key). Most users don't understand the storage implications and developers are already using HTTP to get the benefits of this HIP which expose holders to more risk IMHO. I do believe there's a lot of benefits and innovation this HIP would bring. A new dynamic of more granular adaption of NFTs and more trustless immutability to users. |
While metadata mutation for NFTs has potential benefits, it's important to consider the drawbacks. Some of the things that have been discussed with engineering:
|
Being replaced with - #850 |
Description:
Related issue(s):
Fixes #
Notes for reviewer:
Checklist