Secure Decentralized File Sharing System Using Ipfs — Complete Documentation & Simulation

Overview & System Context

Secure Decentralized File Sharing System Using Ipfs: Comprehensive Web-Sourced Technical Investigation Exhaustive Research Dossier · Pure Web-Scraped Content: ~4659 Words · Real Software Screenshots: 3 1. Executive Overview & Technical Background The InterPlanetary File System (IPFS) is a protocol, hypermedia and file sharing peer-to-peer network for sharing data using a distributed hash table to store provider information. By using content addressing, IPFS uniquely identifies each file in a global namespace that connects IPFS hosts, creating a distributed system of file storage and sharing. IPFS allows users to host and receive content in a manner similar to BitTorrent. As opposed to a centrally located server, IPFS is built around a decentralized system of user-operators who hold a portion of the overall data. Any user in the network can serve a file by its content address, and other peers in the network can find and request that content from any node who has it using a distributed hash table (DHT). In contrast to traditional location-based protocols like HTTP and HTTPS, IPFS uses content-based addressing to provide a decentralized alternative for distributing the World Wide Web.

Content-addressed file storage: Each file is uniquely identified based on its content hash, ensuring data integrity and facilitating efficient retrieval. Peer-to-peer architecture: A distributed network of nodes facilitates direct file sharing without the need for centralized servers. Versioned file system: Supports file versioning and allows users to track changes over time. Interoperability with distributed applications: IPFS integrates with decentralized applications (dApps), offering a storage layer for blockchain and Web3 ecosystems. IPFS gateways allow browsers and tools that lack native IPFS support to access IPFS content over HTTP. Users may choose not to install an IPFS client on their device and instead use a public gateway. A list of these gateways is maintained on the IPFS GitHub page.

Filecoin is a cryptocurrency used to implement an IPFS-based cooperative storage cloud, also authored by Protocol Labs. The shadow libraries Anna's Archive and Library Genesis host books via IPFS. The Brave browser added support in 2021, however support for local nodes and the ipfs:// scheme was removed in 2024 due to low usage and lack of support. IPFS is used as a storage layer for some decentralized applications and Web3 projects, including NFT platforms and blockchain-based services, because content addressing and distributed storage can improve data persistence and reduce reliance on single centralized servers.

Content-addressable storage Dat (software) Distributed file system Hyphanet GNUnet I2P ZeroNet Figure 1: Embracing Decentralization with IPFS Desktop: Empowering File Sharing ... The decentralized web is a network of independent computers that provide secure, censorship-resistant access to information and services without relying on central servers or clouds, using decentralized computing.

Decentralization and democracy: A key aspect of Web 3.0 is its aim to restore the decentralized nature of the original web, thereby returning control and ownership to users. This shift is seen as a way to counteract the loss of democracy and freedom caused by centralized control of data. Censorship and security: Web 3.0 addresses major Internet issues like censorship by governments and security risks due to centralized data storage. Decentralization in Web 3.0 could significantly reduce these issues. Challenges of bandwidth and storage: Web 3.0 also aims to tackle the inefficiencies of bandwidth usage and storage limitations inherent in Web 2.0, proposing solutions like the InterPlanetary File System (IPFS) for more efficient data handlings.

Anna's Archive is an open source search engine for shadow libraries that was launched by the pseudonymous Anna shortly after law enforcement efforts to shut down Z-Library in 2022. The site aggregates records from Z-Library, Sci-Hub, and Library Genesis (LibGen), among other sources. It calls itself "the largest truly open library in human history", and has said it aims to "catalog all the books in existence" and "track humanity's progress toward making all these books easily available in digital form". It claims not to be liable for downloads of copyrighted works since it does not directly host any files, instead linking to third-party downloads. It has nonetheless been targeted for engaging in large-scale copyright infringement, facing government blocks and legal action from rightsholders and publishing trade associations.

