Logos Dev Update: May 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 the runtime and networking layer.
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 May 2026.
Testnet v0.1.3 runup and stake distribution event
May saw good progress made on the runup to Logos testnet v0.1.3. Multiple release candidates were prepared and tested across internal devnets through the month, with 0.1.3-rc.4 published in early May and 0.1.3-rc.6 following later in the month, alongside Docker workflow improvements that auto-publish the latest and latest-rc images on master and release candidate tags respectively.
On 4 May, the team also live-streamed a retrospective of the previous testnet version and a stake distribution event, walking through how stake is distributed across testnet participants in preparation for the v0.1.3 release.
In parallel, the Logos Execution Zone moved its v0.2.0 line forward with rc3 tagged and deployed on Stage 2.
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.
Logos technology stack updates
Logos Core
May was a steady month of investment in Logos Core's developer surface and tooling. The Logos Basecamp launcher gained Wayland support and nested QML directory loading, and bumped its liblogos and view-module-runtime dependencies, while the logos-standalone-app picked up matching nested QML support.
The Logos Design System was expanded with new TabBar and TabButton styles, a new LogosTable component, QT Quick Controls placeholders, and a series of general improvements. The package manager UI was refactored into smaller, more focused components, and the download timeout was extended to five minutes to handle larger module installations.
A push on integration test coverage ran across several Core repositories during the month, with new integration tests landing in logos-logoscore-cli and logos-package-manager-ui, and core_manager references cleaned up across the CLI codebase. A manifest command was added to the logos-package tool and work continued on extending universal modules with module context across the cpp-sdk and test-modules repositories.
The logos-tutorial repository was also updated to reflect correct Logos design system usage and to fix environment variable handling so QML can be reloaded live without rebuilding.
Storage
Logos Storage had a strong month, with several advances made in NAT traversal, anonymous DHT queries, and the LIONESS cipher specification.
Work on NAT traversal was a major focus in the last month. DHT client mode — critical for maintaining content lookup performance when a substantial proportion of storage nodes sit behind NATs or firewalls — was merged. Work began on wrapping libplum, a more modern port mapping library supporting PCP alongside UPnP and NAT-PMP, in a new Nim wrapper. By the end of the month, the team had completed an implementation of NAT traversal covering the full range of options, from port-mapped routers through UPnP/PCP/PMP to relay fallbacks, with Docker tests integrating MiniUPnPd to exercise the mapping logic. Work on NAT traversal is not necessarily specific to storage, and implementation will benefit all aspects of the Logos technology stack.
As part of the work done by the AnonComms team relevant to Storage, the LIONESS large-block cipher specification was finalised and merged after a final round of reviews, with the Mix specification updated to use LIONESS instead of AES for payload encryption and the reference implementation improved to match. Work on hidden services over Mix advanced in parallel, with the team studying the Tor specification and producing a standalone reference implementation of Ed25519 with key blinding, which will form a foundation for future Logos hidden services.
A key anonymity milestone was also achieved, with the DHT-via-Mix proof of concept now working end-to-end. This is the result of the Anonymous DHT Queries deliverable and is being followed up by integration work to make discovery operational across the storage network at large. Separately, a proof of concept was implemented to encode destination read behaviour in the Sphinx packet payload, which would let new libp2p protocols be tunnelled through Mix without recompiling and redeploying exit nodes.
Finally, the Storage team began work on the final pull request for the Status integration history archives, the last piece needed to close out the Status integration milestone. Following the IFT conference week, the cryptography team also brought back a promising lead for speeding up RLN proof generation to around 10ms — a roughly six-fold improvement — based on a recent eprint paper. Given the role RLN plays in Mix performance, the team is now working to implement and benchmark the approach.
Messaging
Messaging closed a significant milestone in May with the Upgrade to Zerokit 2.0 deliverable formally completed and the Delivery module migrated to zerokit v2.0.2. The team also released v0.1.2 of the Delivery module, focused on stability, cleaner data handling, and reduced dependencies.
SDS-Repair was implemented and merged in nim-sds, the SDS persistence interface was defined and made async, and nim-sds was wired into Delivery as a dependency. SQLite management is being lifted into a separate thread, with a domain-agnostic persistency service implemented in Delivery and the connection between delivery persistency and the SDS persistency connector queued up as the next step.
On the infrastructure side, the Logos test fleet was deployed with the Delivery module, the new fleets dashboard went live at fleets.logos.co, and a framework with first end-to-end tests was implemented for the Logos Chat module. The Status integration also formally kicked off in May, with an integration plan published in status-go and the team covering untested functionality ahead of the transport cutover.
Group conversations and contact discovery advanced on several fronts. Logos Delivery was added to the demo client for integrated chat-delivery testing, a GroupV1 ConversationType was added to the Chat library, and a λAccounts crate was introduced as part of the simple identity model. A spike on using LEZ as an account registry for contact discovery was opened, exploring how the execution zone might back the chat identity layer. An ADR for application notifications covering group state updates also landed, alongside notification of missing messages.
QUIC transport remains a focus, with implementation in Logos Delivery slated as the next step once a future nim-libp2p version including the lsquic benchmark fix becomes available.
Blockchain
In May, work on the Logos Blockchain spanned research, engineering, and the Logos Execution Zone. Beyond the v0.1.3 release candidate work and testnet stake distribution event covered above, several deeper architectural changes landed.
The Mantle transaction simplification RFC was implemented during the month: transaction hashes were simplified to use blake only, with Poseidon2 removed; gas prices were removed from Mantle transactions entirely; and Mantle operations now emit events from the ledger, with the Deposit event the first to land. The decentralised sequencing work also progressed substantially, with Zone-SDK competing-sequencers main logic merged, the reorg event simplified for first-write-wins sequencing, atomic withdraws merged, and bounded-blocks streaming refinements landing alongside.
A major piece of build and packaging work concluded with the Circuits as Libraries effort: the poq, pol, poc, and signature circuits are now built as Rust libraries, getting the project one step closer to dropping the circuits install step. Follow-up work hardened the v0.5.0 release across macOS builds, symbol isolation, glibc compatibility, and CI infrastructure.
Blockchain end-to-end tests were also fully migrated to the logos-blockchain-testing framework, consolidating a body of test infrastructure work that has been running since the start of the year.
The Logos Execution Zone also closed out the features that now enable shared account derivation across PDA and non-PDA accounts. Keycard support for auth-transfer was merged, private PDAs were diversified by identifier to enable private donations to multisig accounts, and the public and private transaction flows were unified in a single in-review pull request. The LEZ indexer reached a meaningful maturity point, with the indexer FFI, basic module structure, query API, and a v1 QT Explorer UI all landing within the month, and the LEZ sequencer and indexer themselves migrated from the bedrock client onto the zone-sdk.
A new LEZ benchmarking suite was also developed, covering cycle measurements, crypto primitives, and end-to-end integration latency, with all benches migrated to the criterion harness and a regression CI workflow added for the crypto primitives bench. One of its first uses was benchmarking the LEZ sequencer on a Raspberry Pi 5, an early signal of where the platform's performance envelope sits on modest hardware.
Nimbos, the experimental Nim client, reached another milestone: two-node initial block download now passes, completing the IBD scope for Cryptarchia. Foundations for the Mantle ledger UTXO store were also expanded, including a HashTrieMap, a DynamicMerkleTree, and the underlying data structures.
AnonComms
Last month, AnonComms worked across DoS protection, group messaging, oracles, and supporting infrastructure. The stake-weighted Mix RLN DoS protection specification was finalised and the corresponding Mix RLN Spam Protection Plugin was updated to match. After a round of review the spec was refactored, the mix-dos-protection plugin was updated to use zerokit v2.0.2, and the team verified the Logos Delivery mix integration against the new version.
Work on RLN proof encryption — the next step toward hiding per-hop metadata observability — entered active implementation, with the corresponding draft specification opened for review.
The multi-steward de-MLS specification was completed, including significant treatment of edge cases through the three-layer steward protection mechanism. On the integration side, the de-MLS architecture was reworked from a client-centric to a conversation-centric model, the steward list was integrated, a group sync mechanism was added, and a "super steward" role was scoped. By the end of the month, missing public API methods for inviting members and communicating with the wake-up service had been implemented, with chat integration queued up at the planned integration point.
Capability discovery moved further into production. The Logos Service Discovery standalone API was published as a raw LIP, dogfooding rounds continued through the month, and production integration work in Logos Delivery has begun. The team also published a new single-use reply blocks section in the Mix specification.
Service incentivisation passed an important threshold with the implementation of the payment streams on-chain component, and FFI and protobuf plumbing for payment channels off-chain. An integration plan with Logos Delivery was written, with payment channels and wallet integration within Logos Core lined up as the next steps.
The Zerokit rearchitecture toward enum-based runtime configuration continued at pace, with PR4 and PR5 merged during the month and PR6 completed for the stateful feature. The RLN membership allocation service migrated to the SPEL framework and the supporting simulation was run against the LEZ testnet, with improvements to protocol robustness and the RLN Logos Core module landing alongside.
Finally, the team published a forum post detailing the initial design requirements for the Logos Oracle Network (LON), and the technical specification discussion advanced through the month, including consideration of how Logos Blockchain might be reused either as a separated zone or via shared validators. The IFT Research Call recording on the topic is available here.
Research and DST
May was a particularly strong month for research output, with two paper submissions and a coordinated push on post-quantum analysis across the stack.
The Areon paper was submitted to NDSS 2027, representing a substantial revision of the version submitted to CCS 2026 — claims have been tightened, the theoretical treatment expanded, and new experiments added, including multi-seed comparisons, delay stress tests, robustness analysis, and design ablations. A separate paper, "Total Stake Inference under Stake Privacy: The Case of Ouroboros Crypsinous", was submitted to CCS 2026 in the blockchain track. The supporting TSI analysis report was also significantly extended, with a new appendix on simulation diagnostics for inferred-stake closure and a complete refresh of the accompanying plots. Later in the month, the team began revising "Referenced-Block Visibility for Total Stake Inference" — a new direction extending the baseline TSI construction with uncle references — and opened both the RFC and specification drafts.
Two major post-quantum analyses landed during the month: the Post-Quantum Safety Analysis of the Blend Protocol was finalised after review, and a parallel Post-Quantum Safety Analysis of the Logos Bedrock Layer was prepared. In parallel, the Logos Execution Zone began integrating Kyber-768 as a replacement for ECIES in private account viewing key agreement, with initial findings on Kyber documented and the integration opened for review.
Cryptarchia research moved forward on multiple fronts. The Cryptarchia v1 and Post-Quantum Security report was updated with an operational migration table, and the Checkpoint-based Fast Bootstrapping RFC underwent two rounds of significant revision. A new document, "Modelling of Random Delays", was started, proposing a delay model that accounts for the O(log N) latency inherent in network broadcast.
Blend research continued to focus on the Session-Removal RFC. A withdrawal logic inconsistency was identified and corrected, SDP snapshot timings were clarified, and a Mantle spec revision was incorporated. A new "MiniMax Limits" document was also started, exploring connection management in Blend.
The EmPoWering cryptoeconomics proposal moved close to finalisation, with design details revised and aligned with recent Mantle changes, ready for broader review. Native zones research also began in earnest, with two new documents started: "Path Toward a Common Ledger for Sovereign Zone" and "PoS Participation for Sovereign Channels".
Documentation
Documentation work in May focused on the Zone SDK tutorial draft, which was completed and entered review, alongside the merge of a contributor guide for the Logos Execution Zone. Mantle transaction encoding specifications were updated to reflect the simplifications landed by the engineering team, and a feature document was published explaining what the GroupKeyHolder mechanism solves and how it is used in LEZ.
The documentation that provides an overview of the Logos stack continues to be 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 May, 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.
Logos contributors also showed up at two flagship European Ethereum events during the month, with privacy bootcamps and a Logos presence at both ETHPrague and ETHCluj. The cryptography team returned from the conference week with several new technical leads now feeding back into the stack, including the RLN proof speedup mentioned in the Storage section above.
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.
In June, you can find Logos contributors at Berlin Blockchain Week. We’ll be hosting an informal session in the park, and Logos will also facilitate a BYOC building LAN as part of Dappcon. You’ll need a Dappcon ticket for the LAN, but we are providing 50% off the price of this ticket for LAN attendees.
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