GM fellow Arweaver!
A lot of progress is being made on permaweb infrastructure right now. This week, we're mapping it out.
Let's jump right in.
Strengthening the permaweb, layer by layer 🐘
Arweave's storage layer has been decentralized since the network launched in 2018. Over time, a larger vision for a resilient cyberspace emerged, the permaweb, and it’s developing into a fully decentralized system across the entire stack.
The permaweb is more than storage
The permaweb experience involves more than permanent storage. Gateways, bundlers, indexers, naming, and routing all sit above Arweave’s base storage layer. Together, they help transform permanently stored data into a decentralized user experience where information can be read, written, searched, and routed by anyone.
This graphic from the AO development team’s recent article about permaweb anatomy offers a clear overview of the various user and equipment types that make this experience possible.
From securing permanent data to serving compute requests on consumer hardware, anyone can contribute to this permissionless ecosystem. Another way to picture this is by using xylophonezy’s sprawling archipelago analogy, where each island plays a specialized role, connected by open and neutral rules.
Decentralization in practice
The practical benefits of decentralization run across the full permaweb stack, with composability at the heart of how it all plays out.
Bundling is the most cost-efficient way to get data onto Arweave, while the user experience benefits from quicker uploads without waiting for transactions to finalize. Recent developments have decentralized this process, using the Copycat device to open the service to consumer hardware.
Gateways moving to HyperBEAM makes them fully verifiable and lighter to operate. The recent arweave.net transition allows it to run on $800 worth of hardware, a meaningful indicator of how far the efficiency gains have come. HyperBEAM distributes arweave.net requests across multiple node operators, with 28 nodes currently participating in the alpha stage. See the staking explorer for the latest metrics.
LapEE, the Laptop Execution Environment, takes this further. It's now possible to boot a laptop directly into PermawebOS as a dedicated AO-Core appliance, turning consumer hardware into a secure, verifiable compute node. LapEE devices can participate as bundlers and get paid for verifiable work. This is still early-stage but the direction is clear.
Permaweb Names is another example of this maturation in action. A fully decentralized naming layer is essential to the full permaweb experience, and it's part of the stack too.
Relentless commitment
It’s an exciting time to keep tabs on permaweb development now that the pieces are coming into place. A quick look at HyperBEAM commits reflects the pace of work going on under the hood.
A big thanks to the AO and Hyperzine editorial teams for all the recent updates. The deep dives and details are a fantastic way to get up to speed on everything happening.
Make sure to bookmark both to stay updated:
ICYMI 👀
Here’s a quick snapshot of what’s been unfolding across Arweave and AO.
- LapEE guides available in Chinese
- Apus is working on AI-native devices
- New Arweave-centric features for Odysee creators
This week's community feature 🌎
If today's issue has you inspired about the permaweb, Jonny Ringo's The Eye dashboard is well worth a visit. It tracks live network stats for Arweave and AO, and even includes a 3D globe map of HyperBEAM nodes.
Thanks for reading!
If you know anyone else who would find this information and our insights helpful, please share this newsletter with them.
Follow us on X at @onlyarweave to stay updated on all things Arweave. Want to dive deeper into AO? Check out @aoComputerClub.
The Longview Team
This is not investment advice. No profit guarantees. If in the U.S., ensure compliance with U.S. laws and seek professional advice.