🚀 Apus Trustworthy On-Chain AI is now live. Deterministic. Confidential. Fully verifiable — with on-chain proofs for every inference. ⚡️🧠 Built on @aoTheComputer × @ArweaveEco Just swap the base URL. No code changes. No API key needed during early access. It just works. ✨ Try it now 👇 apus.ar.io/ No hype — just proofs. Welcome to Trustworthy On-Chain AI. 🔥

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

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.

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

Get and set references for Permaweb Names with the new SDK Any names seeded from the ArNS, ANS or ArProfile snapshots can now be controlled programatically on the permaweb. github.com/permaweb/permaweb…

8 years going on Forever. Happy Birthday Arweave!

Happy birthday, Arweave! Today marks the 8th anniversary of the launch of Arweave mainnet. Over the last year, the centralized training wheels of the permaweb have come off. Gateways, bundlers, and the query layer are all now open to be run by anyone, and incentives are coming into place. Today there are... 1️⃣ Trustless, verifiable gateways: The main gateways to Arweave now all serve their data in trustless, verifiable form. Every response comes with all of the information needed to verify that the content that they asked for is the data that they received. 2️⃣ Incentives for gateway operators: Anyone can join a gateway and permissionlessly start to earn for serving content to users. This gateway has started to take over serving a small portion of Arweave . net’s end-user traffic, scaling up over time. 3️⃣ Decentralized bundlers: You can now upload data through a decentralized network of bundlers which anyone can join and start to serve permaweb user requests through. Node operators can earn by running nodes in this network permissionlessly, and users can trust the LapEE(/TEE) implementations, not the node operators themselves. 4️⃣ Decentralized indexers: Those community run LapEE/TEE nodes can even now be used to index and query data on Arweave, inheriting the same trust-minimization properties as bundlers. No public router for this just yet, but try it on your own node — it works 🙂. A year ago none of these were possible. Each was a hard fought battle and there is still a long way to go to make them the defaults in the ecosystem, but the bedrock is now in-place. Where next? 8 years is a long time, and while the mission of Arweave remains immutable the structure of the web itself is shifting: From discrete apps each with a separate team, to a world of agent-built services customized for each user. The next web will not look like the last. I am truly excited about this because Arweave’s permaweb is the perfect substrate for a web that is no longer defined by static, siloed UIs, but instead morphs and mutates at the speed of user’s wishes. For many years we have focused on creating a web that enables composability through… ➡️ Open content: Owned by users, accessible in every app – rather than any single company/service. ➡️ Open infrastructure: Shared between every app, permissionlessly utilized to back every app, not any single particular application. …and now this stack is finally able to be decentralized, too. This architecture just so happens to offer exactly the mix of attributes needed to create an open version of the agent-driven web. When a useful/fun app is just an afternoon’s work, rather than a year’s, creators (no longer just limited to devs) do not want to run specific infrastructure or hire a team just for that single service. Instead, an existing open catalogue of content, matched with open infrastructure they can simply start to send calls to, is the perfect place to build. Can’t wait to see this in practice. More soon. Onwards! 🙂

The future is bright on the Permaweb. Every major innovation takes time and effort to bring to life. There are bumps - fixes, changes, moments that feel rough up close. Step back and it all looks like a journey. Each improvement makes the ecosystem stronger. Arweave was built for the long run. Persistence is akin to permanence.

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…

Your Arweave Weekly Digest. Permanent storage attracts thinkers and tinkerers. It's a truly profound concept. We've rounded up 5 deep-dive posts covering the mechanics, economics, and principles that make @ArweaveEco worth understanding. Read them here: arweavehub.com/weekly

Running permawebOS

Very excited about this launch. Introducing: ➡️ PermawebOS nodes: A bootable, multi-architecture HyperBEAM instance. ➡️ LapEEs: Pretty Good Security via swarms of widely available commodity hardware. ➡️ Decentralized bundlers: A first alpha deployment for LapEEs. Demanding the most recent high-end server chips or ~$100k as an entry ticket to contribute hardware just isn't a path to decentralized networks. To actually decentralize the web we are going to need to enable wide participation. The PermawebOS is how we think we get there. Big day 🙂. To be clear: This is a huge ship and it is definitively, categorically an alpha. We have been running and using LapEEs ourselves at @fwdresearch for weeks, but you shouldn't jump on this today unless you are ready for: A. Nothing to work as you expect. B. The very real possibility that you brick your machine. Stability and ease-of-use will improve over time, so unless you love self-guided firmware flashing adventures it is best to hang tight for now. Further down the track, it also looks like Android deployments of the PermawebOS may be possible, too, using kernel software isolation and some of their security hardware. Running a bundler on your phone that you genuinely do not know how to tamper with even if you wanted to is pretty remarkably. Brick by brick.

Useful @aoTheComputer builder loop updates today. HyperBEAM (node infra) work focused on making the stack more streamlined to build around: better tests safer debug reports smoother publish/release paths.

More tools to build the permaweb faster:

HyperBEAM just underwent a major change, shifting from a monolithic repo to the permaweb's kernel, with hot-loadable devices. Device Forge makes it easy to ship devices that slot into this minimal core as we build the operating system of the permaweb. x.com/aoTheComputer/status/2…

AO devices are like *nix tools: Simple, infinitely remixable, and open for all to build. This is why you can build things like trust-minimized oracles in a single HTTP URL (yes, really [1]). But building devices used to suck. Yesterday, the device forge flipped that. Details👇

Michael S. Hart digitized the Declaration of Independence in 1971 and sparked a movement to preserve human knowledge through Project Gutenberg. 55 years later, 75,945 of those books live permanently on @ArweaveEco. The library that can't be burned keeps getting bigger.

The @aoTheComputer marketplace is beginning to form. You can configure nodes to offer services, charge $AO, and be selected based on price, speed, and guarantees. Cheers to @xylophonezy for showing us how it all comes together. This is exciting :)

Going cacheless means the weave itself becomes the source of truth. Caching data was convenient but left some pitfalls if a cache went out of sync with the Weave. Now, HyperBEAM-powered infrastructure routes directly from miners and indexes from the Weave itself. The permaweb is becoming verifiable end-to-end.

“What are you doing this weekend?” Meanwhile Trump AI twins inside TEE-protected permanent memory systems: “Working very hard, folks. Tremendous work. Very secret things.” 😂 What are you guys building this weekend? Powered by @aoTheComputer and @ArweaveEco