# NFT Metadata
Twitter spaces hosted by [Anett](https://twitter.com/AnettRolikova)
Time: 30 July at 2pm UTC
# Questions:
- How are being metadata stored ?
- Is IPFS reliable for storing metadata ?
- Are we going to store NFT Metadata on chain or offchain ?
- Storing metadata on-chain or off-chain. Causing network state bloat
- OpenSea decentralising metadata [blog](https://opensea.io/blog/announcements/decentralizing-nft-metadata-on-opensea/)
- How is Zora solving Storage issues ?
- Rarible solution [blog](https://rarible.medium.com/meet-metadata-guardians-trying-to-make-your-nft-collection-available-100-years-from-now-60a18baeed6c)

## Storage solutions for NFTs
- [Free decentralized storage and bandwidth for NFTs on IPFS and Filecoin.](https://nft.storage/#getting-started)
- [The Future of DataDAOs - filecoin]( https://filecoin.io/blog/posts/the-future-of-datadaos/)
- [Arweave - store files for ever](https://www.arweave.org/)

# Notes
- We can't host metadata directly on chain
- We are using Token URI to store these data on
- We are storing the data on server but if node is down we can't access the data
- zora stores the uris that are updatable along with content hashes to make sure in the future the url can be updated to point to the same content as a future proofing measure
- IPFS files need to be kept in the network by a pin otherwise there’s no guarantee it will be available
- We should focus more on how to fit the data into the token not what kind of data to fit there
- Opensea is freezing metadata - taking screenshot of the data and uploading them to IPFS
- Not a big issue to use centralised servers
- People don’t care much where the data is stores if they wont change
- what fields to add we should look at twitter embeds and backwards compatibility
- Similar like ERC2891 royalty standandard
- No need to unify the standars but let the smart contract represent the off chain metadata storage standard
- what is metadata on chain and how media ccan be described without lot of work from people to take a look at the metadata
- create easy entry and access to the metadata
- better to find a way how to access the metadata
- what the description of the metadata would look like
- how to describe the media - the reference and describing not about the storage
- you dont want to change the NFT if you are not building async art
- splitting content
- no ERC standard have defined content how to show metadata how to show the metadata and show the information
- to upload mp3 and image with audio file, its impossible to include video and image, you have to upload it as gif for audio animation
- content is separate and there's a mess about browser understanding image / video file
- it would be better to have more description to include more variety of files
- would be lovely to probably have this metadata standardised
- platforms like cathalog are usign zora protocol which created its own definitioon of metadata but the metadata are custom that browsers dont understands them
- the custom fields for metadata does makes sense
- so there will be portability between platforms so other platforms and people can render them without writing custom solutions
- reduce custom code as they dont render on other platforms
- everything needs to have custom compatibility in order to break less things
- backwards compatibility is not too difficult
- platforms want to differ from itself in terms of showing different type of files and content
- when you generate the metadata you dont know the ID of the token so you need to mint the NFT before refferencing to the NFT
- you can reffernece to NFT from on chain hash - metadata
- and your website still need to create the logic by yourself
- custom solutions are nice but they may broke on other website as they cant read the metadata
- they can fetch the data to web2 server which is not so much web3 and focus on the content hashes as key feature
- as long as you have copy of the data you can bring to life by repining back to IPFS
- you dont want to create decentralised twitter as you want to delete tweets at some point
- metadata is the wild west as the key thing is to get everyone in the same room and publish what everyones views are cc nftstandards.wtf
- for example royalty standard hahs been ignored for a long time but now bigger platforms are about to implement it as they realised its cool
- there will be discussion around this at NFT NYC
- mintbase and near is using weird mutation of EVM metadata
- there are a few custom minting tools built of top of Zora protocol
- anyone can build custom front end to zora protocol
- you can custom describe metadata of the adddress and you can include the metadata in the token itself
- Zora is supporting sugraph of polygon
- cathalog is music specific building on zora protocol and cryptographically sign the records
- people are interested in music related standards