It has been quite some time since the last DLL ship on this blog, but today we are releasing this post to outline DLL’s takes for the upcoming months on HyperBEAM, the doubling-down on Arweave and AO, ideas to research, and history to be made – tl;dr: DLL is here to stay.
ICYMI
Before going over the post points, it’s important to know the ICYMIs! In April 2026, Load Network, one of several DLL products, was acquired by KYVE Network – read more.
Additionally, on June 1st 2026, Forward Research released Permaweb Names, a unified permaweb namespace, curating the different fragmented identity-relics from the ecosystem into a single neutral namespace, and as you know, DLL has developed ANS (Arweave Name Service) in the past, so if you own any ANS domains, you should be able to manage them again under Permaweb Names! Read more about Permaweb Names here
DLL & AO
Exactly one year ago, we released the hb/acc manifesto, on Arweave Berlin Day 2025:
On Arweave Day Berlin (June 7th 2025) we announced the inception of the Hyperbeam Accelerationism manifesto, expanding on the points listed in this blog post.
During the talk we demo’d Ultraviolet, the first EVM appchain on top of hyperbeam built on top of the ~evm@1.0 device, and the first general purpose & arbitrary GPU compute, leveraging the ~kem@1.0 device, that’s interoperable with ao atomic NFTs via Bazar. - src
Since the early days of HyperBEAM and our technical interest shifted into developing on AO’s HyperBEAM, motivated by the immense potential seen in this new and early kind of unbound compute. And today we are even closer to AO and HyperBEAM, formally contributing to it, have a deeper understanding of how it works, doubling down on the decentralized cyberspace vision.
PermawebOS, LapEE, and DeFi
These three hot categories are related in our vision context – but for our readers memory refresh (+ ICYMI), AO has released LapEE:
LapEE is the Laptop Execution Environment. It boots a laptop directly into PermawebOS as its sole operating system, starts a PermawebOS node, and exposes evidence that lets a verifier bind that node to the measured boot.
LapEE is not a general desktop and not a multi-tenant isolation system. The machine is treated as a single-purpose appliance.
Technically, LapEE uses TPM 2.0 to connect the running node to the measured state. The firmware and UKI produce boot measurements, PermawebOS builds a boot measurement subject from system evidence, the runtime extends PCR 15 with that subject, and a TPM AK quotes PCRs including PCR 15.
The verifier then checks the quote, PCR replay, AK policy, EK chain, Secure Boot state, and node message.
So you get a verifiably measured execution environment – a verifier can cryptographically confirm which software is running on the machine. Additionally, LapEE supports TME/SME (memory encryption), which provides some hardware-level memory privacy <- and this is where we think LapEE can be leveraged in the next phase of applications and utilities on ao. DeFi.
DeFi on LapEE
What if DeFi applications on AO could leverage memory encryption? Zero centralized components? Eliminate trust bridges? What if the whole financial system of an application gets implemented as a HyperBEAM device package, loaded in a LapEE node, and executed in an encrypted memory where no one has access to it, or control over it? This kind of DeFi is now possible to implement in the alpha release of LapEE.
For example, the treasury.ao mutlisig that we built as genesis-wasm Teal process - is now reimplementable as a HyperBEAM Forge device package, leveraging the existing ~token@1.0 and ~security@1.0 devices and creating the very a HyperBEAM native multipurpose mutlisig that can act as smart wallet, token’s mutlisig wallet (including names!).
Furthermore, the core of DeFi functionalities, swaps. We have an internal PoC of a swap device package that lives inside a LapEE execution environment and facilitates trustless AO <> AR swaps (and that can be private as well!).
Ref: https://github.com/charmful0x/pekka/blob/swap/swap.md
What’s next
DLL has not ceased contributing to the Arweave ecosystem since its inception in 2021, and 5 years today, we are still contributing to Arweave, and to its hyperparallel computer, ao. DLL preserves an identity of experimenting with new technologies on top of Arweave, and with the direction of PermawebOS, and how it’s defining the decentralized cyberspace, we are glad to take the opportunity to keep building and shipping!