AR.IO primary sources — 2026-05-15

What was reviewed

Key notes

  • AR.IO runs its token and network logic through an AO-based smart-contract process that manages balances, gateway registry, ArNS registry, vaults, and ANT discovery/ownership utilities.
  • Gateway operators stake ARIO, can receive delegated stake, and are evaluated through an observer protocol rather than simple self-reported uptime.
  • Each 24-hour epoch selects up to 50 observers using weighted-random selection based on stake, tenure, gateway performance, and observer performance, with hashchain entropy from prior contract state messages.
  • Observers test common prescribed ArNS names plus additional individually selected names, and the system also samples gateways for chunk/offset validation.
  • ArNS provides a shared naming layer for Arweave data, while ANT processes make names and undernames portable, transferable control objects.
  • Protocol rewards come primarily from ArNS name purchases and renewals; 90% of epoch reward allocation goes to base gateway rewards and 10% to base observer rewards, subject to functional/deficient classifications.
  • Delegated stakers share in gateway rewards automatically, which makes stake-routing a meaningful influence layer over gateway economics and observer-selection odds.
  • Deficient gateways that miss rewards for 30 consecutive epochs are removed and their minimum join stake is slashed back into the protocol balance.
  • Repo/docs still describe current multisig ownership with a path toward immutability, so the protocol should be treated as decentralizing infrastructure rather than fully governance-minimized already.

Why it matters

AR.IO is a strong comparison point for decentralized data-access middleware because it does not stop at run a gateway. It ties together gateway admission, peer observation, delegated staking, name-based routing, and usage-funded rewards in one operator economy.