# What you can do URL: https://docs.arcns.io/features/ > Multi-chain address records, a primary name, a profile, subnames, verified records, permanent ownership, recovery and locks, agent records — everything an ArcNS name gives you, and what is not live yet. Your name is the starting point. Here's everything you can do with it — use as much or as little as you like. Two features the app is built for are **not live yet** on Arc testnet and are marked as such below, so nothing on this page is a promise dressed up as a fact. ## Receive on any chain [#receive-on-any-chain] Point `@you` at your addresses on **Arc, Ethereum, Bitcoin and Solana**. Each is a separate address record with its own ENSIP-11 coin type and its own verification flag. When someone sends to `@you`, a name-aware wallet reads the record for the chain they're paying from — no more copy-pasting a raw `0x…` string. You hand out one name; it works everywhere you hold funds. **Arc** Your home chain (coin type `2152525650`). `@you` resolves to your Arc address so anyone can pay you on Arc by name — this is the record the [payment QR and link](/get-paid/) use. **Ethereum** Add your Ethereum address (coin type `60`) so people on Ethereum can send to `@you` instead of a `0x…` string. A wallet can also ask for the Arc record with Ethereum as the fallback. **Bitcoin** Add your Bitcoin address (coin type `0`) and collect BTC under the same name as everything else. You prove control of it with a Bitcoin message signature. **Solana** Add your Solana address (coin type `501`) and receive there too. You prove control of it with an Ed25519 signature from that key. > **Note** > You choose which chains to add — one or all four. Add more later at any time; your name stays the same. A chain with no record answers an explicit `no-record-for-chain`, never the wrong address on the wrong chain. ## Get paid with a QR code and a link [#get-paid-with-a-qr-code-and-a-link] Every name with an Arc record comes with a **QR code** and a **shareable payment link**, so people can pay `@you` by scanning or tapping instead of copying an address. Show the QR in person, or drop the link in a bio, a message, or an invoice. **[Get paid to your name](/get-paid/)** See how the QR code and payment link work, and where they shine — creators, merchants, and splitting bills with friends. ## Be shown as @you everywhere [#be-shown-as-you-everywhere] Set `@you` as your **primary name** and explorers and apps that integrate ArcNS display your wallet as `@you` instead of a long address — in transaction histories, profiles, and anywhere your wallet appears. There is exactly one primary per address across all three namespaces, and it is shown only while it forward-confirms: a `@handle` primary must still be owned by the address, a `.arc` / `.circle` primary must still resolve back to it. A stale primary is never shown. ## Build a profile [#build-a-profile] Behind your name sit text records you control — the same ENSIP-5 records ENS-aware wallets already read: **Avatar & description** A picture and a line of text that make @you recognizable at a glance. **Website & socials** Link your site and social accounts so people can find the real you. **Agent records** agent.manifest, agent.x402, agent.mcp, agent.a2a, agent.erc8004 — the endpoints and identity of an agent, on its name. See below. **All in one place** Everything lives under @you, so your identity travels with your name — and is cleared automatically when the name changes hands. ## Subnames [#subnames] One name can branch into purpose-built names — **`pay.you.arc`**, **`docs.you.arc`**, **`shop.you.arc`** — all under the name you already own, at **no extra registration fee**. A `@handle` gets sub-handles the same way (`pay.@you`). Each one can carry its own records, so you can keep your money and your projects neatly separated under a single identity. **Separate your money** Give out pay.you.arc for payments and keep you.arc for your identity, so a public payment name never exposes your main wallet. **Organize a project** docs.you.arc, app.you.arc, shop.you.arc — one name per purpose, all clearly yours. **Onboard a team** Hand teammates or departments their own subname without giving up control of the parent. **Good to know about subnames** * **They're free to create** — no registration fee beyond the name you already own; you pay only the transaction's gas. * **You're in control.** As the owner of the parent, you create and revoke its subnames whenever you like. * **They live under your name.** A subname has no separate token (`/nft/:name` answers `404 subnames have no token`) and is labelled "controlled by parent" rather than having its own owner — there's nothing separate to manage. * **Where to make them.** Live on chain and in the [SDK](/quickstart/) (`buildCreateSubname` for a handle, `buildSetSubnodeRecord` for `.arc` / `.circle`); the app's subnames panel ships behind a feature flag. ## Prove it's really you [#prove-its-really-you] Anyone can *set* an address on a name. Verification lets you **prove** it: for each record, prove control of that address for that chain and it shows as **verified**. Senders can tell a proven record from an unproven one before they send a single coin. **Verified records** A signature from the address (or an on-chain call for a contract wallet) on a challenge bound to your name's current version. Any later change to the record clears the flag. **Honest by default** An unverified record is shown as unverified so no one mistakes an unproven claim for a confirmed one — the API, the SDK and the app all carry the flag. > **Note** > Verified records are the ones others should trust. The full mechanics — the challenge format and what each proof type checks — are on [Verified records](/verified/). Signing in to third-party apps with a name is not a feature ArcNS offers today. ## Own it permanently [#own-it-permanently] You register a name **once** and it's yours to keep. There's no renewal to remember and no expiry date that could hand your name to a stranger. This is a deliberate choice: a name people send money to must never quietly change owners because a payment was missed. See [Fees](/pricing/) for how one-time pricing works. ## A safety net [#a-safety-net] Losing access to a wallet is the nightmare scenario in crypto. A `@handle` gives you two on-chain tools for it: **Recovery — get back in if you lose access** Set a recovery address in advance, and if you lose access to the wallet that owns your handle, that address can initiate recovery and complete it after a **7-day timelock** (the contract floors the delay at seven days). It's your insurance policy against a lost or inaccessible key — set it up while everything is fine, so it's there when you need it. Recovery is disabled once a handle is tokenized (see [Fees](/pricing/)): an ERC-721 in the wild has only its holder as owner, by design. **Locks — freeze your handle in an emergency** If you think your key might be compromised, lock your handle. A lock freezes it — ownership, records and transfers — so a thief can't move it or redirect your addresses while you sort things out. Unlocking has its own **7-day timelock**, so an attacker can't simply lock and immediately steal. `.arc` and `.circle` names use the verbatim ENS registrar, which has no recovery or lock: protect the wallet that owns them, or hold them from a smart-contract wallet with its own recovery. ## Agents [#agents] An ArcNS name is the naming layer Arc's agent stack lacks: ERC-8004 gives an agent a numeric id, ArcNS gives it `@payday-bot`. A name carries the agent's endpoints and identity as text records (`agent.manifest`, `agent.x402`, `agent.mcp`, `agent.a2a`, `agent.erc8004`), while the payment address stays the on-chain Arc record with its `verified` flag — the one pay-to fact that is proved rather than asserted. **[MCP server](/mcp/)** Resolve names, check availability, read agent records and prepare registrations from Claude Code, Cursor or VS Code — no key, no auth for reads. **[Pay per read with x402](/api/#agents-pay-per-read-with-x402)** Agents read the resolver API for $0.001 a call, settled in USDC from a Circle Gateway balance — no gas, no key. **[Register without a wallet on Arc](/api/#registration-as-a-service)** POST /raas/register: pay once over x402 and receive the name minted to your own address in about two minutes. > **Note** > The `Agent` handle type exists on chain and the API and SDK report it (`handleType`), but the app does not offer it at registration yet. An agent name is recognised by its records (`agent.manifest` / `agent.erc8004`) as well as by its type — see the verification ladder on the [MCP page](/mcp/). ## Not live yet [#not-live-yet] Two features the app is built around are switched off in the app today, even though their contracts are already deployed on Arc testnet. They are listed here so the docs never describe something you cannot do today. **Gift a name — not live yet** The intended feature: **pre-pay a name for someone else** and hand them a claim link, so a friend who holds no USDC yet can claim a name with zero funds of their own. The voucher contract this needs is **deployed on chain** and the app's gift UI is built, but the `/gift` page is behind a feature flag that stays off until a real email provider is wired up for claim notifications and one real gift has been run end-to-end with real funds. This section changes when it ships. **Buy and sell names — not live yet** The intended feature: a **built-in marketplace** (`ArcNSMarket`) with fixed-price listings, escrowed offers and English auctions with anti-snipe protection, a 2% fee on sales, and premium reserved names released through it rather than by direct registration. The contract is **deployed and configured on chain**, with sales fees flowing to the treasury — but the app's `/marketplace` page is still behind a feature flag that has not been switched on yet. Until then a `@handle` moves only by its owner's explicit transfer, recovery or tokenization, and reserved names are released only to their verified rightful holders (see [Fees](/pricing/#reserved-names)). ## Next [#next] **[Register your name](/get-started/)** Put all of this to use — start on app.arcns.io. **[Invite friends](/referrals/)** Share your referral link — and read the honest state of attribution. **[Trust & transparency](/trust/)** How ownership, anti-impersonation and on-chain auditing work. ## Questions [#questions] Questions: [support@arcns.io](mailto:support@arcns.io).