“We have nothing to lose but the tyranny of centralised governance, its corruption and all of its barbed wire fences.”

— Jarrad Hope & Peter Ludlow, Farewell to Westphalia (2025)

Logos

A Sovereign Technology Stack for Self-Governing Communities

Version 0.1 — Draft [Date TBD]

Contributors: [Authorship model TBD — see open questions] Institute of Free Technology

Epigraph & Frontmatter
The Thesis
The Problem
The Logos Stack: Architecture Overview
Design Principles
The Ecosystem
Positioning in the Lineage
Roadmap and Current Status
Economic Design Overview
What Comes Next — The Documentation Roadmap

1. The Thesis

Sovereign nation states are human technologies. They were designed to solve a specific problem — containing the religious and ideological wars that tore through post-Reformation Europe — and formalized in the Peace of Westphalia in 1648. For nearly four centuries, territorial sovereignty has been the dominant organizing principle of human governance. Like all technologies of that era, it is not the optimal solution available today.

The Westphalian settlement was an achievement. It ended the Thirty Years’ War. It established principles of territorial integrity and non-interference that, at their best, provided frameworks for coexistence between peoples with irreconcilable values. But the model carries structural failures that no amount of reform can address: it kettles people of conflicting values within artificial borders and forces them to fight over who controls the levers of power. It concentrates authority into single points of capture — and those points attract corruption with mathematical predictability. It draws lines on maps and then enforces those lines with violence.

The nation state is not destiny. It is an invention. And it is showing its age.

The cypherpunk movement recognized this decades ago. Eric Hughes declared that privacy is necessary for an open society. Timothy May warned that cryptographic tools would alter the nature of government regulation and the ability to tax and control economic interactions. The Bitcoin whitepaper demonstrated that peer-to-peer electronic value transfer could function without trusted intermediaries. Ethereum extended that vision to programmable agreements.

But the promise remains unfulfilled. Fifteen years after Bitcoin’s genesis block, the infrastructure that was supposed to resist capture is being captured. Ethereum validators comply with OFAC sanctions. Block builders centralize into oligopolies — a single entity constructs nearly half of all Ethereum blocks. Decentralized applications store their data on Amazon Web Services. Users coordinate through platforms that surveil every message. The technology changed; the dependency on coercible infrastructure did not.

Sovereignty requires a complete technology stack — not a single chain, but the full substrate of digital life: communication, coordination, and memory. Each layer must be designed so that no operator, no validator, no service provider can be individually targeted, coerced, or shut down without compromising the integrity of the network as a whole.

This is not a theoretical concern. When the United States Treasury sanctioned Tornado Cash in August 2022, Ethereum validators began censoring transactions. The censorship worked because validator identities are public — the protocol’s design made compliance trivially enforceable. The lesson is not that Ethereum failed morally. The lesson is that any system where infrastructure operators are identifiable is a system where those operators can be coerced.

Logos is the response: a technology stack engineered for communities that refuse to outsource their sovereignty to institutions that may not share their values. Three layers — blockchain for coordination, messaging for communication, storage for memory — composed into a unified system where privacy is a protocol guarantee, not an organizational promise.

The thesis is simple, and it is old: people who cannot communicate freely, coordinate without permission, and preserve their knowledge against censorship cannot govern themselves. The technology to make this possible now exists. What remains is to build it correctly — with the right architecture, the right threat model, and the right values embedded at the protocol level.

This litepaper describes that architecture.

2. The Problem

Existing blockchain infrastructure suffers from three structural vulnerabilities. Each represents a point where the promise of decentralization collapses under real-world adversarial pressure.

Failure Mode 1: Consensus Leader Exposure

In every major proof-of-stake protocol, the set of validators is public. Leader schedules are deterministic or predictable. This means that any state actor, regulator, or sufficiently motivated adversary can identify exactly who is producing the next block — and apply pressure accordingly.

This is not theoretical. Following the Tornado Cash sanctions in August 2022, MEV-Boost relays began filtering transactions to comply with OFAC requirements. At peak censorship, over 70% of Ethereum blocks were OFAC-compliant — not because the protocol required it, but because relay operators and block builders chose compliance over the risk of enforcement. The protocol’s transparency made this choice trivially easy: every participant is identified, every action is attributable.

