Sonic Name Service (SNS) Snap Frequently Asked Questions
What is the Sonic Name Service Snap?
The Sonic Name Service (SNS) Snap is a MetaMask extension that allows you to use human-readable .s domain names (like "wallet.s") instead of long hexadecimal addresses when sending transactions on the Sonic blockchain.
How do I install the SNS Snap?
Once approved on the MetaMask allowlist, you can install the SNS Snap directly from the MetaMask Snap directory. Until then, you can test it using MetaMask Flask by visiting [https://github.com/krownlabs/sns-resolution-snap].
What domains does this Snap support?
This Snap supports the ".s" top-level domain (TLD) on the Sonic blockchain (Chain ID: 146).
How do I send tokens to an SNS domain?
Simply type the domain name (e.g., "example.s") in the recipient field when sending a transaction in MetaMask. The Snap will automatically resolve it to the corresponding address.
How do I register my own .s domain?
Domain registration is handled through the Sonic Name Service platform at https://www.sonicname.services. Our Snap only handles name resolution, not registration.
Is there a fee for using this Snap?
No, the SNS Snap is free to use. However, standard transaction fees on the Sonic blockchain still apply when sending transactions.
Can I use this Snap with other blockchains?
No, this Snap specifically works with the Sonic blockchain (Chain ID: 146) and .s domains.
How do I perform a reverse lookup (find a domain name from an address)?
While this feature is not directly visible in the MetaMask interface, applications built on Sonic can use our Snap's reverseLookup function to display domain names for addresses.
What if an SNS domain doesn't resolve correctly?
If a domain doesn't resolve, it may not be registered, may have expired, or might have configuration issues. Check that you've spelled the domain correctly and that it's properly registered on the Sonic Name Service.
Is my transaction data secure when using SNS domains?
Yes, the SNS Snap only performs name resolution. All transaction security is still handled by MetaMask's standard security protocols.