How to keep NFT metadata stable without leaking info?

Question

Im trying to develop an NFT contract and wish to make sure all NFT metadata remains stable. Im concerned that if I include a source metadata link in the contract, it could be visible to users who might exploit it. How can I prevent this from happening? Additionally, Id like to know if I can add optional fields to an NFT object as I do in TypeScript. Heres my idea: type NFT = { name: string; description: string; url: string; attributes: {field: string; value: string}[]; }; Ive never seen this approach before and I feel like Im missing something. Can someone guide me on the best practices here?

yhant3 · Accepted Answer

Regarding adding optional fields similar to TypeScript, you can indeed customize your NFT metadata. Theres a standard metadata format used by popular NFT collections, but you can deviate from it. Use VecMap for attributes as you mentioned, and explore the options of using the Display parameter to customize what metadata is shown. To learn more, explore these resources: NFT Standards and Royalties SUI Vision Object with Fields NFT Display Parameters

Michelle · Answer

It sounds like your main concern is that someone might deduce future NFT metadata because of how theyre minted sequentially. To mitigate this risk, consider shuffling the metadata sequence outside the blockchain. This way, even though they may appear sequential on the blockchain, the metadata wont be predictable. Alternatively, assign a random ID and ensure that the minting function checks that this ID hasnt been minted yet.

帖子

分享您的知识。

How to keep NFT metadata stable without leaking info?

答案

你知道答案吗？