Anna's Archive has said its objectives are to "catalog all the books in existence" and "track humanity's progress toward making all these books easily available in digital form". It has been described as both continuing and greatly extending the ambitions of earlier shadow libraries with its vision of a "universal library" that preserves as many books as possible. It has been interpreted as part of an ascendant "culture of mistrust towards corporations, institutions, governments, and laws... that perhaps began with the financial collapse of 2008 and the Occupy Wall Street movements" which saw the rise of decentralizing technologies. Anna has justified their opposition to copyright on ethical grounds, stating that they "believe that preserving and hosting these files is morally right" and that they and other shadow librarians believe that "information wants to be free". They have suggested that copyright law must be reformed as a matter of national security, proposing that Western countries make legal carveouts for text and data mining so as to remain ahead in the AI arms race. Anna cites programmer and information activist Aaron Swartz as inspiring the project's collection of metadata. The site recommends Swartz's writings as well as Stephen Witt's How Music Got Free and Michele Boldrin and David K. Levine's Against Intellectual Monopoly, which criticize existing copyright law and have been associated with the copyleft movement.

Figure 2: IPFS | Anonymity Network Official blog SLUM: The Shadow Library Uptime Monitor PiLiMi team website at the Wayback Machine (archived 2023-02-19) The InterPlanetary File System (IPFS) is a set of building blocks for a better web. Open protocols to make your data smarter: content-addressed, verifiable, and unstoppable.

On a more technical level, IPFS is a set of open protocols for addressing, routing, and transferring data on the web, built on the ideas of content addressing and peer-to-peer networking. Many popular projects are built with IPFS - see the ecosystem directory (opens new window) and the awesome-ipfs (opens new window) list to find some of these projects.

Figure 3: IPFS Desktop | IPFS Docs Install IPFS Desktop (GUI), Kubo (CLI), or IPFS Companion (browser extension). For infrastructure, see IPFS Cluster, Rainbow, and Someguy . Learn how to retrieve data , provide content , deploy websites , or build applications .

IPFS is a great fit for deploying static sites and dapps, check out the following guides to get started: If you're having trouble retrieving or providing data to the IPFS network, check out the troubleshooting guide . As the IPFS ecosystem has grown and evolved with multiple implementations in different languages, HTTP has become an important foundation for interoperability. Check out the following resources to learn more: Are you developing with IPFS implementations and tools, and looking for technical support from IPFS experts? For the fastest possible assistance and resolution of your support needs, see the guide to getting technical help and support .

IPFS has a bustling community of designers, developers, writers, and activists who are all helping to improve the project. Find out about the events and resources available, and how to get involved in the Community section In this conceptual guide, you'll learn about the major subsystems that IPFS is composed of, and how they work. The three key responsibilities of the IPFS subsystems are: While these are the key responsibilities, IPFS's functionality spans beyond these three.

Data in IPFS is addressed by its contents ( content addressing ), rather than a location, such as an IP address (location addressing). This guide is part 3 of a 3-part introduction to the basic concepts of IPFS . The first part, What IPFS is and isn't , defines IPFS, while the second part, IPFS and the problems it solves , covers the problems with the internet and current protocols like HTTP that IPFS solves.

2. System Architecture & Core Working Principles All IPFS subsystems, ordered by purpose, are listed below, with links to the major subsystems discussed in this guide. IPFS represents data as content-addressed blocks , and operates on those data blocks using the following subsystems: In IPFS, data is chunked into blocks , which are assigned a unique identifier called a Content Identifier (CID) . In general, the CID is computed by combining the hash of the data with its codec . The codec is generated using Multiformats .

IPFS uses InterPlanetary Linked Data (IPLD) to work with CIDs and content-addressed data. IPFS uses IPLD to represent relationships between content-addressed data, such as file directories and other hierarchical structures, using a Directed Acyclic Graph (DAG) called a Merkle DAG . Using IPLD for the general functionality, IPFS is able provide a more tailored, specific mechanism for representing and addressing files, directories, and their symlinks, called UnixFS . With UnixFS, IPFS can chunk and link data too big to fit in a single block, and use the chunked representation to store and manage the data.

