The InterPlanetary File System (IPFS) plays a central role in Bitxenia’s exploration of peer-to-peer infrastructures.
It provides a decentralized alternative to traditional hosting and storage services, allowing content to be shared and replicated directly between users, without relying on central servers.

Unlike conventional web architectures — where resources are located by their position on a server (URLs) — IPFS identifies data through content addressing.
Each file or block of data is represented by a unique cryptographic hash, ensuring immutability, integrity, and verifiable distribution.

This design enables applications to:

• Eliminate single points of failure and reduce dependence on centralized providers.
• Achieve data persistence through distributed pinning and replication.
• Increase censorship resistance, since content can be retrieved from any peer that stores it.
• Improve transparency and collaboration within community-driven ecosystems.

Together, these features make IPFS a suitable foundation for decentralized, community-owned applications — aligning with Bitxenia’s broader goal of restoring autonomy to digital infrastructures.

Several complementary projects within the IPFS ecosystem extend its functionality and are used throughout Bitxenia’s implementations:

• libp2p — the modular peer-to-peer networking layer that enables node discovery, encryption, and transport abstraction.
• OrbitDB — a distributed database built on top of IPFS, providing mutable state for decentralized applications.
• IPNS — the InterPlanetary Naming System, allowing content addressed by IPFS to be updated dynamically.
• IPFS Cluster — coordinates cooperative pinning and replication of data across multiple nodes.
• ENS (Ethereum Name Service) — optionally integrated for human-readable naming and interoperability.

Building upon the tools and abstractions provided by IPFS, Bitxenia defines two complementary infrastructures that together form the foundation for decentralized applications: the deployment infrastructure and the application infrastructure.

This layer is responsible for hosting and distributing web applications through the IPFS network.
It manages the publication and replication of front-end assets, ensuring that web content remains accessible even without centralized servers.

Within this infrastructure:

• Files are stored and pinned across collaborative IPFS clusters to ensure persistence and redundancy.
• The InterPlanetary Naming System (IPNS) provides dynamic addressing, allowing sites to be updated while preserving verifiable links.
• Community-operated nodes collectively maintain availability, enabling a self-sustained hosting mechanism aligned with Bitxenia’s vision of community ownership.

The second layer manages the application logic, shared state, and peer connections among users.
It is the foundation for decentralized systems that require real-time interaction and persistent data, such as collaborative knowledge repositories or peer-to-peer messaging.

This infrastructure leverages:

• OrbitDB as a distributed, peer-synchronized database built on IPFS.
• libp2p for peer discovery, secure transport, and communication.
• Abstractions that encapsulate network complexity, allowing developers to focus solely on application logic rather than low-level IPFS operations.

By separating these layers, Bitxenia establishes a modular architecture that simplifies development and promotes reusability.
Each new application can be deployed over the same foundational components, reducing complexity and ensuring interoperability across decentralized services.

• Deployment Infrastructure — technical implementation of collaborative hosting using IPFS clusters and IPNS.
• Application Infrastructure (AstraDB) — design of a distributed data layer with OrbitDB and libp2p for real-time, community-managed applications.