The fundamental issue is architectural: public validator sets are coercion surfaces. Any protocol that exposes who produces blocks, when they produce them, and what transactions they include is a protocol that can be censored at the infrastructure layer. Adding mixers or privacy tools at the application layer does not solve the problem — it merely moves the coercion target from the validator to the mixer operator, as Tornado Cash demonstrated.

Failure Mode 2: Communication Surveillance

No major blockchain provides censorship-resistant messaging at the protocol level. Users coordinate through centralized platforms — Discord, Telegram, Twitter — where every message is surveilled, accounts can be suspended, and entire servers can be removed.

The consequences extend beyond convenience. When infrastructure operators must coordinate through surveilled channels, their communications become an attack surface. Validator coordination, governance discussions, and incident response all flow through platforms with terms of service that can change without notice and with law enforcement access that is routine rather than exceptional.

The gap is not accidental. Messaging is hard — the combination of privacy, reliability, spam resistance, and decentralization involves fundamental engineering tradeoffs that most protocol teams have chosen not to address. The result is a paradox: networks designed to resist censorship rely on censorable communication channels for their own operation.

Failure Mode 3: Storage Centralization

Decentralized applications overwhelmingly depend on centralized storage infrastructure. Front-ends are hosted on AWS or Vercel. NFT metadata lives on centralized servers or IPFS gateways operated by a small number of companies. Critical application data has single points of failure.

When Cloudflare or AWS experiences an outage, swaths of “decentralized” applications go offline. When IPFS gateway operators receive takedown requests, content becomes inaccessible. The blockchain itself may be censorship-resistant, but the data that applications need to function sits behind infrastructure that is not.

Existing decentralized storage solutions address part of the problem but introduce their own limitations. Filecoin optimizes for raw storage capacity with high hardware requirements. Arweave provides permanence but at the cost of flexibility. Neither offers tunable durability guarantees — the ability to choose precisely how resilient your data needs to be, from ephemeral caching to long-term archival, with cryptographic verification that storage providers are actually preserving it.

The Structural Diagnosis

These three failure modes share a common root: existing blockchain infrastructure was designed for transparency, not for resistance to coercion. Transparency was the original innovation — Bitcoin proved that a public ledger could replace trusted intermediaries. But transparency and resistance to capture are not the same thing. A transparent system is one where anyone can verify. A sovereign system is one where no one can coerce.

Building sovereign infrastructure requires privacy at the protocol level — not as an add-on, not as an application-layer feature, but as a fundamental design constraint that shapes every architectural decision. It requires a complete stack: consensus that hides who proposes blocks, messaging that hides who sends messages, and storage that hides who stores what. Each layer reinforces the others; any gap in the stack undermines the whole.

3. The Logos Stack: Architecture Overview

Logos is a modular technology stack composed of three protocol layers — Blockchain, Messaging, and Storage — unified by a microkernel runtime that allows nodes to dynamically load and compose the components they need. Together, they provide the three capabilities that self-governing communities cannot outsource:

Layer	Capability	Key Innovation
Logos Blockchain	Coordination & settlement	Private Proof of Stake — anonymous block proposers via Cryptarchia consensus + Blend mix network
Logos Messaging	Communication	Privacy-preserving P2P messaging with Rate-Limit Nullifiers (RLN) for spam protection
Logos Storage	Persistent memory	Decentralized file sharing with tunable durability and privacy-preserving retrieval circuits

A node running all three layers provides censorship-resistant computation, communication, and data persistence with no external dependencies.

3.1 Logos Blockchain

A neutral, permissionless settlement layer with anonymous block production.

Logos Blockchain is a proof-of-stake protocol designed around a single architectural constraint: no participant should be identifiable as a block producer, before, during, or after block propagation. This constraint drives every design decision.

Cryptarchia: Private Proof of Stake. Where Bitcoin uses a hash lottery to select block producers (proof of work), Cryptarchia uses a private stake lottery. Stakers hold note-based commitments (analogous to Bitcoin’s UTXO model) and prove their right to produce a block using zero-knowledge proofs — without revealing their identity, their stake amount, or their position in the validator set. One-time leader keys prevent observers from correlating multiple blocks to the same producer.

But anonymous leader election alone is insufficient. If block proposals are broadcast from identifiable network addresses, an observer can triangulate producers through traffic analysis. This is why Cryptarchia is paired with the Blend network — an anonymization layer that routes all block proposals through cryptographic circuits, severing the link between a proposal’s content and its origin.