IPFS uses Content Addressable aRchive (CAR) files to store and transfer a serialized archive of IPLD content-addressed data. CAR files are similar to TAR files, in that they that are designed for storing collections of content addressed data. Content routing refers to the way in which IPFS determines where to find a given CID on the network; specifically, which network peers are providing the CIDs you are requesting. In other words, a node cannot simply find data in the network with a CID alone; it requires information about the IP addresses and ports of its peers on the network. To route content, IPFS uses the following subsystems: IPFS uses Kademlia, a Distributed Hash Table (DHT) designed for decentralized peer-to-peer networks. Kademlia helps you find peers in the IPFS network storing the data you are seeking. The Kademlia DHT can be thought of as a large table distributed across many nodes that stores information about which peers (IPs) have which data (CIDs). Kademlia provides a highly efficient, self-organizing system that withstands node churn. Kademlia uses libp2p to establish connectivity.

Want to learn more about Kademlia and DHTs? See the Distributed Hash Tables (DHTs) conceptual guide . IPFS nodes use Bitswap, a message-based , peer-to-peer network protocol for the transfer of data, that is also used for routing data. With Bitswap, an IPFS node can ask any of the peers that it is connected to if they have any of the CIDs that node is looking for, all without traversing the Kademlia DHT . Peers also store wantlists, so that if a peer receives the requested data at a later time, it can then send it to the node that originally requested. Like Kademlia, Bitswap uses libp2p to establish connectivity.

Delegated content routing is a mechanism for IPFS implementations to use for offloading content routing to another process/server using an HTTP API. For example, if an IPFS node does not implement the DHT, a delegated router can search the DHT for peers on its behalf. The main benefit of delegated routing is that nodes are not required to implement routing functionality themselves if they do not have the computing resources to do so, or wish to build an IPFS system with a custom backend for routing. So, delegated routing over HTTPS provides IPFS nodes with a standard interface that allows more flexibility in terms of how content routing works.

For further information, see the Delegated Content Routing HTTP API spec (opens new window) .. To quickly and efficiently discover peers in local networks, IPFS uses Multicast Domain Name System (mDNS), a type of DNS protocol that resolves human-readable internet domain names to IP names without the use of a name server . The use of mDNS enables quick and efficient discovery of IPFS nodes in local networks without any coordination, e.g., without internet connectivity or access to bootstrap nodes .

In addition to routing data , nodes in the IPFS network must efficiently distribute and deliver the content addressed data, taking into account that there are some nodes in the network who already have a copy of the data, and other nodes who do not have a copy of the data, but want one. To handle the transfer of data, IPFS uses the following subsystems: As discussed in How content routing works in IPFS , IPFS nodes use Bitswap, a message-based , peer-to-peer network protocol for both content routing and the transfer of data. With Bitswap, any peers that an IPFS node is connected to can transfer requested blocks directly to that node without needing to traverse the DHT . Peers also store wantlists, so that if a peer receives requested data at a later time, it can then transfer it to the node that originally requested.

HTTP Gateways allow applications that do not support or implement all IPFS subsystems to fetch data from the IPFS network using an HTTP interface. In its simplest form, a gateway is an IPFS Node that also exposes an HTTP Gateway API (opens new window) . For use cases where transfer of data over a network connection is not an option, IPFS supports the use of sneakernet to transfer content-addressed data between IPFS nodes. Using IPFS, CAR files (discussed in How IPFS represents and addresses data ) can be transferred between two network drives without any network connectivity. Because of IPFS, the data is verifiable and will have the same CID on both sides of the air gap.

No matter who you are or what you're creating, you can be part of the movement to create the next generation of the internet. This site contains everything you need to start building using the InterPlanetary File System (IPFS) and pave the way for the future Web. Check out some of the most popular content in these docs below âII or explore the main site menu to learn about key concepts , try out how-to guides , see API and CLI references , or just install IPFS and get hacking.

These tools can help you use and build on IPFS more quickly and efficiently âII give them a try today! Protect yourself from single-point-of-failure risks and benefit from decentralized infrastructure by hosting your static website using IPFS. If you're new to IPFS, this is an excellent place to start learning how to build on the decentralized web. Want to know more about the decentralized web (DWeb) and how it's changing the internet? These resources will give you a clearer understanding of the DWeb movement, and how it's improving the world: ProtoSchool's self-guided interactive tutorials (opens new window) are designed to introduce you to decentralized web concepts, protocols, and tools. Explore JS-IPFS APIs by completing browser-based coding challenges in ProtoSchool's IPFS course (opens new window) , or explore code-free intros to essential DWeb concepts and related projects in the IPFS ecosystem.

