From Vision to the Next Chapter

17 min read

Publication date: December 27, 2024

From Vision to the Next Chapter: Shaping the Logos Project

The vision of the Logos Project goes beyond delivering just a technological solution; it aims to establish an ecosystem where the community becomes the focus, fully embodying the ethos of FOSS (Free and Open Source Software) and Web3. Creating a solution aligned with Web3 and FOSS philosophies inherently requires a commitment to the principles of freedom, fairness, and shared progress.

Web3 emerged from a spirit of rebellion against large corporations and centralized power, embracing values like decentralization, user sovereignty, and transparency. Yet, as big tech companies begin adopting distributed ledger technologies (DLTs), they often build closed networks with centralized control—practices deeply entrenched in the Web2 era. This fundamentally contradicts the revolutionary ideals of Web3. Simply utilizing blockchain technology does not inherently result in a Web3-native solution or adherence to its values.

To ensure Web3's success as the next stage in internets evolution, it is essential to provide future-ready and sustainable solutions that align with the ethos of Web3 and FOSS. Only by adhering to these principles can Web3 truly realize its transformative potential.

Getting on the Same Page

First, it is important to clarify that while Web3 is referred to as the next evolution of the internet, neither the World Wide Web (WWW) nor the Web3 are synonymous with the Internet. The internet encompasses a vast array of services and protocols operating on different layers. The most well-known and used service is the World Wide Web, which uses the HTTP protocol and operates on the application layer of the internet. Similarly, there are other services that operate on this layer, such as email (SMTP/IMAP/POP3), messaging (XMPP/SIP), file transfer (FTP/SFTP), streaming (HLS/DASH/RTP), peer-to-peer networks (BitTorrent/Tor), and many others. I will not dive into technical models like TCP/IP or OSI here, but it is important to clarify that most of the Web3-native protocols and the WWW protocols, operate on the application layer.

At its core, the internet is the physical and logical infrastructure that supports all these services and protocols operating on different layers.

Generaly, the term Web2 is largely synonymous with the World Wide Web (WWW). The Web2 era shaped the evolution of the WWW, characterized by dynamic content, interactivity, and centralized platforms. Web3 on the other hand encompasses many protocols that go far beyond HTTP(S), serving diverse functions and purposes.

Web3 is not merely an evolution of the WWW but a paradigm shift toward a more decentralized internet.

While Web2 (and the WWW) heavily relies on a unified structure (HTTP/HTTPS) and centralized servers, Web3 leverages a variety of protocols that work together to enable different aspects of a more decentralized internet.

In Web3, alongside traditional protocols like HTTP(S), a new generation of protocols is being developed and implemented to enable decentralized applications and systems. A prominent example is the IPFS protocol, which introduces a content-addressed approach to data distribution. Instead of referencing data by location (e.g., a URL pointing to a specific server), IPFS identifies content by its cryptographic hash. This enables flexible data retrieval, where files can be fetched from any node in the network that hosts the desired content, fostering decentralized content delivery.

Unlike traditional client-server communication, protocols like Libp2p provide dynamic peer-to-peer communication capabilities. Libp2p handles critical functions such as peer discovery, routing, and secure data transfer, allowing networks to operate without reliance on centralized entities. Similarly, ENS (Ethereum Name Service) replaces the traditional hierarchical DNS system by mapping human-readable names to blockchain addresses, creating a decentralized naming system suited for Web3 applications.

Protocols like the IBC (Inter-Blockchain Communication Protocol) further expand the Web3 ecosystem by addressing interoperability. They create frameworks for independent blockchains to seamlessly exchange data and assets, paving the way for a multi-chain future where blockchains can cooperate without central intermediaries.

In Web3, there are many different protocols that serve various purposes in diverse ways. For this reason, it is important to note that blockchain networks like Ethereum, Polkadot, Cardano, and others rely on multiple protocols to operate effectively. Many of these networks developed and implemented their own protocols for specific solutions required by the network, but they also adopt established protocols, such as the previously mentioned Libp2p, whose implementations are already available.

Although the WWW and Web3 cannot fundamentally be equated with the Internet itself, they are nevertheless important components of it. By leveraging decentralized protocols, Web3 offers the potential to make the Internet as a whole more decentralized.

The Vision

Now that we're aligned and on the same page, let me reiterate the core vision. At its heart, it's about shifting from operating physical hardware by data centers to a community-driven model. Through the Web3 paradigm and its focus on decentralized protocols, this vision becomes not only possible but attainable.

The provision of physical hardware components necessary for running Web3-native infrastructure, such as blockchain nodes (L0s,L1s,L2s), will be managed by the broader community. Through the Logos Chain and the utilizing of decentralized protocols, this can be achieved in a secure and trustless manner.

Data center providers have established themselves and achieved success by presenting themselves as entities worthy of trust and promoting this as their core value. However, with Web3, technological advancements have made trust unnecessary. Previously, when hosting something in the cloud, users had to trust that the hardware was secure and that no one but themselves could access their data. Now, we no longer need to rely on trust and hope—we can prove and verify.

This shift has made the community-driven model for the provision of computational and storage hardware not only viable but also highly efficient and secure.

