Browse through https://opensea.io/, the most prominent NFT marketplace at the moment. Digging through the DOM of their website will reveal a lot of links to quite standard content storage solutions. They usually go through a bit of trouble to prevent people from simply clicking "view image in new tab" to reveal the actual location, but it's not difficult to get around.
> [O]ur NFT collection could very possibly become the largest on-chain collection ever in the history of Ethereum. Time would only be on our side because as gas becomes more expensive, the window of opportunity to bypass our on-chain NFT collection would fade away.
To give an idea of the storage costs associated, I dug up this old stackexchange-answer about storage costs on Ethereum [0], which estimates that it costs about 76.000 USD / GB stored. Note that this is 5 year old answer, so the price will probably have multiplied like the price of ETH since then.
Edit: Here's [1] a newer, updated price estimate that takes current prices into account : 309.9 Million / GB. LoL!
[0] https://ethereum.stackexchange.com/questions/872/what-is-the...
[1] https://proderivatives.com/blog/2019/5/10/minimizing-data-st...
The contract for the NFT generally just points to an IPFS identifier (a sha256 hash of the content), and it's up to the viewer (a website like opensea) to decide what ipfs gateway to use. Even if the ipfs network died you could still use other p2p methods to find the content, as long as someone was still hosting it.
It's a problem, it used to be the grand majority of collections were fully decentralised and frozen but nowadays it's a mixed bag – I think it will change once the gas problem is solved, but it's also partly because the audience has changed and newcomers into NFTs don't care so much about their tokens being fully decentralised.
> Here's what happens when you add a file to IPFS — whether you're storing that file on your own local node or one operated by a pinning service or IPFS-enabled app.
Notice that wording: “Add a file to IPFS”.
It’s likewise fine to say, then, that you “put something on ipfs”.
The filing cabinet is the storage, the way I organize files in the cabinet is the filing system.
This is false. Popular content is cached temporarily. Pinning persists the data until unpinned; the ipfs daemon does not automatically pin anything.
Unfortunately, things like that actually happen even though everyone here would consider it a joke.
Actually doing something about it is a problem, as shown throughout the post-Napster era, but every node that serves an infringing copy is potentially liable.
Wonder if they will be or have been subject to copyright complaints / lawsuits.
* Is the material copyrightable? A novel is copyrightable, but a recipe is not. The layout format of a telephone book is copyrightable, but the contents of it are not.
* Is the copyright still in effect? Unfortunately, this is a less relevant question now, as anything written within living memory is under copyright, but it is still a required step.
* Is permission from the copyright holder required? If I am sold a copy of a computer program, I'm allowed to make whatever copies are necessary (e.g. copying from the hard drive to RAM) that are necessary to execute the program, without the permission of the copyright holder.
* What is being done with the copy? If I buy a work, the copyright owner has no right to prevent me from selling it, nor are they entitled to any portion of the proceeds. Re-sale of authorized copies, regardless of permission, are not infringements.
Yes, you put a URL on the blockchain but it's almost always a URL to the ipfs protocol e.g. ipfs://QmVc6zuAneKJzicnJpfrqCH9gSy6bz54JhcypfJYhGUFQu
This identifier is a base58 encoding of a sha256 hash that points to the content. It doesn't actually tell you what host to use to find the content, that's completely left to the client app; so you could use an ipfs gateway like cloudflare-ipfs.com or ipfs.io or you could, imagining a future in which ipfs is not used anymore, use any other kind of p2p network to find the content.
Just like gnutella, or torrents, as long as someone out there is hosting the content it's usually possible to find it.
My point was more that the NFT metadata itself could still be usable x years in the future when another protocol has replaced ipfs – it would just have to make the files findable by the existing hash.
The biggest potential risk would be if sha256 becomes broken and finding collisions is trivial.
https://www.schneier.com/blog/archives/2021/03/illegal-conte...
The answer seems to be that 'nothing much happens, yet'.