Modifying NFT metadata on NEAR: Compatibility and best practices

NFT
1

Hey everyone,

I’m working on an NFT project on the NEAR blockchain and I have a question about metadata. I want to add some custom fields to my NFTs. Will this mess up the NEP 171 compatibility?

If it does cause issues, what’s the best way to go about adding extra info? I’ve heard something about using an extra field in the metadata for custom stuff. Is that the right approach?

I’m pretty new to this, so any advice would be super helpful. Thanks in advance!

{
  "name": "Cool NFT",
  "description": "An awesome NFT with extra data",
  "image": "ipfs://...",
  "extra": {
    "customField1": "value1",
    "customField2": "value2"
  }
}

Is this kind of structure okay? Let me know what you think!

2

hey there WhisperingTree! :blush: that’s a super interesting question about nft metadata. i’m actually working on something similar and have been wondering about custom fields too.

from what i’ve read, using the extra field like you showed is totally fine and won’t mess up NEP 171 compatibility. it’s a neat way to add your own unique data without breaking anything.

but i’m curious, what kind of custom info are you thinking of adding? any cool ideas you wanna share? :thinking: maybe we could brainstorm some creative uses for those extra fields!

also, have you looked into how different marketplaces handle that extra data? i wonder if they all display it properly or if some might ignore it. might be worth checking out before finalizing your metadata structure.

anyways, your approach looks solid to me. keep us posted on how your project turns out!

3

yo WhisperingTree, ur on the right track with that extra field! it’s a solid way to add custom stuff without messin up NEP 171. just keep in mind not all marketplaces might show that extra data, so plan accordingly. what kinda unique info u thinkin of adding? sounds like a cool project, keep us updated!

4

Your approach using the extra field is indeed correct and aligns with NEP-171 standards. This method allows for custom data inclusion without compromising compatibility.

However, it’s crucial to consider the implications of adding custom fields. While it won’t break compatibility, not all platforms or marketplaces may display or utilize this extra data. It’s advisable to research how your target platforms handle custom metadata.

Additionally, consider the long-term maintainability of your metadata structure. As your project evolves, you might need to update or expand these custom fields. Ensure your implementation allows for future flexibility.

Lastly, document your custom fields thoroughly. This will help both your development team and potential integrators understand and work with your NFT data effectively.