Hi Guys,
All our NFTs are hosted with IPFS but since like 1 month or more ago those links stopped working.
Were they blacklisted or something ?
Example: https://bafybeif6xoldu6jgo254ngsr3te2llzvobcm4icrcbgecdge4rmti66xhe.ipfs.nftstorage.link/8575.png?ext=png
Need help please.
Thanks
nftstorage doesn’t exist anymore. The contents have been stored somewhere else and can be accessed at https://bafybeif6xoldu6jgo254ngsr3te2llzvobcm4icrcbgecdge4rmti66xhe.ipfs.dweb.link/ (for example).
I would make backups.
Thank you so much. How did you find that link ? And how can I find the link for the other 10k images of the collection?
Also, I don’t understand enough, but regardless of if nft.storage exist or not, shouldn’t the links be kept the same? I thought the hosting was “immutable” once uploaded would be kept like that for ever
The CID bafybeif6xoldu6jgo254ngsr3te2llzvobcm4icrcbgecdge4rmti66xhe is immutable. The content can be accessed through different gateways (i.e. dweb.link) or directly via IPFS (kubo).
For fully verified results in the browser you can use https://bafybeif6xoldu6jgo254ngsr3te2llzvobcm4icrcbgecdge4rmti66xhe.ipfs.inbrowser.link/ , which verifies the content client-side.
Here are some other gateways: Public Gateway Checker | IPFS
I don’t know the CID(s) for the other 10k images though.
Sorry, I am not sure if I have enough knowlagable to understand your explanaiton.
So you saying nft.storage was just one of those gateways ? and that is why nft.sortage name was on the previous links ?
The biggest problem we have is that our NFTs are immutable, and we can’t change the pointers/links inside the metadata, so even if we back up the images and move them somewhere else, or have access to this new “links” we can’t change in on the blockchain
The nft.storage domain was a gateway offering access to things stored by the NFT storage project.
In your blockchain metadata, you should probably just have used something like ipfs://<cid> rather than the nft.storage url. People will normally recognize the CID in the url though, and know they can try accessing the CID via other options. Problem can also be worked-around via browser extension.
I don’t have a good solution… maybe someone that knows more about why nft.storage hasn’t been redirected to an alternative gateway (given the content has been backed up) can speak up.
Thank you so much, you helped a lot. More than anyone else that I have asked before.
You actually mentioned before that we should back those files up, but isn’t IPFS a permanent host service? Like arweave you pay a one off fee and data is stored for ever?
No it’s not a permanent hosting service… it is not a blockchain to start with…
NFT.storage was more or less marketed on “free storage forever” terms though. So far they have made sure content was stored even though the service stopped, so I guess they are still delivering on that.
But did you pay a one-off fee?
Yes that was what was advertised. And that is why I think this nft.storage was used, instead of Arweave. I though NFT storage was just a intermediary between filecoin/IPFS and the user but the data was still stored safely
Is hard to understand because there isn’t anyone from nft storage to contact
Well, that’s correct, the data is stored safely in Filecoin… it’s the gateway and the possibility of onboarding new data that has been turned off.