3. Software Implementation, Frameworks & Protocols Are you looking for inspiration? You can find a huge collection of awesome community projects over at Awesome IPFS. IPFS has a bustling community of designers, developers, writers, and activists who are all helping to improve the project. You can join in by attending a local meetup, helping out at a conference, chatting online through Matrix channels , or joining a discussion in the IPFS forum (opens new window) .

These documents define the architectural principles that IPFS is built upon, and can be used as tools to evaluate implementations and applications of IPFS. Meta contains all the non-technical documents that conspire to make the standards project work: what the core values are, what the governance model is, how to produce documents, etc.

IPFS Gateway acts as a bridge between traditional HTTP clients and IPFS. Through the gateway, users can download files, directories and other IPLD data stored in IPFS as if they were stored in a traditional web server. IPFS basic primitive is an opaque block of bytes identified by a CID. CID includes codec that informs IPFS System about data format: how to parse the block, and how to link from one block to another.

The most popular data formats used by IPFS Systems are RAW (an opaque block), UnixFS (filesystem abstraction built with DAG-PB and RAW codecs), DAG-CBOR / DAG-JSON , however IPFS ecosystem is not limited to them, and IPFS systems are free to choose the level of interoperability, or even implement support for own, additional formats. A complimentary CAR is a codec-agnostic archive format for transporting multiple opaque blocks.

The InterPlanetary Naming System (IPNS) is a naming system responsible for creating, reading and updating mutable pointers to data. InterPlanetary Improvement Proposals (IPIP) are an orderly mechanism to consider changes to the IPFS specification. They are not changes to the specification itself, but their approval leads to a change in the specification.

New to IPFS or the distributed web? Here's where to get started on understanding the key ingredients in what makes IPFS work. Because IPFS is a system that hopes to change how we use the Internet, it comes with many new concepts! This section aims to get you up to speed quickly. Want the basics in theater mode? Check out these helpful videos for an overview of how IPFS works with files and the overall data lifecycle in the d-web.

Get inspired by usage ideas, explore examples of IPFS implemented in the wild, and dig deeper with case studies on applications and projects in which IPFS plays a crucial role. Referring to files by their content, not their location, is one of the most powerful concepts within IPFS. Learn why with explainers on: Sharing files between peers is incredibly powerful âII and has many nuances! Learn about file-sharing paradigms and tools: IPFS aims to be the future of the internet, but it still needs to play well with today's Web. Here are some ways to do just that: Want a more in-depth look into the decentralized web? Here are a few papers that are useful for understanding IPFS, whether it be understanding the IPFS spec itself or the background for the web, protocols, hashing, and so on. Read the papers âII We're adding more documentation all the time and making ongoing revisions to existing docs, but if you don't see what you need, please file an issue (opens new window) to let us know! We also recommend visiting the IPFS forums (opens new window) for support and discussion with IPFS enthusiasts and experts worldwide.

Internet runs on location-based addressing, when you visit a website, your browser asks a server at a specific IP address for a file at a specific path. It works, but it creates a fundamental vulnerability: the file only exists as long as that server exists. Change the server, break the link. Take the server down, lose the file. IPFS — the InterPlanetary File System — takes a different approach. Instead of asking “where is this file?”, it asks “what is this file?”. The answer is a cryptographic hash called a Content Identifier (CID). Share the CID, and anyone on the IPFS network can retrieve the file from whichever peer happens to have it.

This guide walks through the practical steps of sharing files on IPFS, explains the underlying mechanics, and compares IPFS-based sharing with traditional methods like HTTP downloads, BitTorrent, and cloud storage links. IPFS is a distributed, peer-to-peer protocol for storing and sharing files. Think of it as a single, global filesystem that every peer contributes to and can access — without a central server.