The combination — ZK-proven leader election plus mix-network proposal routing — makes Logos the first proof-of-stake protocol where block producers are anonymous (not merely pseudonymous) even under network-level surveillance.

Security model. Cryptarchia operates under an honest-majority assumption — security holds as long as the majority of stake is honest. This is closer to Bitcoin’s security model than to BFT protocols (which typically assume at most one-third faulty participants). The tradeoff: probabilistic finality (~18 hours, similar to Bitcoin’s convention of waiting for confirmations) rather than the instant finality of BFT. The benefit: a more permissive participation model with no minimum stake requirements and no slashing — if your node goes down, you miss block rewards, but you lose nothing. This eliminates the coercion surface that slashing creates in other PoS systems.

Channels and Zones. Logos Blockchain does not execute smart contracts at the base layer. Instead, it provides a settlement surface for Zones — independent execution environments that post their state commitments to the blockchain via hash-ordered Channels. Each Zone brings its own virtual machine and transaction model. The contents of Channel inscriptions are opaque binary blobs to the base layer.

This design prevents the MEV (Maximal Extractable Value) centralization that plagues Ethereum, where sophisticated actors extract value by reordering transactions within blocks. Because Logos Blockchain performs zero execution, there is no transaction content to reorder at the base layer.

The Logos Execution Zone (LEZ) is the first Zone built on Logos Blockchain — a privacy-preserving smart contract platform using the RISC Zero zkVM. LEZ features a dual-state architecture: public state (on-chain, auditable) and private state (commitment-and-nullifier model, readable only with viewing keys). The same program bytecode runs in both public execution (on-chain) and private execution (off-chain with ZK proof generation). Applications built on LEZ include private payments, confidential DeFi, and selective disclosure systems where users control exactly how much information to reveal.

3.2 Logos Messaging

Privacy-preserving communication with protocol-level spam resistance.

Logos Messaging descends from Ethereum’s original Whisper protocol — the messaging layer that Gavin Wood envisioned as part of the Ethereum “Holy Trinity” (consensus, messaging, storage) but which was never completed. Logos Messaging realizes that vision with modern cryptographic tools.

The system is built in layers:

Logos Delivery is the transport layer — a decentralized peer-to-peer messaging network that handles peer discovery, protocol selection, topic management, and message routing. It provides a simple developer interface: connect to the network, send messages to topics, subscribe to topics. Nodes operate in two modes: Core (desktop, full participation) and Edge (mobile, lightweight).

Rate-Limit Nullifiers (RLN) solve the spam problem that has plagued every decentralized messaging system. Using zero-knowledge proofs, each participant proves membership in the network and proves they have not exceeded their message budget — without revealing who they are. If a participant exceeds their rate limit, the proof system generates a duplicate nullifier that causes the message to be dropped. No banning, no identity revelation — just cryptographic enforcement of fair usage.

Logos Chat builds on top of Delivery to provide secure conversations: end-to-end encrypted 1:1 messaging using the Double Ratchet protocol (forward secrecy) and Extended Triple Diffie-Hellman (post-compromise security). Group chat via Distributed Messaging Layer Security (DMLS) is in development. Post-quantum encryption is on the roadmap.

The Store protocol addresses a fundamental limitation of peer-to-peer messaging: if you’re offline when a message is sent, you miss it. Store allows nodes to persist and retrieve historical messages, enabling asynchronous communication without centralized servers.

3.3 Logos Storage

Decentralized file sharing with privacy-preserving retrieval.

Logos Storage provides the memory layer of the sovereign stack — the ability to store, retrieve, and share data without relying on centralized infrastructure. The current implementation focuses on decentralized file sharing with a clear path toward incentivized durable persistence.

How it works today: A user publishes a file, receiving a Content ID (CID). The network’s distributed hash table (DHT) locates nodes closest to that CID and publishes a provider list. Downloaders query the DHT, discover providers, and connect directly for transfer. Replication is organic — peers who download content become providers.

Performance: The current implementation achieves transfer rates exceeding 100 MB/s (a 20x improvement over predecessor systems), supports petabyte-scale file sizes, and handles swarms of hundreds of peers.

