ar.io
ArNS

Permanent domains for permanent data.

Permanent data needs an address people can remember. ArNS gives every record a stable, programmable name for apps, sites, and agents.

namegateway
your-siteanythingarnsardriveconsolegatewaysomnisyour-siteanythingarnsardrive
.
your-gateway.comwhateverturbo-gateway.comvilenarios.comardrive.netar.ioyour-gateway.comwhateverturbo-gateway.comvilenarios.com
appsfilesdatasetsidentities
Why it matters

A name instead of a hash.

Transaction IDs identify permanent data. ArNS gives each record a stable, human-readable name that owners can update, delegate, and resolve across ar.io gateways.

Discoverable

Replace long transaction IDs with names people, apps, and agents can actually use.

Token-backed control

Each ArNS name is controlled by an ar.io Name Token, giving owners and controllers clear permissions.

Reliable resolution

Gateways in the ar.io network resolve ArNS names and are monitored for accuracy.

What you can do

An ArNS name is a programmable routing record.

Register a name, route it, transfer it, and program how it behaves. ArNS gives teams an address they can operate instead of a static link they hope never changes.

ArNS activity helps fund gateway incentives, tying name resolution performance to the health of the network.

Buy or lease

Own a name outright or lease it annually, with the option to upgrade at any time.

Trade or transfer

Move ownership when a project, brand, or community changes hands.

Update

Point the same friendly name at new permanent data as your app evolves.

Program name behavior

Use smart-contract logic for dynamic routing, agent workflows, identity, and app behavior.

Add undernames

Create undernames like docs_myapp or v2_myapp with included capacity.

Access control

Assign designated controllers to manage domain records without transferring ownership.

How it works

A stable name resolves through gateways to permanent data.

Step 1

Register

Choose a friendly ArNS name and register it as a permanent purchase or timed lease.

Step 2

Configure

Set records, controllers, undernames, and the Arweave transaction your name resolves to.

Step 3

Access

Gateways in the ar.io network resolve the name to the right data and are checked for accuracy.

Register a readable name for permanent data.

Give your permanent data a friendly address that people, apps, and agents can resolve consistently across the gateway network.