I gave a poor example. What I wanted to say was an ever changing data in a non-centrally managed context. Some nodes hold hashes for the previous version and then they&#x27;d compete for resources.<p>The thing from bitcoin is 51% attack where majority of nodes collude to provide the wrong data(they might not be malicious but just serving old version of a data). This can only be prevented by time-stamping in slow scenarios.<p>In case of neocities, a central server is giving you a hash that the nodes would provide you the data for, but without a central management how does IPFS associate correct file to the correct hash?<p>If it only works for a centralised scenario then it is similar to the <a href="http:&#x2F;&#x2F;peercdn.com" rel="nofollow">http:&#x2F;&#x2F;peercdn.com</a> project where instead of a server supplying content, your previous visitor browser cache is supplying the content through p2p webrtc and you save server bandwidth.