Blocky saysIPFS stores files by their content hash — address the data, not a location.
The InterPlanetary File System gives each file a content identifier (CID) derived from its hash, so the same content always has the same address and tampering is detectable. Anyone hosting the bytes can serve them. But IPFS doesn't guarantee persistence — files vanish unless someone pins them. It's the common home for NFT and dApp assets that want durability without full on-chain cost.
Power-ups you unlock
Content-addressed: CID = hash of the file
Same content → same address everywhere
Tamper-evident by design
Needs pinning to persist
Double-Spend Dan attacks — common mistakes
Assuming IPFS = permanent (it needs pinning)
Confusing content addressing with location addressing
Relying on one gateway as a single point of failure
Boss battleExplain why an IPFS CID changes if the file changes.
Example code
<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#e6e0ff;font-family:monospace;padding:20px"><pre>file → hash → CID (the address)
edit file → new hash → new CID
must be pinned to stay available</pre></body></html>