The Logos Project aims to empower the broader community by providing the opportunity to participate in building the foundational physical infrastructure for Web3 without requiring extensive technical knowledge. Most individuals nowdays already possess the basic understandings, needed to contribute their hardware, especially when the process is automated.

What data centers currently provide—and often charge exorbitant fees for—can instead be offered by community members on a fair basis. This aligns with the principles of the project, contrasting with the overpriced services of most cloud providers, which do not reflect the ethos of fairness and accessibility.

As I mentioned at the beginning of this article, the Logos Project is more than just a technological solution — it is an initiative aimed at creating a more independent, equitable, and trustless internet. Achieving a fully decentralized and independent internet requires more than just technology and protocols; it demands a fundamental shift in perspective and approach.

The Logos Network and the sub0layer

I won't dive too deeply into the details here; the aim is simply to offer a fresh perspective, building on the clarity provided in the chapter Getting on the Same Page.

The Logos Network is designed as a decentralized physical infrastructure network that is provisioned, operated, and governed through a trustless, resilient, and verifiable model built on decentralized protocols.

The network itself comprises two main components: the Distributed Virtual Computing Infrastructure (DVCI), which redefines the traditional centralized data center paradigm, and the Logos Chain, responsible for securely anchoring and validating the state changes of the DVCI.

The DVCIs will be distributed regionally across the globe, functioning as decentralized data centers. Each DVCI will be managed through an OpenStack environment, designed to handle and provision community-contributed hardware.

Participants will have the opportunity to contribute to the network by providing their existing hardware—such as PCs, laptops, or home servers—or by utilizing the Logos Edge Hub, a computational device specifically engineered to operate efficiently and securely in a distributed environment.

The Logos Chain serves as the core of the network, ensuring that everything happening within the DVCIs is managed through the blockchain. This means that on the Logos Chain are all base states of the infrastructure defined, and only validated state changes will affect the DVCIs. This process will primarily be handled through smart contracts.

The Logos Chain is envisioned as a fully public blockchain, designed to achieve optimal privacy by leveraging advanced concepts such as zero-knowledge proofs.

The sub0layer represents the physical layer for Web3 and is, in essence, the result of the Logos Network. While this solution could theoretically support a wide range of internet services, the primary focus of the Logos Project lies in Web3 infrastructure, specifically L0s, L1s, and L2s.

The vision of The Logos Network and the sub0layer.

Let's clarify some things

The first thing that needs to be clarified is that the Logos Network consists of a blockchain network (Logos Chain) and many regional networks of physical devices (DVCIs). The operations of these devices are handled through Web3-native protocols but are not part of the Logos Chain infrastructure itself.

A variety of established protocols, technologies, and principles that are already established will be utilized and adapted for the provision of the network. As we know, there is a wide array of Web3-native protocols that have introduced significant innovations and solutions. The approach of the project is to identify a path towards a framework of protocols and technologies that can serve as a standardized model for implementing Web3-native solutions—one that we will adopt ourselves.

While the abundance of protocols is undoubtedly beneficial, it also presents a challenge. For Web3 to achieve broader adoption, there must eventually be a globally standardized and widely accepted framework.

An important point to emphasize is that networks like Ethereum, Polkadot, ICP, etc. do not share the same focus with the Logos Network. General-purpose blockchain networks like Ethereum and Polkadot are designed to support a wide range of decentralized applications (dApps), smart contracts, and various other blockchain use cases.

In contrast, the Logos Chain—the blockchain component of the Logos Network—is specifically designed to provide and manage physical infrastructure. Its primary focus lies in the decentralized management of computational, storage, and networking resources, rather than catering to a broad spectrum of applications.

Another important aspect is the governance of the network. The Logos Network will be governed by a decentralized governance system functioning as a Decentralized Autonomous Organization (DAO). Upon the release of Network version 1.0, all root rights will be transferred to this system, ensuring that neither LogosLabs nor any other entity holds privileged access. The network is designed to operate autonomously, with the community assuming full control.

An important clarification lies in the distinction between cloud providers like AWS, Azure, and GCloud, and data centers with physical hardware which, ironically, are often provided by the same companies, such as Amazon, Microsoft, and Google. Although the terms "data center" and "cloud provider" are often used interchangeably, they are fundamentally different. Data centers focus on provisioning and networking the physical hardware itself. Cloud providers, on the other hand, build platforms and services on top of this hardware, making them accessible and scalable for widespread use.

In the Web3 sphere, many networks offer services similar to those of current cloud providers, but with the advantage of being decentralized, trustless, and mostly community-driven. This approach marks a significant step toward the establishment of Web3-native solutions.

However, even though decentralization has been achieved at the "application layer of the internet", the physical infrastructure remains centralized.

The Logos Project aims to provide a Web3-native solution that offers Web3 services a valuable and fundamental physical infrastructure to run their decentralized networks and protocols—an infrastructure designed to align with the core principles of these approaches.

Abstract depiction of the shift from cloud providers and centralized infrastructure to a Web3-native approach.

