AO

About AO (AO)

What Is AO (AO)?

AO, short for Actor Oriented, is a decentralized compute layer that runs on top of Arweave. It is not a blockchain in the usual sense. AO is a data protocol: any network of nodes that follows it produces what the project calls a single system image, a shared computing environment in which an unlimited number of independent processes run in parallel and coordinate only by passing messages.

AO is the native token of that network. It pays node operators for computation and is staked by the nodes providing services, with stake subject to slashing. AO is a separate asset from Arweave's AR token, though the two are tightly linked: Arweave stores AO's data permanently, and holding AR is one of the two ways AO is minted.

Official sources:

• AO
• AO Cookbook
• AO Protocol Specifications
• HyperBEAM Documentation
• AO on GitHub

Who Founded AO? (History)

AO comes out of the Arweave ecosystem and the team behind Arweave's permanent storage network, with Sam Williams closely associated with its design. It was introduced in early 2024 as the compute complement to Arweave's storage layer.

The rollout was staged. Token minting began on February 27, 2024, well before the network was usable as a mainnet, and ran through an extended testnet period. A second distribution channel for bridged assets opened on June 18, 2024. AO mainnet went live on February 8, 2025, when AO-Core shipped alongside the native token and previously accrued balances became transferable. Work since has centered on HyperBEAM, a ground-up node implementation in Erlang, still receiving commits in September 2026.

How AO Works

1. Processes and messages Each unit of computation is a process, an independent actor with its own state. Processes never share memory. They communicate only by sending messages into each other's inboxes, which is what allows an arbitrary number of them to run at once without contending for one global state machine.

2. Three node roles Messenger units relay and route messages. Scheduler units assign each message an ordered slot for a given process and publish that ordering to Arweave. Compute units evaluate a process's state when someone asks for it. Any of these roles can be run by independent operators.

3. Holographic state AO does not push every computed state to a permanent ledger. What is written permanently to Arweave is the ordered log of messages. State is a projection of that log, and any compute unit can reconstruct it by replaying the messages. Storage cost therefore scales with input volume rather than with the size of computed results, which is what makes long-running and memory-heavy workloads viable.

4. HyperBEAM and devices HyperBEAM is the node software implementing AO-Core. Its functionality is organized as devices, each handling one concern, with a metadata device that declares a node's hardware, supported devices, and its metering and payment terms. It also integrates trusted execution environments, so operators can offer computation whose integrity is attested by hardware.

Key Ecosystem Components

• AO-Core, the data protocol defining messages, processes, and their ordering
• HyperBEAM, the Erlang node implementation and its device model
• Arweave, which stores the permanent message log and is paid in AR
• Messenger, scheduler, and compute units run by independent operators
• The AO Cookbook and aos, the environment used to spawn and script processes

AO Token Utility

AO has a maximum supply of 21,000,000 tokens and a Bitcoin-style four year halving, but the halving is a smooth curve rather than a discrete event. New AO mints every five minutes at a rate equal to 1.425 percent of the remaining unminted supply per month, so issuance declines slightly each month instead of dropping by half overnight. On this schedule the full supply finishes minting in the late 2030s.

The distribution is unusual and worth describing precisely. There was no pre-sale, no team allocation, and no venture allocation. All 21 million tokens are issued through minting, split across two channels:

1. Arweave holders Between February 27 and June 18, 2024, all newly minted AO accrued to AR holders. From June 18, 2024 onward, one third of every new mint continues to go to AR holders indefinitely, anchoring AO's issuance to the network that stores its data. Holders delegate their AR balance to accrue AO, and minting then happens automatically every five minutes in proportion to delegated holdings.

2. Bridged yield-bearing assets The remaining two thirds accrues daily to users who commit yield-bearing assets such as stETH, DAI, and USDS. Those deposits stay on their own native chains rather than being locked into AO. Across the full schedule this works out to roughly 36 percent of supply to AR holders and roughly 64 percent to the bridging program.

