Logos Tech Stack
The Logos tech stack is designed around three basic needs: communication, archiving, and agreement. Decentralised systems for these needs have existed before, but privacy has often been the missing piece.
Logos builds on established technologies rather than reinventing them. The stack combines proven foundations with new work around privacy, unlinkability, anonymity, self-sovereignty, and scalability.
THREE ANCIENT NEEDS
The internet has long had decentralised answers to three basic needs:
• Communicate - Usenet and early email
• Archive - Napster and BitTorrent
• Agree - banks and platforms, followed by Bitcoin and programmable blockchains
These systems demonstrated that decentralised infrastructure could work at scale. Privacy, however, was often left unresolved.
Logos aims to build these capabilities with privacy built into the underlying infrastructure.
STANDING ON GIANTS
Logos uses existing technologies and research wherever they provide a strong foundation.
Examples include:
• Ouroboros
• Solana's data model
• RISC Zero and its ZKVM
• libp2p for peer-to-peer networking
The focus is on extending these foundations with capabilities that are important for a parallel society:
• Privacy
• Unlinkability
• Anonymity
• Self-sovereignty
• Scalability
The goal is not to rebuild everything from scratch, but to build the missing pieces needed to make decentralised infrastructure practical and usable.
MESSAGING
Logos Messaging provides peer-to-peer communication built on libp2p.
It is designed as a general network for sending data, rather than a system tied to one particular application. This means it can support:
• Human-to-human communication
• Machine-to-machine communication
• Bots and automated systems
• APIs and other applications
Messaging is designed to work on phones as well as servers. It also addresses a fundamental problem for decentralised communication: rate limiting without requiring users to reveal their identity.
Key components include:
• libchat - encrypted conversations and groups
• libp2p-mix - a mixnet-based approach that helps hide who is communicating with whom
Encryption protects the content of a conversation, but does not necessarily hide the relationships between participants. Messaging therefore also focuses on preventing the network from building a social graph around users.
STORAGE
Logos Storage allows data to be published and retrieved without relying on a particular central server.
It uses content addressing:
• Data is identified by a hash of its contents
• The identifier can be used to retrieve the same data
• No particular server needs to be the trusted source
Privacy is also applied to both sides of the exchange.
Publisher and downloader unlinkability means that:
• Someone serving data does not necessarily reveal that they are serving it
• Someone retrieving data does not necessarily reveal what they are retrieving
• Users can interact with data without exposing the relationships around that data
This matters because sometimes the sensitive action is not publishing information, but accessing it.
BLOCKCHAIN
Logos Blockchain provides decentralised agreement and consensus.
It has two main layers:
BEDROCK
Bedrock provides the underlying consensus and data availability layer.
Two key technologies are:
• Cryptarchia - private leadership election
• Blend - helps hide who proposed a block
This allows participants to contribute to consensus without necessarily revealing that they are doing so.
ZONES
Zones are lightweight chains that run on top of Bedrock. They provide the environment where decentralised applications and programs can run while relying on Bedrock for underlying consensus and data availability.
The first zone is the Logos Execution Zone (LEZ).
LEZ uses the RISC Zero ZKVM to support both public and private accounts within the same environment.
This allows:
• Public and private transactions
• Private accounts with encrypted data and proofs
• Programs that can work across both public and private states
The result is a more flexible environment for building applications that need both transparency and privacy.
BASECAMP
Logos Basecamp is the user-facing application that brings the different parts of the stack together.
It allows users to:
• Install infrastructure modules
• Install and run applications
• Choose where modules come from
• Run a Logos node
Basecamp is somewhat comparable to a browser because it hosts applications. The difference is that modules are installed locally, signed, and sourced according to the user's choices.
Getting the infrastructure into the hands of users is essential. Infrastructure that nobody can actually install and use remains a research project rather than a functioning part of a parallel society.
RUNNING A NODE
Participation in the Logos network can include running a node.
A node can contribute in different ways:
• Blockchain - participate in consensus
• Messaging - carry network traffic
• Storage - help provide decentralised data availability
• Basecamp - run these components locally
A node can also become an always-on peer that provides services in the background.
Nodes can be run through Basecamp or using the command-line tool logosctl.
HARDWARE
Running a node does not require datacenter hardware.
Possible hardware includes:
• Raspberry Pi 5 with 64 GB storage
• Old laptops
• Second-hand or ex-office desktops
• Other inexpensive machines running recent Linux
The aim is simple: a network that ordinary people can participate in, rather than infrastructure that requires access to a datacenter.
WHERE TO GO NEXT
The Logos stack is still being developed. Activist Builders can contribute by building, testing, running nodes, and experimenting with applications.
Useful resources:
• Logos Documentation — docs.logos.co — tutorials and technical documentation
• Logos Roadmap — roadmap.logos.co — current and upcoming development
• Download Logos Basecamp — install Basecamp and start running applications
The stack is not finished. That is part of the point: Activist Builders are here to help build, test, and use it.