Hi devs — Nacho here from the BWS (Blockchain Web Services) team. We just shipped IPFS.NINJA , a managed IPFS pinning service, and one of the most common questions we get is: “How do I update content on IPFS without changing the URL?” The answer is IPNS (InterPlanetary Name System) — and it's one of those features that sounds confusing until you see it in action. Full disclosure: I work on this product. This post is a transparent walkthrough from the team that built it, with concrete examples you can copy-paste. The problem IPNS solves IPFS is content-addressed: change a single byte in a file, and the CID changes. That's a feature — immutability and verifiability are the whole point. But it's also a problem when you want to update something: Your dApp config evolves → new CID → every client needs the new link. Your NFT metadata levels up → new CID → your smart contract's tokenURI is now pointing at stale content. You redeploy your IPFS-hosted website → new CID → you have to tell users the new URL.…