Privacy-preserving retrieval is the key architectural innovation. File sharing systems leak information at every step: who published what, who downloaded what, which IP addresses accessed which content. Logos Storage addresses this through a circuit-based architecture inspired by Tor’s onion routing:

Entry points — the publisher creates a circuit and publishes the entry point as the provider, hiding the publisher’s identity
Exit points — the downloader creates a separate circuit
Rendezvous nodes — a meeting point where entry and exit circuits exchange data without either party knowing the other’s identity

This architecture ensures that no single node in the network can link a file’s publisher to its consumers.

Toward incentivized durability: Organic replication provides no persistence guarantees — if no one cares about a file, it disappears. The longer-term roadmap includes incentivized durable persistence: users can instruct the network to replicate and store data, compensating storage providers and penalizing non-compliance. The non-private case is well-understood; fully anonymous incentivized storage remains an active research area.

3.4 Logos Core: The Modular Runtime

An operating system for the sovereign stack.

The three protocol layers are unified by Logos Core — a microkernel runtime (liblogos) that manages module loading, process isolation, and inter-process communication. The analogy is deliberate: Logos Core is to the sovereign stack what a kernel is to an operating system.

Modules are independently built, packaged (as .lgx archives), and distributed via a decentralized package manager
Process isolation ensures that a crash in one module does not bring down the system
Inter-process communication via standardized APIs allows modules to interact seamlessly
Multi-language support — modules can be written in Nim, C++, or JavaScript with a unified API pattern

Logos Basecamp is the default distribution — a user-facing application that ships with Logos Core and a curated set of default modules (accounts, wallet, chat, blockchain node management, storage, package manager). Additional modules can be discovered and installed through the built-in package manager.

The modular architecture means Logos is not a monolith. Communities can compose the exact set of capabilities they need. A community that needs only messaging and storage can run those layers without the blockchain. A project that needs only coordination can run the blockchain layer without storage. The full stack is greater than the sum of its parts, but each part is independently useful.

4. Design Principles

Every technical decision in the Logos stack is constrained by six principles. These are not aspirations — they are architectural requirements that shape what gets built and what gets rejected.

1. Privacy by default. Users should not need to opt into privacy. The base layer must protect participant identity as a protocol guarantee. Example: Cryptarchia does not offer an “anonymous mode” — all block production is anonymous. There is no way to produce a block that reveals your identity, even voluntarily, at the consensus level.

2. Political neutrality. The protocol must serve communities with irreconcilable values without privileging any of them. Infrastructure cannot have opinions. Example: Logos Blockchain performs zero execution at the base layer — it cannot censor transactions based on content because it cannot inspect content. Zones bring their own rules; the settlement layer is indifferent.

3. Resistance to coercion. The system must remain operational even when individual operators are compromised, coerced, or shut down. Example: No slashing in Cryptarchia — a compromised validator’s worst-case outcome is missing block rewards, not losing their stake. This eliminates the leverage that slashing-based systems give to coercive actors.

4. Modularity. No component should assume the presence of any other. Each layer must be independently useful and independently replaceable. Example: Logos Core’s module system allows any protocol layer to be loaded, unloaded, or replaced without affecting the others. A future consensus mechanism could replace Cryptarchia without requiring changes to Messaging or Storage.

5. Minimal trust assumptions. Prefer cryptographic guarantees over economic incentives. Prefer economic incentives over social coordination. Prefer social coordination over institutional trust. Example: RLN spam protection uses zero-knowledge proofs rather than reputation systems — a new participant has the same spam protection as a long-standing one, with no trusted third party required.

6. Honest about limitations. The documentation, the roadmap, and the protocol itself must clearly distinguish between what exists, what is planned, and what is uncertain. Example: This litepaper explicitly labels features that are not yet committed (Section 7) and defers detailed economic modeling to a dedicated document (Section 8).

5. The Ecosystem

Logos is developed within the Institute of Free Technology (IFT) — a fully distributed organization of 220+ contributors building public goods for digital sovereignty. IFT provides the organizational substrate; the work is the evidence.

Shipped products

The IFT ecosystem has delivered production systems that collectively demonstrate the engineering capability behind Logos:

Status — a blockchain-native messaging application with millions of users. Status is the original application that drove the development of the messaging stack that became Logos Messaging. It provides real-world validation of the protocols at scale.

