Load Network

The $LOAD fair launch is now live on the Permaweb Index! Anyone can delegate stake to earn $LOAD - the native token of Load Network. Today we reveal the tokenomics and utility of the $LOAD token, and how the fair launch works:

Today we're testing Load's consensus layer, Ultramarine, with load-blaster ~95k TPS, 2 gigagas block limit filled load-blaster is generalizable to any EVM chain and specifically built to test high blob throughput github.com/loadnetwork/lo…

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 🫡.

This esoteric NixOS mention from the latest @aoTheComputer series is a nice way to think about AO hashpaths when setting up a new Nix installation, you can determinstically orchestrate the whole stack of packages from 0 and prove that the builds are correct and deps are satisfied. you can fully reconstruct how your OS came into existence, you're not trusting snapshots. same with how AO hashpaths prove computation -- instead of packages, it's process state. you're answering how the base state arrived to the latest state a million messages later, with each mutation able to be proven and verified by any node in the network hashpaths prove the lineage of a piece of computation rather than just checking the last output is correct verifiability without painfully slow legacy algorithms

One year of AO mainnet. A lot happened that didn't make the headlines. @mil_itia sat down with @samecwilliams to go deeper on all of it. HyperBEAM evolving into a full PermawebOS, what trustless infrastructure actually means for users, the Permweb Index rebuild from scratch, and why the team went heads down instead of online. This is the deeper dive.

5/ Future Storage Solutions What does the future of storage look like? ☁️ We are already testing incredible solutions on KYVE Testnet, including: 🟦 @WalrusProtocol 🟦 @shelbyserves 🟦 @useload 🟦 @Filecoin

xANS-104 goes brrrr @ data.load.network

One year of AO. Reflections on the state of web3, the progress we've made on the permaweb, and the path forward.

we contributed to DefiLlama Adapters, adding support for two previously untracked token deposits - USDS and DAI - where before only stETH was tracked in the ao-bridge adapter! * updated DefiLlama dashboard: defillama.com/protocol/tvl/a… * PR: github.com/DefiLlama/Defi…

Two days until AO's first birthday 🎂 A year of building the permaweb stack from the ground up. A year of learning what actually works and what doesn't. Grateful for everyone who's been eating glass with us.

Atlas just got a big upgrade to support @aoTheComputer token queries. * Top $AO spenders / receivers * Filter AO token transfers by tag, recipient, amount * Custom query builder to find e.g. all transfers that send over X amount of AO to Y address bonus: Atlas is indexing ALL token process messages to unlock even further complex queries and use cases atlas.decent.land/tokens

new PoC built on @apus_network & @aoTheComputer: space.ao gives agents a world to live in Deploy agents, define their purpose and personality, run them autonomously on AO !! wip: DNS propagating, steady lads

AO's HyperPATH let you access an ao process state variable via a simple HTTP GET request, no interface required at all - the beauty of the patch@1.0 device! treasury.ao multisig process example: @1.0/now/cache/admins/serialize~json@1.0" target="_blank" rel="nofollow noopener">app-1.forward.computer/_ZHB6lKJ8FaZfT…

The first multisig on @aoTheComputer is here The treasury.ao alpha MVP, built on ao mainnet, can custody tokens and execute functions based on votes from predefined treasury admins. Read in full and try it here: blog.decent.land/treasury-ao/

xANS-104 usage goes brrrrrr

AI systems are giant data factories. Some data needs permanent storage for verifiability & reproducibility. While some data is ephemeral. @useload offers smart routing between Arweave and their hot cache. All data is stored in one standard format with multiple ways to do so.

We just published the Deep Ventures Jan 2026 Newsletter! We highlight: - Predictions for 2026 - we are bullish! - PortCo updates for @zkPanther, @Bitflow, and @useLoad - New content - who owns the upside, token or equity holders? Give it a read and let me know what you think! blog.deepventures.io/p/deep-venture…

13/ Everything in this thread is wrapped up here: blog.load.network/load-for-ai-st… more: load.network/ai

12/ Resources pt. 2 s3-agent: REST API to upload and query ANS-104 DataItems to Load S3 - docs.load.network/load-cloud-pla… data.load.network: explore Load S3 data and pools of AI datasets Load S3 partner program: get 100GB/mo of Load S3 storage for free - load.network/s3-partner-pro…

Load for AI storage megathread time The APIs, CLIs, examples and theory you need to store verifiable AI data on Load S3 🧵