What Is IPFS? Content-Addressed Storage
IPFS (the InterPlanetary File System) is a decentralized, peer-to-peer protocol for storing and sharing files by their content rather than their location. Instead of asking a specific server for a file by URL, you ask the network for a file by its content identifier (CID) — a cryptographic hash of the file itself. Any node holding that content can serve it, and the hash guarantees you got exactly the right bytes.
This is a fundamental shift from the web's usual model. Normally a link like https://example.com/file is location-addressed: it points to a place, and if that server goes down or changes the file, the link breaks or silently serves something different. IPFS is content-addressed: the address is the fingerprint of the content, so the link always refers to that exact data no matter where it lives.
How content addressing works
When you add a file to IPFS, the protocol splits it into blocks and computes a cryptographic hash of each. Those hashes are combined into a single root CID that uniquely names the whole file. To retrieve it, you give the network the CID; IPFS locates peers that have the matching blocks (using a distributed hash table to find them), fetches the blocks, and reassembles the file. Because the CID is derived from the content, your device can re-hash what it received and verify it matches — if even one bit were altered, the hash would differ and the tampering would be obvious.
Content addressing gives you integrity for free
The killer property is tamper-evidence: the address is a hash of the content, so you can always check that the data you received is exactly the data that was requested. Identical files automatically share the same CID (natural deduplication), and content cannot be quietly swapped out the way a file behind a normal URL can be.
Persistence: pinning and gateways
IPFS does not magically keep files online forever. A piece of content stays available only as long as at least one node pins (chooses to keep and serve) it. If every node that had a file drops it, the CID still names the content, but no one can supply it. Anyone can run a node and pin data they care about, which is how communities and services keep content alive without depending on a single company's servers.
Why IPFS matters
Content addressing makes data verifiable, resilient, and server-independent. No single server is a chokepoint that can be taken down or coerced into altering a file, which is valuable for censorship resistance and for long-lived archives. For applications, it means you can reference a blob by its hash and be cryptographically certain of what you will get back.
Common misconceptions
- "Files on IPFS live forever." No — content persists only while some node pins it. Without pinning, it can disappear.
- "IPFS is anonymous." By itself it is not; peers can see which CIDs you request. Anonymity needs an additional layer such as Tor.
- "IPFS encrypts my files." The protocol addresses and distributes content but does not encrypt it for you; if you need privacy, you encrypt the data before adding it.
IPFS is not a blockchain
IPFS is frequently lumped in with cryptocurrencies and blockchains, but it is a different kind of technology and it is worth being precise. A blockchain is a shared, append-only ledger that every participant agrees on, designed to record an ordered history of transactions — it is about consensus. IPFS is a way to address and move files by their content hash — it is about storage and retrieval. IPFS does not require a global ledger, does not mine coins, and does not need every node to agree on a single history; nodes simply store and serve the blocks they choose to keep. The two can be combined — a blockchain can store a compact IPFS content identifier as a tamper-proof pointer to bulky off-chain data — but IPFS itself is just a distributed, verifiable file layer. Understanding this avoids a common misconception that using IPFS means adopting cryptocurrency or its energy costs.
How OSHI uses IPFS-style storage
OSHI uses a self-hosted, content-addressed blob store in the IPFS style to handle media and larger attachments. Files are referenced by the hash of their (already end-to-end encrypted) content, so a recipient can verify integrity and no readable copy sits on a third-party server. Because OSHI runs its own content-addressed store rather than relying on a public pinning provider, it keeps this piece of the system under its own control. OSHI is open source under the MIT license.
Related guides & features
End-to-end encryption What is Tor Mesh networking What is metadata Anonymous messaging All OSHI features Compare OSHIFrequently Asked Questions
What is IPFS?
IPFS, the InterPlanetary File System, is a decentralized peer-to-peer protocol for storing and sharing files by their content. You request a file by a content identifier, which is a cryptographic hash of the file itself, rather than by a server URL.
What is content addressing?
Content addressing means a file's address is a hash of its contents, not a location. The same content always has the same address, and you can verify that the data you received matches the address exactly.
Do files on IPFS stay online forever?
No. Content stays available only while at least one node pins it, meaning it chooses to keep and serve that content. If no node pins a file, it can become unavailable even though its address still exists.
Is IPFS encrypted or anonymous?
Not by itself. IPFS addresses and distributes content but does not encrypt it or hide who requests what. For privacy you encrypt files before adding them and use a network layer like Tor for anonymity.
How does OSHI use IPFS?
OSHI uses a self-hosted, content-addressed blob store in the IPFS style for media, referencing files by the hash of their already end-to-end encrypted content so integrity is verifiable and no readable copy sits on a third-party server.
Private messaging, by design
OSHI is a free, open-source, Swiss encrypted messenger. No phone number, no ads, no tracking.