Nimbus — an Ethereum consensus client implemented in Nim, designed for resource-restricted environments. Nimbus runs on devices from Raspberry Pis to cloud servers, demonstrating the team’s competence in protocol engineering and resource-efficient systems design. Nimbus validates Logos’s commitment to low hardware requirements — if it runs on a Raspberry Pi, it cannot be captured by requiring expensive infrastructure.

Keycard — an open-source hardware security module for cryptocurrency key management. Keycard demonstrates the team’s ability to ship physical products and manage the full stack from silicon to software.

Vac — a research organization producing peer-reviewed academic work, including the Waku IEEE paper (2022). Vac provides the formal research foundation for Logos’s protocol designs, bridging the gap between academic rigor and production engineering.

Community infrastructure

Logos Circles — a network of local community chapters providing grassroots infrastructure for the sovereign-tech movement.

Development activity

Testnet status

Logos testnet v0.1 launched in February 2026 with all three protocol layers integrated. The testnet supports:

Node start/stop and wallet inspection
Bitcoin-style UTXO transfers via Cryptarchia consensus
Ephemeral 1:1 encrypted chat via Logos Chat
Decentralized file sharing via Logos Storage
Logos Execution Zone with token programs, AMM, and account management
Seven productive devnets completed; the longest ran continuously for four days
Nodes from all core contributors running on Raspberry Pis

6. Positioning in the Lineage

Logos does not exist in a vacuum. It builds on — and diverges from — the work of every major protocol project that came before it. An honest accounting of that lineage is more credible than pretending to be unprecedented.

Bitcoin

Logos shares Bitcoin’s security model (honest-majority assumption), its UTXO-like state representation (note-based commitments in Cryptarchia), and its cypherpunk ethos. Bitcoin proved that a decentralized network could resist capture for over fifteen years. Logos extends that vision beyond money into complete sovereign infrastructure — communication, coordination, and memory — while inheriting Bitcoin’s conservative security philosophy: no slashing, no minimum stake, probabilistic finality over BFT assumptions.

What Bitcoin got right: Minimal design. Resistance to capture through simplicity. Honest-majority security that has held for over a decade. Where Logos diverges: Bitcoin’s transparency is a feature for money but a vulnerability for infrastructure. Block producers in Bitcoin are pseudonymous at best. Logos makes them anonymous.

Ethereum

Ethereum proved that programmable agreements could function on a decentralized network and catalyzed an ecosystem of unprecedented scale. But Ethereum’s design made a fundamental tradeoff: transparency over privacy. Public validator sets, deterministic leader schedules, and MEV extraction have created centralization pressures that undermine the original promise.

What Ethereum got right: Programmability. Composability. The vision of a world computer. Where Logos diverges: The privacy gap. Logos addresses the structural vulnerability that allows Ethereum validators to be coerced into compliance — not by adding privacy as an application-layer feature, but by making anonymity a protocol-level guarantee.

Filecoin / Arweave

Both projects advanced decentralized storage, proving that economic incentives can sustain distributed data persistence. Filecoin optimizes for raw capacity with proof-of-replication; Arweave pursues permanence through an economic endowment model.

What they got right: Proving that decentralized storage markets can function. Where Logos diverges: Logos Storage prioritizes durability over raw capacity — tunable guarantees that let users specify exactly how resilient their data needs to be. Lower hardware requirements expand participation. Privacy-preserving retrieval circuits ensure that storage providers cannot surveil access patterns.

Urbit

Urbit is the closest philosophical sibling — both projects pursue digital sovereignty as a first principle, both envision a complete stack (not just a chain), and both take seriously the idea that technology embeds political choices.

What Urbit got right: The full-stack thesis. The insistence that sovereignty requires owning every layer. Where Logos diverges: Architecture. Urbit is monolithic and proprietary; Logos is modular and open-protocol. Urbit invented its own language, VM, and networking stack from scratch; Logos builds on battle-tested foundations (libp2p, established cryptographic research, the Ouroboros family of PoS protocols). Urbit’s address space is a fixed-supply land grab; Logos has zero stake requirements for participation.

7. Roadmap and Current Status

What exists today (Q1 2026)

