You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you create a metadata and host it on ipfs, it gives you a hash starting with Qm and it is accessible on the network using ipfs prefix like ipfs://Qmsomething
Browser wallet cant process metadata without having `https://ipfs.io` before the prefix cause it sends GET requests directly. However, this gateway is not IPFS. It is a gateway meaning if this website stops, things can get lost if its the metadata. Right way of storing metadata is ipfs://Qm and any gateway can reflect the network that way.
Ideally, a wallet should handle both. Ping me for more details or if not clear. @by
The text was updated successfully, but these errors were encountered:
When you create a metadata and host it on ipfs, it gives you a hash starting with Qm and it is accessible on the network using
ipfs
prefix likeipfs://Qmsomething
Browser wallet cant process metadata without having `https://ipfs.io` before the prefix cause it sends GET requests directly. However, this gateway is not IPFS. It is a gateway meaning if this website stops, things can get lost if its the metadata. Right way of storing metadata is
ipfs://Qm
and any gateway can reflect the network that way.Ideally, a wallet should handle both. Ping me for more details or if not clear. @by
The text was updated successfully, but these errors were encountered: