🐘🔗 sam.arweave.dev

Huge shift here. Thanks to everyone on the @OdyseeTeam, @dh_association, and @fwdresearch teams who made this possible -- as well as @ar_io_network for all their help in the transition. But what does this shift mean? tl;dr: Arweave dot net now runs on AO-Core. So... 1⃣ Every response from .net is now verifiable, right to the end-user. This is the fundamental building block of decentralization. When you get a reply from an AO-Core node its headers contain everything that you need in order to verify the data atomically. No need for consensus, querying multiple nodes, etc., just fully trustless cryptographic verification. Additionally, all of the useful tags and metadata that have always been attached to content on Arweave is now available to callers. Users can now process this information and act upon it, just like 'body' data. You can think of Arweave as a permanent database, with each item being a row. Now the whole content of each of those rows can be accessed by users, not just the largest field. 2⃣ Data served from .net is now directly sourced from Arweave nodes. Previously, there needed to be caches in between the user and the nodes, which made gateways heavier to run and 'separated' from the dataset. This detachment introduces points of software and operations dependence in the caches themselves. While .net is still importing some of the data from the legacy gateway (and will be over the next few weeks), these caches have now been removed from the data serving flow. This also opens the opportunity for... 3⃣ ...Permissionless nodes operating .net. Because each AO-Core node serves everything needed to verify each response it gives by default, the next step is to let anyone register to provide the data for IDs to the gateway, then verify their responses before relaying them to users. This alone is a big deal. In time we expect it will provide an additional incentive for Arweave miners to serve (and also store) data, as well as improve performance (by routing to and rewarding the fastest providers) and reliability (by removing points of failure). Further down the track there is a clear path to even decentralizing the operation of these verification+routing nodes, so that every Arweaver can take part in running those, too. We can achieve this by letting TEE nodes register with one another and share private TLS credentials, allowing them to directly serve end-user traffic routed by the DNS layer. We have tests of this flow working in principle, but principle -> practice-at-scale will take some time. 4️⃣ Compute-Over-Arweave-Data just dropped. AO-Core is a protocol to orchestrate a decentralized supercomputer. In this deployment we are making heavy use of AO-Core's codec devices, but it is now possible to do so much more than that. More on this soon. Upshot? Decentralization and trustlessness of data access on Arweave just took a huge leap. Trustless verification of content -> Permissionless data serving -> Decentralization of data access and transformation. Congrats again everyone 🫡.

arweave . net has transitioned to HyperBEAM infrastructure. For years permaweb access has been served through gateway infrastructure. Over the past couple weeks we’ve introduced a distributed network of @aoTheComputer HyperBEAM nodes that can serve the same functionality. This removes a major point of centralization in the stack. Requests can now be served by nodes that produce verifiable responses about how data was retrieved and computed. Transitions like this are never perfectly smooth, and some edge cases may still surface as the new system settles. But the direction is clear: arweave . net is now just one entry point into a decentralized network. Thanks to everyone who bore with us through the migration.

After a year of building, here's the first public demonstration of AO Core. 60+ composable devices. Every state addressable and remixable. Your URL bar as programmable, verifiable infrastructure. @samecwilliams walks through the PermawebOS, the complete decentralized web stack, trustless, in one box. Show don't tell.

⏳ Time travel is now possible… for your ARNS history. Introducing ARIO Rewind by RANDAO⚡ Every @ar_io_network Permapage is permanently preserved on @ArweaveEco — and accessible via @aoTheComputer so nothing is ever lost. 📜 Snapshots, edits, past states — all retrievable, verifiable, and eternal. Because when data lives forever, memory becomes a feature. 🌀 Start time traveling: rewind.arweave.net #RandAO #ARIO #Arweave #Web3 #Blockchain #Permanence

I believe forward.computer is presently running an m3b3 router build that you can join and be paid for computing on, if you are running HyperBEAM OS with a compatible TEE. Docs are lacking/out of date for m3b3 and it certainly wouldn't be easy, but should be possible right now. There is nothing special or privileged about our nodes on that router. Making that simpler and stable will be the next focus after state reads transition. Brick by brick, but it is starting to fall into place.

Important Update for Builders & Community 🔧 We're rolling out major performance improvements to the AO network starting today. Balance requests are going from 10-12 seconds to ~100ms through state lookups on HyperBeam nodes. For Builders: If you haven't enabled patch on your token yet, please do so ASAP. It's just 3 simple steps: hackmd.io/arweave/view/x… Once you've completed the migration, let us know so we can switch you from dry-runs to state access! Many projects have already made the transition, but if you're still on the legacy testnet.xyz cluster using dry-runs, time to update. This is especially critical for token and DEX projects. For the Community: Over the next few days, you may experience temporary disruptions when interacting with DEXs and other dApps as builders complete their migrations. This is normal and expected during the transition period. The result: A dramatically faster, more efficient network for everyone. Questions? Drop them below or reach out in Discord.

Important Update for Builders & Community 🔧 We're rolling out major performance improvements to the AO network starting today. Balance requests are going from 10-12 seconds to ~100ms through state lookups on HyperBeam nodes. For Builders: If you haven't enabled patch on your token yet, please do so ASAP. It's just 3 simple steps: hackmd.io/arweave/view/x… Once you've completed the migration, let us know so we can switch you from dry-runs to state access! Many projects have already made the transition, but if you're still on the legacy testnet.xyz cluster using dry-runs, time to update. This is especially critical for token and DEX projects. For the Community: Over the next few days, you may experience temporary disruptions when interacting with DEXs and other dApps as builders complete their migrations. This is normal and expected during the transition period. The result: A dramatically faster, more efficient network for everyone. Questions? Drop them below or reach out in Discord.