Along with storage, the permaweb needs decentralized ways to read, write, and search data. Part two explores how these core infrastructure layers are becoming verifiable, incentivized, and decentralized with HyperBEAM.

The Lapee site and guides are now available in Chinese! Lapee 网站和指南现在提供中文版了！ permawebos.arweave.net/#/zh-…

Devices themselves are not limited to the ones that ship with HyperBEAM. Builders can create their own devices, package them, test them locally, run them on their nodes, and publish them to Arweave. A Ruby on Rails device. A custom AI device. A database device. A private API device. A device for anything you want your node to do. HyperBEAM is the kernel. AO is programmable at the infrastructure layer.

Devices enable anyone to build their own verified, trust-minimized oracle. relay@1.0 fetches price data from multiple sources over HTTP. process@1.0 can aggregate those feeds, normalize the data, calculate an average price, and sign the result. The output becomes a verifiable price feed that other applications can consume. The permaweb is a composable platform for building verifiable services.

From bundlers to gateways to indexers, the full permaweb is becoming decentralized. This post is the first in a series dedicated to the topology of the new permaweb, and the evolution underway.

AO devices become more powerful when they work together. bundler@1.0 uploads data to Arweave. copycat@1.0 indexes it. query@1.0 makes that data discoverable with GraphQL. Chained together, they create a complete workflow for publishing and discovering information on the permaweb. AO is built around composable services.

Firing up your own Lapee? Come share your build and chat with other Operators in the #Lapee channel in @discord! discord.gg/kkxffavfUb

We're used to thinking in terms of smart contracts, but these "processes" are just one feature powered by one device. Beyond ~process@1.0, HyperBEAM devices power gateways, routers, bundlers, indexers, payment systems, storage interfaces, and dozens of other network services. A device can be any service. AO is evolving into a decentralized service economy backed by 32+ devices and counting. The most interesting applications on AO may not use processes at all. ao.arweave.net/#/blog/open-s…

It's a cat in a pool! Actually, it's an Arweave data discovery tool packaged as a HyperBEAM device. --> It helps @aoTheComputer nodes find newly posted Arweave data sooner. Being created by @xylophonezy, more about it below.

Using Permaweb Names and the ~reference@1.0 device to build a blog With how powerful devices have become, not everything needs an AO process hyperzine.xyz/using-referenc…

8 years of the Arweave! Celebrate by grabbing that old dusty laptop from storage and spinning up your own LapEE bundler, uploading data straight to Arweave! The Permaweb keeps growing. Happy birthday. 🎉 Start yours and share your build setups below! permawebos.arweave.net/run

8 years ago Arweave launched with a simple but radical idea: store data forever. Today the Permaweb hosts millions of pieces of data and applications, an unstoppable archive of human knowledge, and a full decentralized supercomputer running on top of it. What started as permanent storage has become permanent infrastructure. Here's to 8 years of building the foundation of The New Internet.

LapEE turns abundant consumer hardware into verifiable AO infrastructure. One of its first jobs: decentralized bundling. Now permaweb-deploy supports AO bundlers, allowing deployments to route through the emerging network of community-operated bundling nodes. Another piece of the Permaweb stack decentralized. Learn More: github.com/permaweb/permaweb…