Some of you may be curious about the name Logos and its significance, especially since there are already other projects using this name. Well, we're a bit of a group of philosophy nerds. The name was inspired by Heraclitus' concept of Logos, which represents structure and harmony within the ever-changing natural world. We felt it perfectly aligns with our vision of bringing order and coherence to the decentralized infrastructure of Web3. Given how fitting it was for our mission, we simply couldn't imagine naming it anything else.

Evolving Towards the Vision

Since the release of our initial concept paper (opens in a new tab), which outlined a rough proposal, significant progress has been made. The concept and approach have evolved, reflecting a deeper understanding of the project's complexities. While some aspects have changed, the vision remains steadfast. However, the implementation trajectory differs from what was initially envisioned in the original proposal.

It is also important to emphasize that not all components of the network have been fully finalized. These details will be thoroughly addressed with the publication of the technical specification paper.

The initial concept has been archived, as certain aspects could be easily misinterpreted. To provide clarity, we have published numerous blog articles (opens in a new tab), documentation pages (opens in a new tab), and FAQs (Logos (opens in a new tab), DePIN (opens in a new tab)) to better explain the network's approach. However, as the project is in a phase of continuous evolution, it is crucial to stay updated by referring to the latest articles and contributions.

A research paper titled "Enterprise Security in Public Blockchain Networks" was initiated, with its initial version (opens in a new tab) already published. This paper captures the essence of the ongoing research efforts. Notably, the research is closely tied to the technical specifications it aims to support, making their releases interdependent.

An important change regarding the implementation approach was outlined in the article Logos Edge Hubs: Key to Effective Implementation (opens in a new tab), where the background and reasoning were briefly explained. It is important to note that detailed specifications will be included in the technical specification paper, while the blog article provides only a general overview.

One significant change we implemented was a shift in our licensing model. The primary reason for this decision is that the GPLv3 and GFDLv1.3 licenses ensure that the use of our code and documentation aligns with and supports the philosophy of Free and Open Source Software (FOSS). Unlike permissive licenses such as Apache 2.0, which allow code to be incorporated into closed-source projects, GPLv3 mandates that derivative works remain open-source and adhere to the same licensing terms.

At the Web3 Summit in Berlin this year, we engaged with the Web3 community to discuss our vision, sparking new insights and ideas on how to bring it to life. A key topic of discussion was security, particularly the handling of private keys, secrets, and memory safety. These conversations with experts in their respective fields were invaluable, helping us adopt a more pragmatic approach to these critical aspects.

The vision itself has now become clear and well-defined. The overall idea and objectives of the project have been effectively communicated and made accessible to the community. What remains is the development of detailed technical specifications for the network, which will serve as the foundation for its implementation.

The Next Chapter

The next chapter of the Logos Project will focus primarily on delivering the technical specifications. During this phase, most updates will be shared through the development section of our website. These updates will include technical specifications, research findings, and test results, providing transparency and keeping the community informed about our progress.

The specifications will be released step by step, in phases, as their complete development is expected to continue until the end of Q3 2025. The process, which has already begun under the leadership of us (LogosLabs), will also involve experts from various fields. This collaborative approach ensures that the specifications can serve as a single point of truth and any developer can interpret and implement.

With the release of the technical specifications, a Proof of Concept (PoC) will also be made available. The PoC is a critical step to validate that the specifications are not only theoretically sound but also practical and implementable in real-world scenarios. Additionally, following the publication of the technical paper, we will release a Request for Comments (RFC) to invite constructive feedback. This will ensure the specifications are robust and benefit from the collective expertise of the broader community.

In this chapter, the community will have more opportunities to get involved. With more material being published in our repositories, the FOSS community can better support us in various aspects of the project. This brings us to an essential principle that must be fulfilled and aligned with: our unwavering commitment to the philosophy of FOSS.

To reinforce this commitment, several significant changes will take place. These include replacing JavaScript in our web applications, migrating away from GitHub, joining the Free Software Foundation (FSF), etc. These steps underline our dedication to creating an open and transparent ecosystem fully aligned with FOSS principles.

After this chapter is written, we will be ready to start building the Logos Test Network. The community will play a significant role in its provision and providing feedback, contributing to refining and improving the network as it evolves.

Driving Force

The aims of the project are highly ambitious and even intriguing, as they require a paradigm shift that could have significant impacts on society itself.

We are heading toward a future where digitalization will permeate every aspect of our lives. Yet the centralized systems we currently rely on are fundamentally unprepared for this shift. They lack transparency, fairness, and the ability to foster shared progress. They demand trust instead of being trustless, and their unsustainable nature risks undermining the very foundation of our collective digital evolution.

What drives us is the vision of solving these challenges to create a fair and sustainable digital future—a future where people and communities take precedence. A future where data and privacy are respected and protected. A future defined by shared progress, not profit-driven motives.

The Logos Project initiative represents an important step toward realizing this vision. While it is a significant and challenging step, it is both necessary and meaningful.

Now, the choice is ours. If we truly desire this future, we must unite, take action, and make it a reality.

Do you have questions or want to discuss more? Join our discussion on Discord (opens in a new tab)

References:

Home Logos Edge Hubs: Key to Effective Implementation