Cryptarchia consensus — implemented and running on testnet with anonymous block production via Blend network
Logos Execution Zone — dual-state (public/private) smart contracts with token programs, AMM, and account management live on testnet
Logos Messaging — ephemeral 1:1 encrypted chat operational; Logos Delivery transport layer integrated
Logos Storage — decentralized file sharing with 100+ MB/s transfer rates
Logos Core — modular runtime with 13+ modules, process isolation, multi-language SDK
Logos Basecamp — alpha v0.1.3, user-facing application with built-in package manager
Testnet v0.1 — all three protocol layers integrated; running on commodity hardware (Raspberry Pi)

Near-term milestones

Testnet v0.2 — group chat via DMLS, Reliable Channel API with delivery guarantees, cross-zone messaging, decentralized sequencing, post-quantum encryption research
Public testnet phases — progressive opening of the testnet to external participants
Incentivized testnet for Storage — testing economic mechanisms for durable persistence

Medium-term

Mainnet target: early 2027

What is explicitly NOT committed

The following are areas of active research or planning that have not been committed to specific timelines:

Token launch specifics (timing, distribution model)
Data Availability at the base layer (active research, not in v1.0 scope)
Fully anonymous incentivized storage (significant open research problem)
Specific TPS or throughput targets (the architecture prioritizes sovereignty over throughput)

8. Economic Design Overview

The Logos economic design creates reinforcing incentive loops across all three protocol layers. Detailed tokenomics — vesting schedules, emission curves, and formal game-theoretic analysis — will be published in a dedicated economics document. This section outlines the structural logic.

Three-component economic flywheel

Blockchain security budget. Cryptarchia’s block rewards incentivize stake participation, securing the settlement layer. Because there is no slashing, the economic risk of participation is limited to opportunity cost — stakers cannot lose their principal. This lowers the barrier to entry and broadens the validator set, increasing decentralization.

Storage marketplace. Users pay storage providers to persist data with specified durability guarantees. Providers compete on price and reliability. The marketplace creates organic demand for the settlement layer (payments flow through Logos Blockchain) and for messaging (coordination between storage clients and providers).

Messaging incentivization. Core messaging nodes that relay traffic and provide Store services are compensated for their bandwidth and storage contributions. RLN membership — the right to send messages at a given rate — is allocated through the Logos Execution Zone, creating demand for LEZ transactions.

How privacy reinforces the economic model

Privacy-preserving staking (via Cryptarchia’s note-based commitments) prevents the targeting of large stakers by adversaries. In transparent PoS systems, the largest stakers are identifiable and become high-value targets for coercion — comply with sanctions or risk enforcement action against known addresses. Cryptarchia’s privacy eliminates this attack vector, allowing participants to stake larger amounts with confidence that their participation cannot be used against them.

9. What Comes Next — The Documentation Roadmap

This litepaper is the first in a series of documents that will provide progressively deeper technical specification of the Logos stack.

Forthcoming documents

Document	Scope	Target
Logos Umbrella Whitepaper	Comprehensive integrated architecture, threat model, security analysis, formal economic design	Litepaper + 6–12 months
Logos Blockchain Technical Specification	Cryptarchia consensus, Blend network, Channels & Zones — formal specification	Independent timeline
Logos Storage Technical Specification	Durability engine, erasure coding, ZK storage proofs, marketplace design	Independent timeline
Logos Messaging Protocol Specification	Protocol family, RLN, Store protocol, adaptive nodes	Independent timeline

Existing published work

The Logos stack is not starting from zero. Substantial technical documentation already exists:

Waku IEEE Paper (2022) — peer-reviewed academic publication on the messaging protocol family
Codex Whitepaper — technical specification of the decentralized durability engine
Cryptarchia Specification — formal description of the private proof-of-stake consensus mechanism
Logos Blockchain V1 Specifications — protocol-level specification of the testnet implementation
Farewell to Westphalia (Hope & Ludlow, 2025) — book-length philosophical foundation
press.logos.co — ongoing technical writing on architecture, privacy, and design rationale

Open resources

Logos Roadmap: roadmap.logos.co
Specification Hub (LIPs): lip.logos.co
RFC Index: github.com/vacp2p/rfc-index
Research Forum: [TBD]
GitHub: github.com/logos-co

This litepaper is version 0.1. It will be updated as the protocol evolves. The version history will be maintained publicly.

Logos Assembly

Explorer

Logos Litepaper — Draft v0.1