ao

AO has a blog now. So we can finally explain things properly. First post: HyperBEAM and trust-minimized Arweave gateways. (check the “Read” tab on the AO site)

@wallet managing funds. but only if its memory and actions are verifiable otherwise you’re just delegating capital to a black box

What’s the first thing you’d trust an onchain AI agent to do for you?

How much do you pay just to remember? Introducing: OneMemory. Store your favourite memory on Arweave. No wallet or sign up required.

The Arweave gateway stack went cacheless with the transition to HyperBEAM and that broke the old assumption that someone's maintaining a global index With the SaaS infra propping up the network fully cancelled, @aoTheComputer needed an indexer for deeply nested dataitems. In the old model this was slow, and in the new decentralized model, it didn't exist But instead of reintroducing a centralized service, github.com/permaweb/Hyper… ships an upgrade that turns the copycat device into a deeply recursive indexer that runs inside the AO network and indexes at a rate of 1GB/s (4 days to crawl every corner of the entire 24 billion tx blockweave) lots getting built on AO if you look at the PRs

apps shouldn’t break APIs shouldn’t lie infra shouldn’t disappear ao fixes that

@HeyGoAudio 💯

Brass Tacks, bottom line, at the very heart; #Arweave Maxxers are the purest of Web3 hodlers. We know the value $AR brings to the whole world. The smallest transaction, the tiniest file, the most minute piece of secured, preserved public data could mean everything. Remember♾️

@memendexi @elonmusk @ArweaveEco 🫡

@elonmusk @aoTheComputer @ArweaveEco Too the moon missions

Rocket garden at Starbase. You can see this from the public highway.

@HouseofChimera depin makes more sense if you stop thinking of it as a category; it’s just real-world resources plugging into a programmable web

The DePIN category is hard to dismiss even in 2026, anon. 🔹 ~$9.3B category mcap today 🔸 ~$72M in FY25 onchain revenue 🔹 Leading networks traded around 10–25x revenue 🔸 DePIN startups raised ~$1B in 2025 Updated landscape below. Who did we miss?

Lunar is now the official AO explorer 🌔 Replacing ao.link, Lunar is the official source for exploring AO network activity: → Live messages & transfers → Process and action tracking → Node health and network stats → Wallet & transaction lookup → AOS terminal + GraphQL Explore AO at lunar.ar.io

@theelixyne congratulations again!

Humbly received with a grateful heart 🤍. Truly appreciate @aoTheComputer team for the kindness, patience, and constant updates throughout the whole process. Your support made everything smooth, which shows how reliable the team truly is. Wishing nothing but the best for AO team moving forward. My support will always be here. 🙌

@itsdayagain @crypto_with_seb @Auki 🫡

@crypto_with_seb Yes. $AO @aoTheComputer $AUKI @Auki

These are my bets for AI sector. Anything else I should add? $TAOBOT $QUBIC $TAO $FET $RENDER $PAAL $ICP

Why run Arweave gateways on HyperBEAM? Because eventually you shouldn’t need to trust the people running the infrastructure. In this clip @samecwilliams explains the thinking behind moving gateway functionality into the AO / HyperBEAM stack.

@fwdresearch ☝️

Arweave: 7.5 years of continuous uptime. Complete protocol. No roadmap because there's nothing left to add. The foundation layer that makes permanent applications possible. Just a decentralized archive doing exactly what it was designed to do.

@K4y1s @dan_note 👀

@dan_note Cool project! Might contain some inspiration for getting TypeScript on @aoTheComputer 👀

I've built a new JavaScript runtime that runs inside the BEAM. Every JS runtime is a GenServer with its own OS thread. No JSON anywhere — JS objects map to BEAM terms natively through a lock-free queue. What makes it different from running Node/Deno/Bun alongside Elixir: → JS runtimes live in supervision trees. They crash, restart, recover state — standard OTP → fetch() goes through :httpc. WebSocket through :gun. crypto.subtle through :crypto. BroadcastChannel through :pg — works across a cluster → The DOM is lexbor (C library). JS renders into it, Elixir reads it directly — no serialization, no re-parsing → Workers are BEAM processes. They get preemptive scheduling for free → TypeScript toolchain (OXC) and npm client built in — no Node.js on the machine at all Full control over the JS layer: parse ASTs, bundle imports, transform TypeScript, minify — all from Elixir via OXC NIFs. Use cases: — SSR with Preact/React into native DOM, Elixir reads the tree — Sandboxed user-defined business rules with memory limits, timeouts, and a controlled API surface — Parallel Workers that compute and broadcast via distributed process groups — Evaluating or bundling TypeScript without any external toolchain — Running npm packages inside the BEAM Still a research project in early beta. Covered with tests including Web Platform Tests ports, but expect rough edges. github.com/elixir-volt/qu…

YOUR WEEKEND BUILD CHALLENGE 👾 One winner will receive $100 USD or equivalent in stablecoins. 
Build a personal productivity tool using @ao_devbot. Need ideas? Here are a few you can build: 
→ A Habit streak tracker
 (with a token?) → A Daily goal tracker → A Simple study planner Tag @ao_devbot with your builds to be eligible! Submissions close Sunday, 11:59 PM UTC. Best builds get featured in our Builder Spotlight 💯

@mil_itia 🫡

AI infrastructure won’t just be chips and datacenters, a lot of it will be software >>> @aoTheComputer