On the demand side, users pay node operators to run their processes, and messenger, scheduler, and compute units post AO as an economic bond that can be slashed for misbehavior.

What Makes AO Unique?

The clearest differentiator is that AO separates the ordering and storage of computation from its execution. Consensus applies to the message log, which is anchored on Arweave. Execution happens off that critical path, on demand, by whichever compute unit a user selects. That removes the usual ceiling where every node must re-execute every transaction, which is why AO targets workloads such as model inference that do not fit inside a replicated virtual machine.

How AO Differs from Similar Networks

Against general purpose smart contract chains, AO does not replicate execution across all validators. State is recomputed from a permanent log when requested rather than maintained in lockstep by every node.

Against Arweave itself, the distinction is the one readers most often get wrong. Arweave is a storage network with its own consensus and its own token, AR, which pays for permanent storage. AO is a compute protocol that uses Arweave as its data layer and has its own token. Owning AR does not mean owning AO, although AR holders accrue AO under the mint schedule. They are complementary layers with separate assets and separate security models.

Against decentralized compute marketplaces, AO processes are persistent and stateful rather than one-off jobs, and their history stays permanently retrievable.

Use Cases of AO

• Long-running autonomous processes and agents that hold state indefinitely
• Compute-heavy workloads that do not fit inside a replicated virtual machine
• Applications needing a permanent, auditable record of every input received
• Decentralized finance and coordination logic built as message-passing actors
• Selling spare compute capacity by operating a node and charging for execution

How AO Is Secured

AO's guarantees rest on three layers. Arweave's consensus and storage endowment secure the permanence and integrity of the message log. Determinism secures state: because state is a replay of an ordered log, any party can independently recompute a result and compare it. Economic bonding secures node behavior, since scheduler, messenger, and compute units stake AO and can be slashed.

HyperBEAM's trusted execution environment support adds hardware attestation on top, which is trust minimization rather than trustlessness and inherits the assumptions of the hardware vendor.

Risks and Considerations

• Architectural novelty, since an off-consensus execution layer with holographic state has far less production history than replicated virtual machines
• Dependence on Arweave, whose endowment economics set AO's permanence and cost structure
• Node decentralization is still maturing, and the real distribution of scheduler and compute units matters for censorship resistance
• Mint-driven issuance means supply grows for years, much of it via a bridging program whose participation can change
• Unstable third-party tooling. At the time of writing, ao.computer did not resolve and the commonly cited ao.link explorer did not respond, so neither is linked here. The canonical entry point is ao.arweave.net.
• Trusted execution environments introduce a hardware trust assumption

Why AO Matters

AO is the most serious attempt so far at a general compute layer whose scalability is not bounded by replicated execution. It is also an economic experiment: a 21 million cap distributed entirely by minting, with a third permanently tied to holders of the storage network beneath it, has very few precedents.

Where Can You Buy AO (AO)?

AO trades on centralized exchanges that listed it after the February 2025 mainnet launch made balances transferable. It can also be accrued rather than purchased, by delegating AR holdings or joining the bridged asset program described in official documentation. Listings and jurisdictional availability vary.

Major Centralized Exchanges (CEX)

AO is often available on:

• Bybit
• Gate
• MEXC
• KuCoin
• Bitget

Pairs are typically quoted against USDT.

Storage Options After Purchase

After purchase, AO can be held:

• On an exchange, where the exchange controls the keys
• In an Arweave ecosystem wallet supporting AO processes and token balances
• In a hardware-backed setup where the wallet software supports it

AO balances live inside AO processes rather than on an EVM chain, so an AO address is an Arweave-style address, not an Ethereum one. Verify the network and the wallet's AO support before any transfer, and be cautious with third-party interfaces given the instability of parts of the ecosystem's domain landscape.

Related Coins

You can compare AO with related ecosystems on Coinrithm:

• Arweave (AR)
• Filecoin (FIL)
• Internet Computer (ICP)
• Celestia (TIA)
• Bittensor (TAO)