This is location-based: the server at example.com has a file at the path /images/photo.jpg . If the server goes down, the file is unreachable. If someone modifies photo.jpg , you can’t tell — the URL is the same. That string — QmXo...6uco — is the Content Identifier (CID) , a cryptographic hash of the file’s content. It’s generated using the SHA-256 algorithm. Two properties make this powerful: 4. Practical Deployment, Analysis & Case Studies An IPFS node is simply a machine running IPFS software and connected to the network. When you upload a file to IPFS: If your node goes offline, the file may become unreachable — unless another node has pinned it. Pinning tells your node to keep a file and serve it to others. Services like Pinata, Filebase, and Web3.storage (now Storacha, covered in a previous article) offer pinning as a service.

Note: Gateway links are convenience only. The gateway provider can block or throttle access. For true decentralization, use the CID directly. CIDs change when files change. IPNS assigns a mutable pointer (a peer ID) that you can update to point to a new CID while keeping the same shareable identifier.

Now share /ipns/k51qzi5uqu5d... instead — you can repoint it later without breaking links. By default, your file is only available while your node is online. For permanent availability: IPFS is a public network by default. Anyone with the CID can retrieve the file. It’s not encrypted at the protocol level. This is a critical point that beginners often miss: IPFS provides content addressing and decentralization, not privacy. If you’re sharing sensitive documents, always encrypt before uploading.

Availability requires pinning. IPFS is not a permanent storage solution out of the box. If nobody pins your file, it disappears when your node goes offline. You need a pinning strategy (self-hosted or paid service). No built-in access control. IPFS is public. If you need private sharing, you must add encryption on top. This adds complexity for non-technical users.

Gateway centralization. Many users access IPFS through HTTP gateways (ipfs.io, cloudflare-ipfs.com). This reintroduces the centralization IPFS was designed to avoid. Always prefer direct node connections when possible. CID management. CIDs are long and unfriendly. IPNS helps, but the ecosystem around human-readable naming (ENS, DNSLink) is still maturing.

Performance. First-time retrievals can be slow if no nearby peer has the content. Content discovery over the DHT (Distributed Hash Table) adds latency compared to a CDN hit. Gautham has been in the Blockchain and Web3 space for more than a decade, working with multiple publications as an editor while consulting for various projects in product design, content, public relations and marketing space.

As a programmer on a journey to master different technologies, there’s nothing more satisfying than learning how to build decentralized solutions. One such technology that's gaining traction is IPFS (InterPlanetary File System), a protocol for creating distributed, peer-to-peer networks for storing and sharing files. Today, I’ll walk you through running your own IPFS node, uploading files, and ensuring they’re available across the global IPFS network.

IPFS is a decentralized system designed to make the web more resilient by spreading content across multiple nodes instead of relying on a central server. In IPFS, every file is identified by a CID (Content Identifier), a unique cryptographic hash. This CID is crucial for retrieving the file from the IPFS network. Before we dive into running your node, let’s first cover the basics of installation and initialization. If you're already familiar with setting environment variables and command-line tools, this will feel straightforward.

First, you’ll need to install Kubo (formerly called go-ipfs), the reference implementation of the IPFS protocol. Follow these steps: Download IPFS and unzip the files to a directory, e.g., C:\Users\YourName\kubo. Add the Kubo binary directory to your system’s PATH environment variable: This command creates a local repository (by default in C:\Users\YourName.ipfs) and generates a peer identity. Your node is now ready to connect to the network.

You’ll see your node connect to other peers in the network, and the WebUI will be available at http://127.0.0.1:5001/webui . Once your node is running, you can start adding and pinning files to make them available on the IPFS network. You can do it via WebUI http://127.0.0.1:5001/webui and via console - see below: When you add a file to your local node, it automatically gets pinned. Pinning ensures the file stays on your local node even if it's requested by others. The great part? You can use the WebUI to manage pins, making it user-friendly to see the status of your pinned files.

5. Performance Evaluation & Extended Technical Observations Once you have the CID, you can access your file from any IPFS gateway. For example, let’s say the CID of your file is QmWS2n1SihYJ9eDSGhxQUDo2zCdfk1zRQjXq43jsywjYB2. When you first add a file, it might not be immediately available from public gateways. This is because public gateways need to discover your file through the distributed network. You may need to wait a bit, or try the following: Keep Your Node Online: If your node is offline, public gateways won't be able to fetch the file. Once your file becomes widely available, though, it should persist on the network, even if your node goes offline.

