ANS quickstart for real users
This page explains exactly how to register, manage, and use your .abs name on our website. If you are building a wallet, app, or indexer integration, use the developer docs.
Choose your docs path
User flow
alex.abs
Owned by you
User Docs
Learn how to search, register, configure records, transfer names, and migrate from V1 to V2.
Jump to QuickstartDeveloper flow
resolve(name)
Production ready
Developer Docs
Read integration architecture, method reference, event indexing, and production checklist details.
Open Developer DocsWhat ANS is
ANS is a naming layer on Abstract. A .abs name is an ERC-721 NFT that you own and can transfer like any other NFT.
What you can do
Register your name, attach records for wallets and profiles, and use your name across supported apps.
Where to verify
You can always verify ownership and transactions directly on ABScan for full transparency.
Open V2 contract on ABScanQuickstart in 10 detailed steps
Follow this exact website flow. It mirrors the current UI and avoids the most common mistakes during registration.
1) Open Register page
Open the Register page. This is the only page where availability, pricing, and registration are combined.
2) Connect your wallet
Use Connect Wallet in the header and confirm you selected the account that should own the name.
3) Search your preferred label
Type the label and click Check. The app normalizes the input and validates allowed characters.
4) Read the status result before you continue
The card can show Available on V2, Registered on V1, Owned by your wallet, or unavailable states.
5) Check subdomain namespace status if you use a dot
For names like label.project, verify the project subdomain namespace is enabled before registration.
6) Review the full checkout quote
Read base USD price, discount effects, estimated chain payment, and the Pyth update fee.
7) Apply a coupon only if needed
Enter a coupon code and click Apply. If valid, the quote updates before you sign anything.
8) Register and approve in wallet
Click Register, confirm in your wallet, and wait until the transaction is mined.
9) Verify ownership from the result actions
After success, use Go to name to open your name page and confirm owner and profile fields.
10) Continue in Manage
Use Manage to open your management page and configure records or transfer.
Manage your name after registration
This guide follows the real V2 management UI so users can update records without guessing.
A) Open the correct manage URL
Go to Manage for all names, then use the search field to jump to one specific name.
B) Confirm wallet and domain list
If no names appear, connect the wallet that owns the domain. Use Search your V2 names to find and open the right card.
C) Update Primary record
In Primary record, enter the destination value and click Save record. Confirm the write in your wallet.
D) Update profile fields
Fill avatar, twitter, discord, url, and email. Each field has its own save action, so confirm each write separately.
E) Upload avatar when needed
You can upload an avatar image in the card first, then click Save avatar so the URL is written on-chain.
F) Transfer safely if needed
In Transfer domain, enter a wallet address or V2 .abs name. Verify the resolved recipient preview before confirmation.
G) Refresh and verify updates
Click Refresh in Manage, then verify the latest data from your name page and on ABScan for final confirmation.
H) Handle V1 migration cases
If a name is marked Registered on V1, open Migration first. Then return to V2 Manage to set records again.
Using MetaMask Snap
If you want direct .abs resolution inside MetaMask, use the dedicated Snap docs and installer flow.
Open MetaMask Snap DocsName rules
- Minimum length is 1 character.
- Allowed characters are a-z, 0-9, and hyphen (-).
- Names are normalized to lowercase and are case-insensitive.
- Subdomains use one dot in label.project format.
- Registering an existing name fails.
Pricing
Pricing is based on label length. The shorter the label, the higher the price. Prices are USD-based through Pyth and converted to chain payment value.
Coupon discounts and holder discounts can change the final payable amount.
Subdomains for projects and communities
Subdomains are enabled per project namespace, for example bob.moody. Once a project namespace is enabled, users can claim labels in that namespace and receive standard ERC-721 ownership.
- Format is label.project with exactly one dot.
- Only enabled project subdomains can be registered.
- Price is based on label length, not full string length.
- Some project namespaces may have custom pricing tables.
- Subdomains can be transferred like regular names.
Want a project subdomain namespace for your community? Contact us via Discord, Telegram, or email.
V1 to V2 migration guide
V2 adds richer records and improved metadata handling. Eligible V1 owners can migrate by burning the V1 token and minting the same name on V2.
Eligibility cutoff
Only V1 token IDs 0 through 1965 can migrate to V2. Token IDs above 1965 are not eligible.
- Connect your wallet on the migration page.
- Choose your V1 token and confirm the exact same name for V2.
- Approve V1 token transfer to complete the burn step.
- Run migration transaction and wait for V2 mint confirmation.
- Set records again on V2, because records do not auto-migrate.
Common issues and fixes
Name looks valid but registration fails
Double check if the name is already registered, reserved for migration, or uses an unsupported format.
Resolution does not update instantly
Wait for transaction confirmation and indexer refresh. Then resolve again from a fresh app session.
Coupon is rejected
Coupons can be inactive, expired, or exhausted. Try again without a coupon to verify base registration flow.
Migration option unavailable
Confirm that the V1 token ID is eligible and that your wallet currently owns the V1 token.
Need help from the team?
If you find unclear wording, translation issues, or onboarding gaps, report them so we can improve docs quality for all languages.
Join support channels on Discord and Telegram, or send an email.