Logos Dev Update: January 2026
Your monthly update on the development of the Logos technology stack.
Logos
Under the unified Logos technology stack, we will be providing monthly developer updates on the state of Logos development.
These updates will encompass all elements of the Logos technology stack, including Storage, Messaging, and Blockchain, as well as other projects such as Logos Core and AnonComms.
We are aiming to provide developers with a brief snapshot of what has been built in the last month, the state of various projects, and highlight new initiatives with which they can become involved.
For developer-focused highlights on X, please follow Logos Tech. For broader updates on the Logos movement as a whole, stay tuned to the main Logos account.
Below is the Logos Developer Update for January 2026.
Building Logos Testnet v0.1
A primary focus of development this year is the Logos Blockchain, beginning with Logos Testnet version 0.1.
Currently under development, Logos Testnet v0.1 is designed to validate the core backend infrastructure rather than deliver a polished user or developer experience.
The primary focus will be on testing the Blockchain, including the Logos Execution Zone (LEZ), alongside Storage and the ChatSDK/Messaging stack. While UX and DevEx will be intentionally limited, developers will be able to build and test applications on Logos Core using simple, alpha-stage interfaces.
A major goal of this release will be to expose as much functionality as possible through Logos Core, with an emphasis on loading modules via the Logos Node, which will run all core services in headless server mode.
Logos Testnet v0.1 will ship with a set of Logos Core modules in alpha, including Blockchain and LEZ wallets, a LEZ block explorer, and nodes for Blockchain, Storage, and Chat.
On the blockchain side, Testnet v0.1 will use PPoS consensus via Cryptarchia and the Blend Network, enabling testing of wallets, staking, validators, faucets, and token transfers.
LEZ will run with a centralised sequencer that settles on the Logos Blockchain and will support public and private token transfers, custom tokens, and execution of sample applications, with public activity visible through an explorer. The LEZ will be migrated to a decentralised sequencer in a future version of the Logos Testnet.
Alongside work on testnet v0.1, contributors are also scoping out v0.2, which is currently in an early planning phase.
Want to build or operate a node on the Logos blockchain? Register your interest at logos.co/take-action.
Logos technology stack updates
Logos Core
This month’s work on Logos Core focused on laying the foundations for module loading, packaging, and application support. Early in the month, the team concentrated on the Logos App, adding support for web-based apps via a secure webview and a restricted QML-only plugin mode.
Work was also done to improve documentation for core libraries and SDKs, and to set up a central repository for Logos modules with CI support, making them easier to build, index, and distribute.
As the month progressed, the team worked on the package manager (which is still in an early stage), updating it to fetch packages from an online index, install them asynchronously without blocking the UI, and support both local and distributed setups across Linux and macOS. January also saw good progress being made on the development of the Logos node, which will be able to run core services in headless server mode.
A new LGX package format was introduced, with CLI tooling, specs, and CI coverage, alongside experimental work on a module builder to simplify how Logos modules are built and abstracted.
Liblogos itself was refactored, with added tests and CI, while the Logos App adopted the new package manager, gained support for installing apps, modules, and plugins from both folders and LGX packages, and split major components such as the package manager UI and webview app into dedicated repositories.
Storage
This month’s work on Logos Storage focused on stabilising the new direction of the system and preparing it for integration with Logos Core.
A major milestone was the release of Logos Storage v0.3.0, marking the transition away from the old Codex design and narrowing the project’s scope to file sharing. As part of this shift, unused modules such as the marketplace and proving logic were removed, the codebase was cleaned up and renamed, and a clear split was established between the legacy code and the new Logos Storage architecture.
At a technical level, the team delivered a new high-performance dataset store capable of running at SSD speeds, backed by updated dataset and storage data model specs. Merkle tree work progressed significantly, with improvements merged, a dedicated repository created, and multithreaded testing added. The datastore implementation was refactored to match the API specification, with unit tests added and further work planned on quotas, multithreaded I/O, and deeper integration.
Progress was made on the testnet file sharing client, including rebasing AutoNAT support, restarting end-to-end testing, and evaluating future system designs. Privacy research continued in parallel, with ongoing analysis of information leakage in file sharing, a deeper study of existing anonymous communication systems, and active collaboration with the AnonComms team on mixnets, RLN improvements, and provider anonymity.
Integration with Logos Core also moved forward. A new Logos Storage UI repository was set up with Nix support, initial module APIs such as version, debug, and peer identity were implemented, and debug information was surfaced in the UI.
Messaging
This month’s work on Logos Messaging centred on delivering a first usable Chat SDK and preparing the messaging stack for integration into Logos Core.
The team made steady progress on the core building blocks, including improvements to Logos Messaging Nim, such as context-aware event brokers, automatic certificate renewal, and groundwork for clearer health and send APIs.
Most of the visible progress was around the Chat SDK MVP and its developer preview. Key pieces landed during the month, including double-ratchet support, managed-ratchet state storage, chat introductions, and updated protobuf definitions.
FFI bindings were extended and early UI samples were added to demonstrate usage. A first iteration of the Chat SDK module for Logos Core was created, with follow-up work planned to publish it via the shared modules repository.
The team worked on exposing Waku-related APIs, improving service peer management, and enabling basic health checks, while also addressing graceful shutdown support in the underlying runtime.
Integration with Status Communities continued, with progress on SDS-based message confirmation and recovery.
Blockchain
This month’s work on Logos Blockchain focused on achieving major research milestones for the Bedrock architecture and advancing the Logos Execution Environment (LEE) toward its integration as a functional Zone.
The team reached a significant peak with the submission of the Areon paper to CCS and the finalisation of the Mantle specification, which covers decentralised sequencing and bridging. Within the Bedrock engineering stream, Data Availability (DA) was factored out from the core blockchain and testing framework, alongside the implementation of Total Stake Inference and Proof of Claim for the Cryptarchia consensus mechanism.
Significant progress was made in the Logos Execution Environment (LEE), which began its transition into a proper Zone running on the Logos Blockchain. A key focus was the unification of public and private execution to provide a consistent developer experience, supported by research into unifying nonce structures and Program-Derived Accounts (PDA). By the end of the month, the LEE Sequencer was successfully posting blocks to Bedrock, and the Indexer service skeleton was merged.
The infrastructure and testing suite also saw heavy optimisation. This included a massive reduction in cargo-hack CI runtimes from over an hour to just 12 seconds. Additionally, the team introduced support for Windows builds and updated the Rust toolchain to version 1.93.
AnonComms
This month’s work on AnonComms focused on establishing robust discovery protocols and hardening the mixnet infrastructure with advanced spam protection.
The team reached a major milestone with the publication of a general discovery API specification and the implementation of the capability discovery module, including advertiser and IPTree logic. Parallel to this, the team made progress on strengthening the libp2p mixnet through a new pluggable DoS and Sybil protection mechanism based on Rate Limiting Nullifiers (RLN). This included merging the RLN DoS Protection LIP and integrating per-hop proof generation into the messaging stack.
Significant progress was made on Zerokit 1.0, with the successful rework of its public API to support big-endian architectures and the merging of its final RFC. For gasless L2 transactions, the team enabled multiple RLN provers to share a PostgreSQL database using custom binary types and implemented support for burning multiple IDs in a single RLN proof.
Work also progressed on the RLN membership allocation service, where the team began developing a Logos Execution Environment (LEE) programme featuring Merkle tree commitments for public registration. Additionally, the de-MLS track advanced by transitioning to a Hashgraph-like consensus model and specifying draft APIs for multi-steward group management.
Research and documentation
Work has continued on improving the developer experience by consolidating fragmented documentation into a unified, coherent structure to foster a stronger technical community. A key part of the transition to a consolidated Logos technology stack was to ensure consistent public-facing terminology, improve accessibility, and improve integration across protocols.
Developer documentation is the foundation of this interconnection, and the Logos docs are being designed with this in mind.
You can find the temporary docs index on GitHub. Note that this is still subject to change and is under construction.
As part of this shift, Logos Research has migrated all existing RFCs to the new Logos Improvement Proposals (LIPs) repository. This mdBook-based LIPs site serves as a central, reviewable index for specifications across the messaging, storage, and blockchain layers.
Throughout 2026, documentation will be released in phases, with dedicated operator and developer guides designed to provide a predictable onboarding path and accurately reflect the current state of the Logos ecosystem
Tune in to the Logos Broadcast Network
This year saw the launch of regular programming on the Logos Broadcast Network, a collaborative initiative by Logos contributors to deliver consistent updates and foster deeper community engagement.
From developers to activists, Logos contributors are coordinating and publishing a diverse array of content, coding streams, and live spaces that invite pioneers to help shape the collective future we are building.
The schedule features recurring highlights such as Logos Dev Club sessions and Weekly Technical Updates, alongside movement-focused events like Logos Online Circles on X, which host discussions with aligned guests and visionaries.
The full calendar and participation details are available at press.logos.co/calendar.
Logos Circles and events
In addition to delivering across the technology stack, Logos contributors were active across numerous Logos Circles meetups in January, mixing with like-minded builders and pioneers aligned with the wider movement to discuss and build tools to solve local challenges.
13 cities hosted Circles in total last month, showcasing the global and sustained reach of the Logos movement, with at least 10 already scheduled for February.
To find a circle in your area or host one yourself, head to logos.co/circles.
You can find the full calendar of upcoming Logos events on Luma.
To get the latest developer updates from the Logos stack, follow Logos Tech on X. Stay tuned to the main Logos account for news on the wider global movement.
Discussion
Logos
Logos
Logos
Logos
Logos
Logos
Logos
Logos
Logos
Logos