ANS MetaMask Snap for .abs resolution
This page is specific to the ANS MetaMask Snap. It explains what the Snap does, how users install it, which permissions it requests, and how to troubleshoot common issues.
What this Snap does
- Resolves name.abs to addresses inside MetaMask.
- Supports reverse lookup where ANS V2 data is available.
- Scope is Abstract mainnet only (chain ID 2741).
Current release
Package
@ans-abstract-name-service/ans-snap
Version
0.1.2
Snap name
ANS | Abstract Name Service
Install flow
- 1. Open ans-snap.vercel.app.
- 2. Connect wallet (MetaMask Flask for local testing).
- 3. Click Install Snap and approve in MetaMask.
- 4. Send assets in MetaMask to names like yourname.abs.
Main website docs can link to installation, but Snap installation itself should happen through the Snap install app so users get the exact MetaMask Snap request flow.
Permissions and scope
endowment:name-lookup
Enables MetaMask name resolution for .abs.
endowment:ethereum-provider
Reads on-chain ANS V2 data via MetaMask provider calls.
Chain
eip155:2741 (Abstract mainnet only)
Security and support
Snap package is public on npm and source code is public on GitHub.
This Snap does not request key-management methods such as snap_getEntropy.
Support channels:
- GitHub Issues: github.com/0xShroomy/ans-snap/issues
- Discord: discord.gg/5jXUqCSR7Q
Troubleshooting
Snap is not on the allowlist
Use local testing with MetaMask Flask, or use an allowlisted npm version in production.
Resolver not working for a name
Confirm you are on Abstract and the ANS V2 record exists for that domain.
Local Snap changes not reflected
Click Reconnect on the Snap install page when using local development origin.
Uninstall
In MetaMask, open Snaps, select ANS | Abstract Name Service, and remove the Snap.