Now let's review the possible practical use of IPFS in implementing the practical thing. Here is for example the post blog that doesn't need any server at all. I place the interface page on netlify , You can also save it web page locally (just right on the page - select "save as" - and select "Webpage, completely". That it, then just open the page and it is also is ready to fetch post data from IPFS.

Learning how to run your own IPFS node and contribute to the decentralized web is a great step in mastering distributed technologies. While it may seem complex at first, running your own node provides you with full control over how your files are stored and shared. Experiment with adding more files, pinning them, and accessing them through different gateways. In time, you’ll appreciate the resilience and innovation that IPFS brings to the web! IPFS (InterPlanetary File System) is a protocol and peer-to-peer network for storing and sharing data in a distributed file system .

“Step-by-step guide to install, configure, and use IPFS (InterPlanetary File System) for decentralized file storage and sharing, with demo commands, screenshots, and CID-based file retrieval.” The InterPlanetary File System (IPFS) has significantly transformed data storage and retrieval, offering decentralized solutions for managing data. However, a gap exists in its ability to support secure data sharing. This project introduces a novel scheme for secure, flexible, and decentralized data sharing in IPFS, leveraging blockchain technology and smart contracts.

Conducted in the Polygon test network Mumbai, our tests validate the performance and efficiency of the system. The results demonstrate the achievement of our goals - confidentiality, flexibility, and decentralization, at an affordable cost. We welcome contributions from the community. Please read our contributing guidelines before submitting your pull requests. Developed as part of research on decentralized data sharing systems. For more details, refer to the accompanying research paper.

IPFSdatasharing: A secure and decentralized data sharing system on IPFS, using blockchain and smart contracts for enhanced data confidentiality and access control. IIIIIIIIIPFSIIIIIIIIIIIIIIIIIIIIIIIIIIIIII A decentralized file-sharing application built on top of IPFS (InterPlanetary File System) and Ethereum Blockchain to enable secure, trustless, and transparent sharing of digital files .

This system ensures data integrity, tamper resistance, and access control without relying on centralized servers — providing a modern solution for privacy-conscious individuals and organizations. In the modern era of cloud computing, accessing files from anywhere has become easy — but data security and trust remain major concerns. While encrypting files before uploading can enhance privacy, it still requires trusting third-party cloud providers and makes secure sharing among users difficult.

The Secure File Sharing System leverages blockchain and IPFS to solve this problem. It ensures that: A blockchain is a distributed ledger maintained by a network of peers. Transactions are validated through cryptographic mechanisms and recorded in immutable blocks. The first major blockchain, Bitcoin , introduced the concept of a decentralized ledger verified by miners using a Proof-of-Work (PoW) mechanism. Later, Ethereum extended blockchain functionality by introducing smart contracts — programmable logic that automates trust-based operations without intermediaries.

While blockchain provides data immutability, it’s not suitable for storing large files due to storage and transaction costs. Hence, a decentralized storage layer like IPFS is introduced. IPFS is a peer-to-peer distributed file system designed for content-addressed storage and efficient file distribution . Each file is identified by a unique cryptographic hash , which acts as its address. It offers several key components: Together, these features ensure scalability, redundancy, and immutability in distributed storage.

Harvested Online Documentation & Reference Sources • https://en.wikipedia.org/wiki/InterPlanetary%20File%20System • https://en.wikipedia.org/wiki/Decentralized%20web • https://en.wikipedia.org/wiki/Anna%27s%20Archive • https://docs.ipfs.tech/ • https://docs.ipfs.tech/concepts/how-ipfs-works/ • https://docs.ipfs.eth.link/ • https://specs.ipfs.tech/ • https://docs.ipfs.eth.link/concepts/ • https://blockcritics.com/blog/2026/05/07/how-to-share-files-on-ipfs-a-practical-guide-to-decentralized-file-sharing/ • https://dev.to/mibii/how-to-run-your-own-ipfs-node-and-share-files-o8j