Start here
Retrieve and serve
Fetch permanent files and applications from local caches, peer gateways, or Arweave.
Protocol architecture
Independent gateways. One permanent cloud.
Ar.io gateways store cached copies close to applications, fetch missing records from peers or from permanent storage, build indexes, verify responses, and resolve ArNS names.
The permanent cloud stack
Three systems. Three distinct jobs.
The protocol separates the permanent source record, gateway caching and services, and network coordination. Each system has a distinct responsibility.
The shortest explanation
Gateways do the serving, indexing, and verifying. The storage layer keeps the permanent record. Solana coordinates the protocol.
Gateway services
Not every gateway does the same job.
Each gateway can expose a different mix of retrieval, indexing, verification, naming, caching, and observation services. Operators publish those capabilities for applications to use.
Index and query
Inspect transaction metadata and expose structured interfaces for discovery.
Verify
Check data against its cryptographic Arweave record and sign gateway responses.
Resolve and route
Resolve ArNS names and help clients reach the right permanent resource.
Cache and specialize
Keep useful content close and support application, region, or dataset-specific services.
Observe performance
Participate in open observations that measure whether gateways serve ArNS content correctly.
Programmable naming
Immutable records. Pointers that can evolve.
ArNS is the naming layer for permanent data and applications. A name can point to a new permanent version while every earlier record remains unchanged and addressable.
Explore ArNSArNS resolution trace
my-archive.ar.io
Current target
New permanent version
Earlier target
Earlier version remains directly addressable
- Pointer
- Update records as an application evolves
- Namespace
- Create undernames for apps, users, or environments
- Control
- Assign controllers and limited management rights
- Resolution
- Resolve the same name across compatible gateways
- Terms
- Lease a name or purchase it permanently
- Ownership
- Transfer a portable, user-controlled routing asset
Open network participation
No central operator controls access.
Gateways are independently run. Shared registration, observations, staking, and incentives coordinate useful service without turning the network into one hosting company.
Multi-gateway routing
Open networkRequest
Your application
ar.io gateway
Independentar.io gateway
Independentar.io gateway
IndependentPermanent source
Arweave record
Applications can choose a gateway, switch providers, or route across several while resolving the same permanent source.
- 01
Select
Every 24 hours, up to 50 gateways are drawn as observers by weighted random selection, seeded from Solana runtime entropy. Weight comes from stake, tenure, and past performance.
- 02
Observe
Each observer resolves prescribed ArNS names against its assigned gateways, and spot-checks chunks against their Merkle proofs.
- 03
Report
Results go onchain as a compact bitmap, one bit per gateway, with the full signed report stored permanently on Arweave.
- 04
Settle
A gateway fails the epoch if more than half of reporting observers mark it failed. Passing gateways and observers earn ARIO.
performance feeds the next selection
Fail 30 epochs in a row and a gateway becomes eligible for removal from the registry, with its minimum operator stake slashed. Reports are signed and permanent, so the record is auditable after the fact.
- Minimum stake
- 20,000 ARIO to register
- To get started
- 4 cores, 4 GB RAM, 500 GB SSD
- Recommended
- 12 cores, 32 GB RAM, 2 TB SSD
Build on the protocol
Start with one gateway. Grow into the network.
Start with a gateway, add multi-gateway routing, register an ArNS name, or run the infrastructure yourself.