Logos Dev Update: April 2026
Your monthly update on the development of the Logos technology stack.
Logos
Logos provides monthly updates on the state of the technology stack and the development of its various modules.
These updates cover all elements of the unified stack, including Storage, Messaging, and Blockchain, as well as lower-level infrastructure such as Logos Core and AnonComms.
The aim is to give developers a clear snapshot of what has been built over the past month, the current state of key projects, and highlight new initiatives they can get involved in.
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 April 2026.
Logos Testnet v0.1.2 launched
The biggest highlight from April was the release of Logos Testnet v0.1.2, the second iteration of the unified Logos testnet. The release builds directly on March's v0.1 launch, incorporating chain recovery fixes, improved Docker deployment, and a more reliable bootstrap path for new nodes joining the network.
Two release candidates were prepared and tested across internal devnets through the first half of the month before the full v0.1.2 release went live. In parallel, the Logos Execution Zone moved forward with its own v0.2.0-rc1 release, with rc2 successfully deployed on stage 2 and finalising 100 blocks against the latest Bedrock node.
To accompany the launch, we also published a Testnet v0.1 retrospective on 17 April, reflecting on what was learned from the first iteration and what the team is carrying forward into subsequent releases.
Developers can continue to engage with the stack through the Builder Hub, download Logos Basecamp to run a node, or join the testnet channel on the Logos Discord to provide feedback and report issues.
λPrize programme now underway
On 16 April, Logos formally launched λPrize, a builder incentive programme that will distribute up to $500,000 in total prizes to developers shipping privacy-preserving software on the Logos stack.
Unlike traditional grant schemes, λPrize rewards working code rather than ideas or proposals. Builders submit production-ready implementations against clearly defined challenges, with prizes awarded on a pass-or-fail basis once submission criteria are met.
Open challenges currently span a wide range of difficulty and scope, from focused tools such as wallet utilities, privacy attestations, and DAO infrastructure, through to larger applications including decentralised exchanges, NFT marketplaces, lending protocols, and an anonymous forum with threshold moderation. Listed prizes range from $400 to $1,200 at the lower end, with significantly larger amounts attached to the more ambitious challenges. New prizes are being added on a rolling basis.
Submissions are handled through the λPrize GitHub repository using a structured pull request workflow, and participants gain direct access to the Logos engineering team through office hours and ongoing technical support.
For the full background and submission process, read the dedicated article: Logos Launches λPrize Rewards for Developers. To browse open challenges, head to the Logos Builder Hub.
Logos Privacy Builders Bootcamp
The Logos Privacy Builders Bootcamp, announced in March in partnership with Encode Club, kicked off on 13 April.
The four-week programme saw participating developers working on private messaging systems, peer-to-peer applications without central control, and tools built on Logos's modular, privacy-first stack.
Participants received direct support from the Logos team throughout the programme. Further details on the bootcamp are available on the Encode Club programme page.
If you missed any of the Logos Privacy Builders Bootcamp sessions, you can find the recordings below:
Logos technology stack updates
Logos Core
April saw a significant expansion of the Logos Core developer surface, with three new repositories introduced early in the month: logos-dev-boost, an AI-assisted developer tooling project that bundles LLM rules, SKILLs, an MCP server, and scaffolding for building Logos modules and apps; logos-test-framework, a testing framework for loading, inspecting, and exercising Logos modules in automated test scenarios; and logos-logoscore-tui, a Rust terminal UI for managing a logoscore daemon, complete with module listings, autocomplete-driven method calling, and a live event dashboard.
Last month also saw the introduction of a new UI module pattern in which QML runs in-process while Qt backends are loaded into a separate process. This separation has been adopted across modules such as accounts, wallet, and the package manager UI, and is supported by a new logos-view-module-runtime repository. Alongside this, package signing and validation, instance persistence, thread-safe plugin management, and truly asynchronous method calls have all been added to the core libraries.
The latter half of April was dominated by a substantial Qt-removal effort across logos-liblogos, logos-cpp-sdk, and logos-module. Qt types, the Qt process manager, Qt logging, and the Qt application context have largely been replaced by C++-native equivalents, with overloads added to ease migration for dependent modules.
Qt Objects are tied to Qt-specific runtime assumptions, while Logos desires a small, language-neutral, process-neutral module boundary based on open standards. Qt will remain useful at the UI/QML layer; the shift is about making the core module system-independent.
The work also added support for unload-with-dependents and a refactored package manager.
Developer experience saw further investment too: a QML inspector accessible via an MCP server was integrated into the module-builder flow for testing UI modules, AppImage startup was sped up by disabling squashfs compression, and the logos-dev-boost scaffolding gained support for the new UI types and the test framework.
Module migrations to the new module-builder continued throughout the month across the chat, storage, accounts, wallet, package manager, and tutorial repositories.
Storage
Logos Storage spent April advancing toward the final stages of Status integration while making meaningful progress on privacy, NAT traversal, and release infrastructure. Two outstanding Status integration pull requests were made ready for merge, leaving only the final logos-storage support PR to land before the Status integration milestone can be achieved.
On the privacy side, the team completed an initial implementation of the LIONESS large-block cypher, the proposed solution to the Sphinx payload integrity issue identified at the start of the month. Work on hidden services over Mix progressed in parallel, with the design generalised to support any service type rather than just storage, and detailed work on cryptographic primitives, introduction point protocols, and hidden service descriptors is now underway.
NAT traversal moved from research into implementation. Autonat integration was finalised, the underlying nim-libp2p stack was upgraded to Nim 2.2.8, and a new --allow-private-address flag was added to fall back to private IPs when no public addresses are detected.
The block exchange layer also saw improvements, with bandwidth-delay product throughput calculation reworked, active probing with exponential backoff added for downloads, and manifest CID handling decoupled so that the DHT advertises only the manifest CID while the tree CID is used internally for block addressing.
Distributed release testing reached a notable milestone: the test cluster now spins up and tears down automatically as part of the release workflow on GitHub runners, with a follow-up port to Google Cloud underway to leverage integrated log collection.
Messaging
Messaging closed two significant milestones in April. The Messaging API Developer Preview milestone was closed in the first week, marking the API's transition out of preview.
The Nimble migration also landed in logos-delivery, with vendor dependencies being progressively deprecated, and the v0.38.0 release was created and prepared for distribution.
Major maintenance work cleared a backlog of fleet stability and shard configuration bugs, and the legacy storev2 module was completely removed from logos-delivery. Release builds were also optimised for speed.
Work on the next generation of messaging primitives moved forward on multiple fronts. Development of the Reliable Channel API specification continued, and a first implementation of SDS-Repair landed in nim-sds.
QUIC transport reached local validation, with integration into Logos Delivery as the next step.
On the Logos Chat side, the Chat SDK Developer Preview gained a CLI test app, a Nix flake, and FFI cleanup, while preparatory work for group conversations and de-MLS integration continued.
Blockchain
Blockchain made significant progress in April, anchored by the v0.1.2 testnet launch and the LEZ v0.2.0 release candidates.
All three major bridging features — finalised deposit subscription, atomic deposit-and-inscription, and finalised withdrawal subscription — were merged to master, completing a substantial body of work on cross-zone primitives.
The Blend protocol passed an important reliability threshold during the month, with the first stable internal Blend testnet running in the DST lab. A series of networking and protocol refinements landed alongside this milestone, including DNS-based SDP multi-address resolution, exponential back-off for re-dials, tracking of previously failed peers, and a switch to forwarding only after signature verification.
A separate memory investigation reduced memory growth from 1.4 GB to 70 MB over five days — a roughly 20-fold improvement.
Account-level work included advancing multi-owner support, a mechanism that allows a single key pair to control a family of private accounts (unblocking the private donations use case), and a draft Keycard integration for public accounts. The indexer was promoted into its own module repository and an FFI was finalised, while the explorer gained a first QT-based UI and a dedicated specs repository.
Test infrastructure also matured, with continued migration of e2e tests onto the Cucumber framework and the introduction of shared configuration crates.
Nimbos, the experimental Nim node, advanced its P2P stack: the Identify protocol was implemented with mainnet/testnet protocol names, Kademlia bootstrap and routing-table discovery were added, and the entire P2P branch was merged into unstable by the end of the month.
AnonComms
April was a productive month for AnonComms, opening with the closure of the Gasless L2 Transactions milestone: the LIP describing the RLN-based mechanism for gasless L2 transactions on Status Network was merged at the start of the month.
The Zerokit 2.0 upgrade was integrated into the mix-rln spam protection plugin, and a broader rearchitecture of Zerokit began toward enum-based runtime configuration. The cover traffic specification was drafted, implemented in nim-libp2p, and integrated with logos-delivery, where it was tested in local simulation and made ready to merge by the end of the month.
The capability discovery work that began in March reached a key milestone with a change that allows client mode for discovery without participating in the Kad-DHT. Dogfooding of the Logos Service Discovery protocol began in earnest, with bootstrap nodes set up and Logos Delivery nodes running in both Docker and local builds while integration bugs were ironed out. A draft specification for a standalone capability discovery API has also entered review.
The de-MLS multi-steward RFC was merged, the steward list was integrated into de-MLS, a group sync mechanism was added, and a "super steward" role was scoped. The RLN membership allocation service reached a working proof of concept by the end of April, with the logos-chat-module successfully receiving a membership through the protocol and communicating over the mix network.
Research and DST
The Bedrock and DST teams had a strong month. On Total Stake Inference, the team worked out how much the stake estimator's accuracy varies with network conditions: it gets less accurate when delays are uneven, and more accurate when the average delay is higher. They also identified three ways the estimator behaves depending on how network delay compares to the slot rate and settled on h = 1/f as the best learning rate—a setting that keeps the estimator stable, robust, and simple. The supporting paper was reorganised, with consistent notation throughout and a tidier appendix.
Cryptarchia research moved forward on several fronts. The fast bootstrapping RFC was rewritten around a new StateRoot concept, with updated diagrams and matching changes to the Cryptarchia Protocol and Block Construction specs.
The post-quantum security analysis was reviewed and expanded to include recent findings from Google Quantum AI on elliptic curve cryptography. A separate post-quantum safety analysis of the Blend protocol's cryptography was also published.
Research on Data Availability Sampling continued to mature. The team refined its analysis of how an adversary could selectively withhold data, brought the supporting calculator and animation tools together under a single portal, and added more figures to the main DA sampling analysis document, which is now close to complete.
Three new repositories were also spun up: one for block explorer module specs, one for the indexer module, and logos-sql-zone for the Logos password manager, which has now been extracted into its own project.
Documentation
Documentation work in April focused on consolidating the Zone SDK tutorial, drafting a new specification structure to support the growing body of protocol documents, and continuing with the updating of project branding across specifications.
The Testnet v0.1 retrospective also serves as helpful documentation of the initial version of the network, capturing what was learned from the first testnet iteration.
The documentation that provides an overview of the Logos stack is maintained on GitHub, and the node quickstart guide remains the recommended starting point for anyone wanting to run a Logos Blockchain node.
Download Logos Basecamp to get started with the Logos stack and explore the user-facing UI and module management system.
Logos Broadcast Network and Circles
Throughout April, Logos contributors continued to host online and IRL Circles around the world, creating digital and physical space to solve real-world problems with privacy-preserving technology.
The Logos Broadcast Network continued to deliver regular programming, from Dev Club sessions and weekly technical updates to regular office hours every Friday at 14:00 UTC.
Join these office hours to learn more about building on the Logos stack or to get help for specific issues and problems.
You can also find Logos contributors hosting privacy bootcamps in May, one alongside ETHPrague and the other at ETHCluj.
Full schedules and participation details are available at press.logos.co/calendar and logos.co/circles. For a full list of upcoming Logos events, check out the event page 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