So, IPFS (which is actually very similar to torrent files on a theoretical level) has all the 'nice' properties that come with being stateless. Because of this, IPFS and torrents don't fundamentally need a cryptocurrency platform to enable them (though you can use one, you don't need to).

By stateless I mean this: once you solve the bootstrapping problem (e.g. finding the hash of the file you're looking for, or the torrent file you want), verification is actually quite easy as it doesn't require external validators. The hash of the file always matches -- as it has no state, the file contents don't change, and thus it is easy to verify the hash of the file matches the hash you are looking for.

For statefull content, think about your account balance. There's no way for you to validate your own account balance in constant time -- you need to know the current state of the whole ecosystem and it's entire history to know your balance, as your balance is actually not a single "thing" with cryptocurrencies: your balance is rather the sum of all your historical actions regarding your balance.

So, unfortunately file storage doesn't help with statefull content -- this is where we have that necessity for validation, and where we run into the trusted interfacing problem. If the trusted interface misses (or hides) a historical action, they hide the truth. And unlike with stateless content, you cannot immediately validate on your own that an item is missing.