Page cover

Using SNS

1. Transacting with SNS

The Solana Name Service is supported by most, if not all, of the popular wallets on Solana

Amongst other use cases that can be found under List of Integrations - transacting with your .sol is amongst the most popular

You can send SPL tokens and native SOL directly using a .sol domain or Twitter handle instead of using an address

Transacting with a .sol domain

To send tokens to someone using their .sol domain you need to enter <domain_name>.sol in the "Recipient's SOL Address" field. If the domain name is not registered it will display as below after clicking "Next"

If the domain name of the recipient is snsavailable you need to enter snsavailable.sol

Most wallets follow the same convention described here

Transacting with a Twitter Handle

To send tokens to someone using their Twitter handle you need to enter @<twitter_handle> in the "Recipient's SOL Address" field. If a Twitter handle is not registered it will appear as below

If the Twitter handle of the recipient is @snsavailable you need to enter @snsavailable and not snsavailable

Twitter handles are case-sensitive

At this moment, only Solflare supports transactions via Twitter handles

2. Resolving websites with SNS

2.1 Inhouse resolver

Go to your profile page and click on the domain you'd like to resolve

In this example, we'll be using snsavailable.sol

Scroll down to the record section of your domain. The resolver supports (1) URLs (2) IPFS CIDs & (3) Arweave hashes. Choose what you would like to resolve and enter it accordingly. Here we used a URL

The format of the records is as follows:

  1. IPFS: ipfs://<CID> (e.g ipfs://QmZk9uh2mqmXJFKu2Hq7kFRh93pA8GDpSZ6ReNqubfRKKQ)

  2. ARWV: arwv://<HASH> (e.g arwv://KuB5jmew87_M2flH9f6ZpB9jlDv8hZSHPrmGUY8KqEk)

  3. url: With the following format url_to_your_website (e.g https://sns.id)

If you have more than one record set, the resolver will prioritize the url section first, then IPFS and lastly ARWV

Once your record section is set, you can browse SNS websites in the format of yourdomainname.sol-domain.org. In this example, it would be snsavailable.sol-domain.org and it'll resolve to https://www.sns.id/

2.2 Brave example

Brave's integration allows you to resolve domain names natively. This means no gateway or extension is needed - just your .sol domain name in the URL tab

Follow the steps above and edit either the URL or IPFS record section of the domain. Sign the transaction and you are good to go

Go to Brave Browser and type your .sol just as it is in the URL tab and watch your website resolve

2.3 4Everland example

4EVERLAND Hosting service supports SNS+IPFS and offers a dedicated gateway 4sol.xyz for all SNS owners

To deploy your website on IPFS and associate your domain name, follow the steps below

Video tutorial for 4EVERLAND setup

2.4 Marlin Oyster gateway

Marlin Oyster also allows you to access any IPFS URL appended to your IPFS record under your .sol domain. The setup is incredibly easy. View your domain, dropdown records and edit the IPFS record with your link

Now you are completely set up and you can access your website through the .place gateway. For example, https://builtonoyster.sol.place

3. SNS Manager

Build and manage your identity with our smart SNS manager on Web3 and unlock the value of your on-chain personality

PreviousCross-Chain Domain (Experimental)NextX Handle Registration

Last updated

Was this helpful?