Ar.io is migrating to Solana

You'll need your current wallet (the one holding your ar.io assets today) and a destination Solana wallet. Each destination wallet must be unique to a single source wallet — destination wallets cannot be combined or reused across source wallets. You can change your destination wallet at any time before the snapshot.

The snapshot replicates the entire state of ar.io onto Solana as of the snapshot deadline — gateways, delegations, names, and token balances — with the exception of any assets that weren't registered. Anything not registered is treated as unclaimed and stays behind.

Any tokens that are not accounted for by the time of the snapshot will be deposited into the Protocol Balance and used for the network's incentive layer. This is a one-way action and cannot be undone.

No. The tokenomics, token distribution, locked supply,and total token supply remain unchanged. The only difference is that unclaimed tokens will be put into the Protocol Balance, but the total supply remains at 1 billion ARIO.

Yes. If you're holding $ARIO on a CEX, withdraw your tokens to your Arweave wallet and complete the registration site before the snapshot deadline.

$ARIO on Base will continue to function for users who prefer EVM-based access. During the migration period, the AO↔Base bridge will be deactivated. After migration, the bridge will be re-enabled as a Solana↔Base bridge, so users can bridge Base $ARIO to canonical $ARIO on Solana and back.

We're working with ecosystem partners to figure that out. Check back here for updates, or reach out in Discord if you have a specific situation. Ask in Discord

Unregistered gateways will not be migrated to Solana. In addition, all operator staked tokens will be treated as unclaimed and deposited into the Protocol Balance when mainnet on Solana is live.

No. The goal is for all existing gateways to retain their performance stats (tenure, streaks, etc.) as of the snapshot.

As long as you complete registration, your stake is safe. If the gateway you delegated to also registers, then your delegation continues on Solana with no action required. If that gateway does not register, it will be removed from the network and your previously staked tokens will be placed into a withdrawal vault — from there you can either restake to another gateway or wait for the withdrawal period to complete. If you do not complete registration yourself, you will not be able to recover your delegated stake.

Yes. If you want to continue managing your name after the migration, you need to complete registration and map your current wallet to a destination Solana wallet. "ar.io classic" will continue on AO for as long as it remains functional, but once Solana mainnet is live, gateways that migrate to Solana will resolve name data from the Solana contract, not "ar.io classic". Name owners should register even if they only have one permabought name or subdomains.

If you complete registration, your ArNS names migrate with you to Solana and continue resolving Arweave data across the ar.io network of gateways. Registration maps your current wallet to a destination Solana wallet, which is required for your names to be assigned to you on Solana. "ar.io classic" will continue on AO for as long as it remains functional, with no changes to existing wallets or owners. However, any gateways that move over to Solana will resolve the state of the Solana contract, not "ar.io classic". After migration, names are managed from Solana wallets, so the Ar.io Name System name better reflects how the system works and leaves room for broader multi-protocol support. Also note that:

• Unregistered permabought names are mirrored to Solana as-is and continue resolving, but they are assigned to an ownerless burn wallet and frozen at their snapshot state.
• Unregistered leased names are mirrored to Solana as-is and assigned to an ownerless burn wallet, where they can eventually expire and return to the market for repurchase.

ANTs move to Solana as Metaplex Core NFTs, with all settings maintained. They will also ship with updated field naming to support future multi-protocol resolution (for example, IPFS) in later phases.

The intent is to minimize breakage as much as possible. The SDK abstraction layer is designed to minimize or eliminate code changes for most applications, so users will generally just need to make sure that they're on the latest version. That said, the performance of general ar.io functionality with Arweave wallets will degrade, including support for Primary ArNS names.

Unfortunately no, not initially — and that is one of the big trade-offs. Going forward, all interactions (Ar.io Name System, gateways, and more) will require Solana wallets. The one exception is users holding $ARIO on Base. Note that wallet types supported by Turbo for data uploading will be unchanged.

Ar.io is already plugged into the Solana ecosystem and leveraged by many notable teams and projects, so moving our execution layer there is a natural next step. Solana also gives us faster execution and better developer velocity while reducing dependency risks. Arweave remains the permanent foundation.

No. Arweave continues to be the core permanent, immutable data and provenance layer for everything we build. This is an optimization of the execution layer only.

No. This is an existing asset migration — holders who complete registration keep the same balance on Solana. No new tokens or rewards will be distributed.

If your situation isn't covered here, come find us in Discord and we'll help you figure it out. Join the ar.io Discord