> For the complete documentation index, see [llms.txt](https://docs.4everland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.4everland.org/hositng/guides/domain-management/sns-setup-guide.md).

# SNS Setup Guide

<figure><img src="/files/6Bg1vMgihxxt1vnLyfHw" alt=""><figcaption><p>Solana Name Service (SNS) Domain Setup Guide for 4EVERLAND IPFS Deployments</p></figcaption></figure>

## Introduction to SNS Integration

4EVERLAND supports **Solana Name Service (SNS)** domains, enabling seamless mapping of `.sol` names to your IPFS projects. SNS domains offer:<br>

* **Decentralized Ownership**: Controlled via Solana private keys (no central registrars)
* **On-Chain Resolution**: Map domains to IPFS CIDs, Solana addresses, or custom data
* **Cost Efficiency**: Low registration fees (≈ $5–$10/year) and minimal gas costs on Solana
* **Web3 Native**: Works with Solana wallets (Phantom, Slope, Trust Wallet) and dApp browsers

{% hint style="info" %}
**Current Support**: IPFS projects only | **Roadmap**: Arweave/Internet Computer support
{% endhint %}

## Prerequisites

1. **Owned SNS Domain**:
   * Register via [SNS App](https://www.sns.id/?ref=4everland) (e.g., `yourproject.sol`)
   * Ensure ownership by controlling the associated Solana wallet private key
2. **Deployed IPFS Project**:
   * Live on 4EVERLAND (Dashboard → Projects → \[Project] → Details)
3. **Solana Wallet Setup**:
   * Install Phantom/Slope Wallet (Chrome/Firefox) with Solana Mainnet configured
   * Sufficient SOL for transaction fees (≈ 0.001 SOL per transaction)

## Step 1: Add SNS Domain in 4EVERLAND

<figure><img src="/files/dNGDgtN4lAPHb5CERZpe" alt=""><figcaption><p>Add SNS Domain in 4EVERLAND</p></figcaption></figure>

**Path**: Dashboard → Projects → \[IPFS Project] → **Domains** → **Decentralized Domains** → **SNS**&#x20;

1. **Domain Input**
   * Enter your SNS domain (e.g., `yourproject.sol`)
2. **Configure On-Chain Records**
   * Click **Add** → 4EVERLAND will show IPNS & IPFS CID
   * Go to [SNS Domain Management](https://v2.sns.id/) → Edit `yourproject.sol`
   * Add new record:
     * **Value**: `ipns://k51qzi...` or `ipfs://bafybe...`
     * Save changes → Sign transaction (gas fee: \~0.001 SOL)

<figure><img src="/files/OZVKOC4e4YFkfFvUj8X0" alt=""><figcaption></figcaption></figure>

## Step 2: Confirm Resolution & Testing

1. **Transaction Confirmation**
   * Check Solana Explorer: Search your wallet address for `SetRecord` events
2. **Resolution Testing**
   * **Web3 Wallet**: Open `yourproject.sol` in Phantom Browser (auto-resolves to IPFS content)
   * **Non-Web3 Browser**: Use 4EVERLAND Gateway → `https://yourproject.4sol.xyz`

{% hint style="info" %}

### 📞 Support Resources

* **Live Chat**: Join [Discord server](https://discord.com/invite/Cun2VpsdjF) → #Open a ticket
* **Email**: <contact@4everland.org> (include domain name & project ID in subject)
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.4everland.org/hositng/guides/domain-management/sns-setup-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.