Hey everyone, I’m working on a project involving NFTs on the NEAR blockchain and I have a question about metadata. I want to include some extra information in the NFT metadata, but I’m not sure if this will affect its compatibility with NEP 171. Does anyone know if adding custom fields to the metadata will cause any issues?
I’ve been looking into this and found the extra field in the NFT metadata structure. Is it okay to put additional JSON data there? Or is there a better way to include extra information without breaking the standard?
I’m really trying to balance between having all the data I need and sticking to the proper format. Any advice or experiences with this would be super helpful. Thanks in advance!
yo sophia, totally get ur struggle. been there myself. the extra field is ur best bet for custom data without messin with nep 171. just dump ur json in there and ur good to go.
but heads up, some wallets might not show that extra stuff. maybe consider makin ur own viewer for the full experience? jus a thought. good luck with ur project!
Regarding your question about expanding NFT metadata while maintaining NEP 171 compatibility, you’re on the right track with the extra field. This is indeed the designated space for additional custom data without compromising the standard.
However, it’s crucial to consider how this extra data will be utilized. While adding custom fields to extra won’t break compatibility, not all platforms or applications may recognize or display this information. It’s advisable to document your custom metadata structure thoroughly for other developers or services that might interact with your NFTs.
Additionally, consider the size implications of your extra data. While there’s no strict limit, excessively large metadata could impact performance or cost. If you’re planning to include substantial additional information, you might want to explore off-chain storage solutions and reference them in the metadata instead.
Lastly, ensure your core metadata adheres strictly to the NEP 171 standard to maintain wide compatibility across the NEAR ecosystem.
hey sophia! that’s a great question about nft metadata. i’ve actually been experimenting with this myself recently.
from what i’ve found, using the extra field is definitely a good way to add custom data without breaking nep 171 compatibility. you can put pretty much any json in there and it should be fine.
but i’m kinda curious - what sort of extra info are you wanting to include? might give some ideas for how to structure it best. have you thought about maybe using a standardized format within extra so other devs can easily parse it too?
also, random thought - have you looked into how marketplaces and wallets handle custom metadata? might be worth checking if theres any quirks there. let me know what you find out!