I’m working on a project involving NFTs on the NEAR blockchain, and I’m wondering about adding extra information to the metadata. Does anyone know if including additional fields in the NFT metadata will affect its NEP 171 compatibility? I’m not sure what the best approach is here.
I’ve heard that using the extra field in NFT metadata might be a solution, but I’d like to confirm if this is the right way to go about it. Can someone explain how to properly extend NFT metadata while staying within the standard guidelines?
Also, if there are any other recommended methods for including custom data in NEAR-based NFTs, I’d really appreciate hearing about them. Thanks in advance for any insights or advice you can offer!
hey man, ive worked with near nfts before. using the extra field is totally fine for adding custom data. it won’t mess with nep 171 compatibility at all. just make sure to serialize your extra data properly. you could also consider using token-specific metadata if you need more flexibility. hope this helps!
I’ve implemented custom metadata for NEAR NFTs in several projects. The extra field is indeed the recommended approach for extending metadata without compromising NEP-171 compatibility. It’s designed specifically for this purpose.
When using extra, ensure you serialize the data as a JSON string. This maintains flexibility while adhering to standards. For more complex scenarios, consider implementing a separate metadata contract that your NFT contract can reference. This allows for more extensive customization without cluttering the NFT metadata itself.
Remember to document your metadata structure clearly for any applications or marketplaces that might interact with your NFTs. This ensures smooth integration and better user experience across the NEAR ecosystem.