# The NFD Protocol ### What is NFDomains? Non-fungible domains (NFDs) are unique, digital identities built on Algorand. Unlike traditional DNS domains which are used to identify and locate resources on the internet, NFDomains are used to identify and locate resources on the Algorand blockchain and elsewhere. Users can link any data they want to an NFD, with the ability to verify certain records like their Twitter, Discord, Bluesky, Telegram, email, and more.\ \ `staci.algo` ➡️ `DC7K77...EK3Qv` The [NFD registry contract](/smart-contracts/resolving-nfds/nfd-registry) is the permissionless registrar for the `.algo` TLD. The contract allows for trustless and decentralized minting of unique NFDs, with ownership secured and verified by the Algorand blockchain. *** ### app.nf.domains Users can register and manage their NFDs through the [nf.domains](http://app.nf.domains) web interface. Users can also interact directly with the contracts to mint and manage NFDS - see the [Smart Contracts](/smart-contracts/resolving-nfds) section. *** ### Resolution One of the key utilities of an NFD is its ability to perform forward and reverse resolution. #### Forward Resolution Forward Resolution is the process of converting a name into an address, along with loading any associated records tied to that name. These metadata records may include a profile picture, Discord, Twitter, Telegram, GitHub, email, and more. Example: `staci.algo` ➡️ `Algo Address: DC7K77...EK3Q` `BTC Address: jk2h3...yu23` `Twitter: @staciwarden` `Discord: staci#2493` Integrating forward resolution into an application can be as simple as a few lines of code! For more details on how to implement forward resolution, see the [Address Resolution](/smart-contracts/resolving-nfds) documentation. #### Reverse Resolution Reverse Resolution is the process of converting an address into a human-readable name. This is a crucial feature of the NFD system, as it allows any address to be easily identified by its associated name. Rather than displaying long, confusing addresses, you can show the names of the users behind them. Example: `DC7K77...EK3Q` ➡️ `staci.algo` Implementing reverse resolution in an application can also be achieved with just a few lines of code! To learn more about how to implement reverse resolution, check out the [Address Resolution ](/smart-contracts/resolving-nfds)documentation. *** ### Segments Segments (subdomains) can be minted from any root domain, given the root domain owner allows it. Root owners have the ability to open minting and set a price for their segments. They can also lock their domains to prevent anyone from minting a segment from it. {% hint style="info" %} [Learn more about Segments!](/platform/segments-subdomains) {% endhint %} *** ### # Why Own an NFD? ### **Simplify transactions** Simplify transactions with human-readable names like *staci.algo* instead of long, complex wallet addresses. Users are far less likely to make errors when sending crypto to an NFD than to a traditional 58-character address. Non-Fungible Domains (NFDs) are integrated across all major Algorand wallets, explorers, and dApps, making sending and receiving crypto easier, faster, and more transparent. `staci.algo` ➡️ `Algo Address: DC7K77...EK3Q` *** ### **Self-sovereign identity** Your entire digital identity—linked wallets, assets owned, assets created, social links, bio, DIDs—unified in one profile that follows you across the ecosystem. Say goodbye to creating a new profile for every site and hello to seamless, portable identity.

*** ### **On-chain and off-chain verifications** You can optionally verify your Discord, Twitter, Telegram, Bluesky, Github, email, and domain, enabling you to establish credibility and trust across various platforms. This allows you to carry your off-chain reputation on-chain & vice versa, building a strong and cohesive digital identity.

*** ### **Native DNS — your NFD is a real domain** Your NFD isn’t just a name — it’s a fully functional domain powered by native DNS. Through the `.algo.xyz` TLD, names like `app.algo` become `app.algo.xyz` and are accessible from any browser, email client, or DNS-aware application worldwide. **What you can do with NFD DNS:** * **Host a website** — Point your NFD to a web server, Vercel, Netlify, or any hosting provider with A, AAAA, and CNAME records. * **Receive email** — Configure MX records to use Gmail, ProtonMail, or any email provider at your NFD. * **Secure with SSL** — Use CAA records to control which Certificate Authorities can issue certificates for your domain. * **Verify ownership** — Add TXT records for Google, Bluesky, SPF, DMARC, and other verification systems. * **Custom redirects** — Each NFD gets its own `.algo.xyz` URL that defaults to your profile page and can be set to redirect anywhere. All DNS records are stored on-chain in your NFD’s smart contract, giving you self-custodial, cryptographically enforced control — no third-party registrar required. Record changes are signed transactions, and advanced setups like multisig or DAO-controlled domains are fully supported. The DNS resolver itself is [open-source](https://github.com/TxnLab/nfd-coredns), so anyone can run their own. Learn more in the [Native DNS for NFDs](/platform/manage/native-dns-for-nfds) documentation. *** ### **Empowering collectors and creators** Multiple wallets can be linked to a single NFD enabling creators to connect all of their works under a single profile. Collectors or creators can advertise their listings on their 'for sale' page, which aggregates listings across all major NFT marketplaces.

*** ### **Suite of integrations** NFDs are built into the Algorand ecosystem with 60+ unique [integrations](/resources/integrations), including [Pera](https://perawallet.app/), [Defly](https://defly.app/), [Allo](https://allo.info/), [Folks Finance](https://folks.finance/), and many more.

*** ### **Multi-chain compatible** NFDs are multi-chain! Any integrator wishing to add support for NFDs can read NFD data from an Algorand node or our public API. You could use your NFD on Solana or Ethereum if the platform supported it!

*** ### **Built on** [**Algorand**](https://www.algorand.foundation/) NFDs are built on Algorand, one of the fastest and most efficient blockchains. Whether you're updating your avatar or adding a new address, every on-chain interaction completes in seconds with ultra-low transaction fees, giving you a smooth and reliable experience.

*** # Mint ### Mint Overview On the *Mint* tab, search for any name you'd like to register. The NFD must be an alphanumeric containing letters `A-Z` and / or numbers `0-9`, no special characters are allowed. You can browse the [marketplace](/platform/marketplace) for NFDs that were registered and listed for sale. *** ### Pricing The NFD registry charges a yearly fee for name registrations. This fee is paid in ALGO, but denominated in USD. These fees fund the development of NFDomains and prevent the speculative registering of names (domain-squatting). | Characters | Price Per Year | | ----------------------------------------- | ------------------- | | [Segments](/platform/segments-subdomains) | $5 + Root Owner Fee | | 5+ | $6 | | 4 | $12 | | 3 | $30 | | 2 | $90 | | 1 | $315 | *** #### Carry Cost Every NFD has a carry cost of `~2.5 ALGO` which is paid once upon minting a new NFD. These fees are for storage and other on-chain costs. *** ### Inflation Schedule & Maximum Registration Time The protocol has a built in inflation parameter set to `2%` per year. The date for the first price hike is 1 year from V3 launch, `September 02, 2025`. The protocol has a cap of `20` years that an NFD can be registered for. *** # Manage ### Manage Page The Manage tab allows you to see all of your NFDs (owned, for sale, and reserved), as well as renewal dates, expirations, sales history, and [offers](/platform/marketplace#offers).

*** ### Transfer an NFD Since NFDs are smart contracts, wallets like Pera and Defly don't yet support transferring them like ASAs. Users can use the transfer feature on app.nf.domains. To transfer an NFD, navigate to an NFDs profile page and select *transfer.*

Enter the NFD or wallet address that you want to transfer to and select *transfer.* If you toggle *Give NFD as a Gift* you will transfer 1.108 ALGO to the recipient to cover the cost of claiming. The recipient can claim the NFD in their [Reserved ](/platform/marketplace#offers-and-reserved)tab (located on the Manage page).

{% hint style="warning" %} Any assets in the NFDs vault will be transferred with the NFD! Make sure to check your vault contents prior to transferring! {% endhint %} {% hint style="warning" %} Transferring an NFD clears all the NFDs metadata, including all verified fields! {% endhint %} *** # Setting Metadata Records ## Setting Metadata Records To set metadata records, navigate to an NFD you own and select *Edit*. On mobile you can find *Edit* in the three dot menu

The first tab on the sidebar is for addresses.

*** ### Addresses The address that will resolve when sending to an NFD ([forward resolution](/#forward-resolution)) will be the *owner address* by default*,* **unless** a *verified* or *unverified address* are set. By linking a *verified* or *unverified address* you are selecting that address to receive funds instead of the *owner address.* This address becomes known as the NFD's *primary address*. By setting a *verified deposit address*, integrators are able to trust the [reverse resolution](/#reverse-resolution), matching your wallet to your NFD. Without the address being verified, the reverse resolution cannot be trusted as anyone can paste an address in an NFD. {% hint style="info" %} The owner address and the linked addresses are **independent**. {% endhint %} If you wish to link multiple *verified addresses* to one NFD you need to use a wallet that allows selecting multiple accounts at once, such as [Pera ](/resources/new-to-algorand)or [Defly](/resources/new-to-algorand). To verify multiple addresses we require users to sign for both account A and account B in the same transaction group. If you have multiple NFDs linked to the same *verified address*, you can pick which NFD you'd like to be displayed on reverse resolution by setting your *primary NFD*. This can be found in the wallet menu. {% embed url="" %} Setting Addresses {% endembed %} *** ### Other Records Other metadata records can be set in the Edit -> Metadata tab. These include profile picture, banner, bio, name, email address, physical address, Twitter, Bluesky, Discord, Telegram, Github, LinkedIn, web domain, [algo.xyz redirect](/platform/manage/algo.xyz), and custom metadata records.

Certain metadata records can be verified off-chain in the Verification tab. Once records are set in the appropriate metadata fields in the Metadata tab, you're able to verify those in the Verification tab. Twitter, Bluesky, Github, web domain, email, avatar & banner can be verified through the verification tab. Telegram and Discord both require users to interact with NFD bots to verify. {% embed url="" fullWidth="false" %} Verifying Metadata {% endembed %} *** # Bluesky Verification {% hint style="warning" %} Must be a Root NFD on at least version 3.x. {% endhint %} In Bluesky, go to: * Settings * Change handle * Select 'I have my own domain' * Enter: xxxx.algo.xyz for domain (ie: patrick.algo.xyz) * Pick 'no dns panel' * Copy the entire DID value it shows in the 'that contains the following' field * On Android, select 'copy file contents' In your NFD, go to: * Edit metadata * Paste the DID value into the `blueskydid` field * Update the NFD * Scroll back up to the `blueskydid` field and hit verify * Select 'start verification' * Post the verification challenge to Bluesky * Confirm on NFDs (allow up to a few minutes) Once your Bluesky account is verified in your NFD, go back to Bluesky, and go to: * Settings * Change handle * Select 'I have my own domain' * Enter: xxxx.algo.xyz for domain (ie: patrick.algo.xyz) * Pick 'no dns panel' * Select 'verify text file' Your Bluesky handle will now be your NFD!\\ {% embed url="" %} Video Tutorial {% endembed %} # Twitter Verification ## Twitter Verification * Enter your handle into the Twitter field of your NFD (see [Setting Metadata](/platform/manage/setting-metadata-records)) & update it. * Once the field is updated, you will see a 'verify' option appear below the Twitter field. You can also get there by navigating from Metadata to Verification on the sidebar (drop-down on mobile). * Select 'Verify' and then 'Start Verification' * Tweet out the verification challenge (allow \~30 seconds for the post to be posted to the timeline) * Come back to NFDomains and hit confirm * If successful your Twitter handle will move into the Verified section at the top of your profile. To be ranked on the Leaderboard, see[ Analytics](/platform/analytics/twitter-leaderboard). {% embed url="" %} Verifying Twitter {% endembed %} *** # Discord Verification To verify Discord you must interact with our Discord bot in the **#verify-nfd** channel and follow the instructions. [Discord Verification Channel](https://discord.gg/TazX7rFRu3) {% embed url="" %} Discord Verification {% endembed %} *** # Telegram Verification To verify Telegram you must interact with our Telegram bot which can be found in edit -> verifications -> follow instructions. {% embed url="" %} Verifying Telegram {% endembed %} *** # Github Verification ## Personal Verification To verify Github, enter your handle into the Github field of your NFD (see [Setting Metadata](/platform/manage/setting-metadata-records)) & update it. Once the field is updated, you will see a 'verify' option show up in the Verification tab, as well as in the Metadata tab below the Github field.

When you click verify, you'll see a dialog to 'start verification'. Click that. You'll next see a modal like this:

Follow the directions, creating a **PUBLIC** gist for your user with the contents as specified. Once completed, come back to the NFD page and click Confirm. If your handle is an organization, do NOT create a gist but follow the changes below. *** ## Organization Verification Follow the directions above but instead of creating a gist, set the nfd-verify:xxx challenge value into a root file called "**.nfd**" in the **.github** Organization Repo for your organization. If you don't already have a .github repo, one easy way of doing it is to click the 'create readme' link on the right of your organizations github profile page. You can also click the '+' dropdown menu and click New Repository - naming it .github.

Clicking 'create a README file' will create your .github repo

If you choose the 'New Repository' route. Here is an example - **notice it must be public** !

If you create the empty .github repo like above, then click the 'creating a new file' link.

followed by naming the file '.nfd' and pasting in the challenge:

Commit the changes and then switch back to the NFD page and click Confirm. *** # Assets & Vaults ### Assets The *Assets Owned* tab aggregates NFTs, NFDs, and Tokens across all of your accounts (owner account, linked accounts, and vault). You're able to manage all of your assets here (send, move to vault, choose a PFP / banner, etc.).

*** ### Vaults Vaults are distinct Algorand accounts associated with an NFD. These accounts have the ability to auto opt-in to assets that are sent to them. #### What’s an Opt-In? Before an Algorand account can receive a specific asset it must opt-in to receive it. While this is a nice feature to prevent unwanted assets from entering your wallet, it adds friction when trying to transact new assets. This is a major issue for airdrops and giveaways, but also for regular users sending each other NFTs which all have unique ASA IDs. #### NFD Vault Features Newly minted NFDs will have Vault functionality. Existing NFDs may need to be upgraded to at least `Version 2.11` to enable Vaults. See the [Smart Contract](/platform/manage/smart-contract) section to learn how to upgrade your NFDs contract. #### **Auto opt-in / opt-out** Vaults will auto opt-in to any asset they are sent, and they will also auto opt-out when you send an asset resulting in a zero balance which helps manage the minimum balance requirement (MBR) of the account. The sender pays the .1 ALGO MBR and does not get it back, preventing the spamming of unwanted assets by adding a cost. **Vaults default to being unlocked.** The Vault can be unlocked or locked at will, offering a high degree of control to the user. Don’t want random tokens showing up? Keep your Vault locked! Find the toggle in your Assets -> Vault page, or in Edit -> Vault. {% embed url="" %} All About Vaults {% endembed %} *** ### **Asset Management** NFD Vaults offer seamless asset management, allowing users to transfer assets between their accounts and Vault, or to any other NFD account or its Vault. You can also access the Send feature through the Wallet Menu and through the Search.

### Lock & Unlock Vault Newly minted or upgraded NFDs come with unlocked Vaults. If you wish to lock your NFD, there is a toggle on the Assets -> Vault page to lock or unlock.

Alternatively, you can go into an owned NFD and go to Edit -> Vault -> toggle locked or unlocked -> Update Vault.

### Send to a Vault / From a Vault To utilize vaults you need to use the NFD app or the Defly wallet. Pera wallet has not integrated NFD Vaults. 1\) Generic 'Send' can be found in the Wallet Modal at the top right of your screen, or through the search bar when looking for a name. You can send to any NFD or any NFDs Vault as long as they have an upgraded contract and an unlocked Vault.

2\) From the Assets Owned or Vault page of an NFD, click the three little dots for options. You can Move to Vault, Move to Deposit Account, and Send from this menu.

### Transfer an NFD with Contents The Vault is the NFD, meaning that all assets travel with it. This feature enables users to sell or transfer their NFD along with all of its vaulted assets, facilitating easy trading of large NFT collections. Be aware of this when selling an NFD!

*** ### Notifications To get notifications of assets sent to your Vault, add the Vault address as a 'Watch Account' in Pera or Defly and ensure notifications are turned on. Find the Vault address in your NFDs Details.

To add a watch account in Pera, hit the `+` icon -> I want to create an account -> Add watch account -> Paste in the Vault address To add a watch account in Defly, hit the `+` icon -> Contact -> Paste in the Vault Address *** # Smart Contract ### NFD Versions NFDs are currently on `Version 3.7` (V3) of the [NFD Registry contract](/smart-contracts/resolving-nfds/nfd-registry). There were major changes between V1 and V2, as well as V2 and V3. Prior to `Version 1.16`, NFDs didn't have Segments. Prior to `Version 2.11`, NFDs didn't have Vaults. `Version 2.12` was needed to allow V2 NFDs to mint Segments with renewals. Any NFD prior to `Version 3.01` is considered a legacy NFD, meaning it doesn't have renewal fees. If a V2 NFD is upgraded to V3, the NFD owner will need to start paying renewal fees. The NFD protocol will never force V1 / V2 owners to upgrade to V3. *** ### Upgradable Smart Contracts NFDs are upgradable and NFDomains takes full-advantage of this as Algorand releases new features. NFDomains pushes updates along with update notes on what has been changed and why. #### Upgrading your NFDs Smart Contract To upgrade your smart contract, navigate to an owned NFD -> *Edit* -> *Smart Contract* -> *Upgrade Contract*.

*** ### Lock / Unlock Smart Contract To allow maximum user control, users can toggle between locking and unlocking their NFD to upgrades. If you lock your contract, your NFD cannot be upgraded until you unlock it. *** # Algo.xyz Users are able to use the `algo.xyz` domain to redirect to any webpage they'd like. To resolve an NFD via DNS, users simply need to append `.xyz` at the end of the name. Example:\ `silvio.algo` ➡️ [`silvio.algo.xyz`](https://silvio.algo.xyz/) {% hint style="info" %} For Segments you have to use the following format for redirects: `algo.xyz/segment.root` {% endhint %} By default the redirect will go to your profile page. If you want to redirect to an entirely different page, paste the URL in the *Redirect to* field. To confirm your changes make sure to hit "Update URL" in the bottom right corner.

*** # Native DNS for NFDs Expose Your .algo Domain via .algo.xyz ## Introduction With the release of DNS support in NFD on Algorand, you can now bind globally-resolvable DNS records to your .algo name—served directly from the Algorand blockchain. Through integration with the `.algo.xyz` TLD, names like `somedapp.algo` become `somedapp.algo.xyz`—and can be accessed via any DNS client, browser, or application worldwide. **Your NFD becomes a real, working domain:** * `patrick.algo.xyz` - accessible via standard DNS This means you can point your NFD to a website, receive email, configure SSL certificates, and more—all with records you control on-chain. This creates a true **Web3 DNS system** using **native DNS protocol standards**, while retaining: * On-chain data control * Self-custodial ownership * Trustless resolution *** ## How It Works ``` 1. You configure DNS records in your NFD (stored on Algorand blockchain) ↓ 2. The NFD DNS service reads your on-chain data ↓ 3. Standard DNS queries resolve your NFD as a normal domain ``` When someone queries `patrick.algo.xyz`, the NFD DNS service fetches your records from the blockchain and returns a standard DNS response. No special software needed—it just works with any browser or application. *** ## Background: DNS and RR Types DNS (Domain Name System) maps human-readable names to machine-usable data using **resource records (RRs)**. Common RR types include: | Type | Purpose | | ------- | ---------------------------------------------- | | `A` | IPv4 address of a host | | `AAAA` | IPv6 address | | `TXT` | Free-form text (often used for verification) | | `MX` | Mail server settings | | `CNAME` | Canonical alias (points one domain to another) | | `SRV` | Advanced service routing | | `CAA` | Certification authority authorization | Traditionally, these records are stored and managed via centralized registrars or DNS providers. In contrast, NFDs allow **you** to define these records on-chain. *** ## Architecture ### Storage Each NFD stores its DNS records in a `dns` property—structured JSON stored on-chain inside its associated Algorand smart contract. This property is: * Versioned (requires NFD v3+) * User-editable via the NFD Manager * Strictly owned/controlled by the NFD's controlling account ### Ownership & Security Ownership of DNS records is cryptographically enforced by the Algorand blockchain: * You can use single-signature wallets, multisig accounts, or smart contract wallets to own NFDs. * No third-party registrar required. * Record changes are signed transactions. This enables advanced workflows like: * Smart contracts updating DNS records automatically. * DAOs owning service domains like `community.algo`. * Multisig-controlled dApp endpoints (e.g., `swap.algo.xyz`). *** ## DNS Record Format DNS records are stored as JSON in your NFD. Each record has these fields: | Field | Required | Description | | -------- | -------- | -------------------------------------------------- | | `name` | Yes | Where the record applies (use `@` for your domain) | | `type` | Yes | Record type: A, AAAA, CNAME, MX, TXT, SRV, CAA | | `rrData` | Yes | Array of record values | | `ttl` | No | Cache time in seconds (default: 300) | ### Name Field * `@` — Your domain itself (e.g., `patrick.algo.xyz`) * `www` — A subdomain (becomes `www.patrick.algo.xyz`) * `mail` — Another subdomain (becomes `mail.patrick.algo.xyz`) * `grafana` — A subdomain (becomes `grafana.patrick.algo.xyz`) * `_dmarc` — Special subdomain for DMARC records #### Accepted name forms All of the following are accepted and resolve to the same place under your NFD (`patrick.algo`): | You write | It serves | | ---------------------- | ------------------------- | | `@` | `patrick.algo.xyz` (apex) | | `www` | `www.patrick.algo.xyz` | | `www.@` | `www.patrick.algo.xyz` | | `www.patrick.algo` | `www.patrick.algo.xyz` | | `www.patrick.algo.` | `www.patrick.algo.xyz` | | `www.patrick.algo.xyz` | `www.patrick.algo.xyz` | The `.@` suffix (e.g. `www.@`, `_dmarc.@`, `_http._tcp.@`) is the explicit canonical form—it states "this is a subname of my NFD." Bare labels like `www` work identically. {% hint style="warning" %} **Scope: every record name is rooted under your NFD.** You have DNS authority only over your own NFD and its subnames, so any `name` you store is interpreted as something *inside* your NFD's subtree. A trailing dot in a standard DNS zone file means "fully qualified—don't append the origin." In NFD context that's almost always a mistake. To avoid this footgun, any name that isn't already inside your NFD's zone is **re-rooted** under it: * `_test._tcp.` (trailing-dot, no NFD) → serves as `_test._tcp.patrick.algo.xyz` * `evil.someone-else.algo.` (a *different* NFD) → serves as `evil.someone-else.algo.patrick.algo.xyz` (you do **not** gain authority over `someone-else.algo`) When in doubt, use the `.@` suffix—it makes your intent explicit and is never re-rooted unexpectedly. {% endhint %} ### TTL (Time to Live) * **Minimum:** 60 seconds * **Maximum:** 86,400 seconds (24 hours) * **Default:** 300 seconds (5 minutes) Lower TTL = faster updates, but more DNS queries. Higher TTL = better caching, but slower propagation of changes. *** ## Managing DNS Records in Your NFD ### Editing via UI To add or modify DNS records: 1. Open the NFD Manager and select an NFD (version 3+). 2. Click **DNS Editor**. 3. Use "Add DNS Record": * **Type**: Choose one of the supported types (`A`, `AAAA`, `TXT`, etc.) * **Name**: Use `@` to represent the root of the NFD (e.g. `patrick.algo`) * **TTL**: Set time-to-live in seconds * **Value**: A string or list, depending on type (e.g. multiple IPs for an `A` record) *** ## How `.algo.xyz` Resolution Works The `.algo.xyz` TLD is backed by [**nfd-coredns**](https://github.com/TxnLab/nfd-coredns), an open-source [CoreDNS](https://coredns.io/) plugin that resolves DNS queries for Algorand NFDs by reading on-chain data directly from the blockchain. When a DNS query arrives for a domain like `patrick.algo.xyz`, the plugin: * Strips the `.xyz` suffix * Checks a local cache for previously fetched records * Queries the Algorand blockchain if needed * Converts on-chain JSON data to standard DNS resource records * Returns the response as a normal DNS reply The resolver supports all NFD DNS record types (A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, SOA, CERT) and honors TTL values. ### Run Your Own Resolver Anyone can run their own NFD DNS resolver using the Docker image: ```bash docker pull txnlab/nfd-dns:latest ``` See the [nfd-coredns GitHub repository](https://github.com/TxnLab/nfd-coredns) for configuration details and setup instructions. ### Live Resolvers * `algo.xyz` zone is currently served by: * [TxnLab Resolver](https://txnlab.dev) * [Nodely Resolver](https://nodely.io) *** ## Subdomain and Delegation Model Unlike traditional DNS, the NFD subdomain model **preserves segment ownership**. A *segment* (e.g. `api.patrick.algo`) is its own NFD with its own owner, and it **always serves its own DNS records**—regardless of who owns the root NFD. How a segment combines with the root depends on ownership. There are three cases: 1. **No segment NFD is minted** — the root NFD serves the subname directly. A record stored on `patrick.algo` with name `api` answers `api.patrick.algo.xyz`. 2. **Segment owned by the same account as the root** — the segment is **merged** with the root. The root can define sub-records that fall inside the segment, and **root records win** if both define the same name + type. This lets you manage a root NFD and the segments you own as one zone. 3. **Segment owned by a different account** — the segment alone is **authoritative** for its own subtree (`api.patrick.algo` and everything under it). The root NFD owner has no DNS authority inside it, and any root records pointing into the segment's subtree are **ignored**. This mirrors how segments are sold and operated independently. This prevents parent domains from hijacking subdomain content they do not own. {% hint style="info" %} "Authoritative" here describes the *NFD-ownership* boundary, not a DNS delegation. The plugin still answers these names directly—there is no NS referral and no delegated subzone (NFD subdomains never have NS records; see [Limitations](#limitations) below). {% endhint %} ### Resolution examples The tables below assume a root NFD of `patrick.algo`. "Resolves to" is what a DNS query actually returns. **Scenario A — no `api.patrick.algo` segment is minted (root serves the subname):** | Query | Record on `patrick.algo` | Resolves to | | ------------------------ | ------------------------ | ----------------------------------- | | `patrick.algo.xyz` A | `@` → `203.0.113.1` | `203.0.113.1` | | `www.patrick.algo.xyz` A | `www` → `203.0.113.2` | `203.0.113.2` | | `api.patrick.algo.xyz` A | `api` → `203.0.113.3` | `203.0.113.3` (root serves subname) | | `api.patrick.algo.xyz` A | *(no `api` record)* | placeholder / NODATA | **Scenario B — `api.patrick.algo` is a segment owned by the *****same***** account as the root:** | Query | `patrick.algo` defines | `api.patrick.algo` defines | Resolves to | | ---------------------------- | ---------------------- | -------------------------- | -------------------------------------- | | `api.patrick.algo.xyz` A | `api` → `1.1.1.1` | `@` → `2.2.2.2` | `1.1.1.1` (root wins the conflict) | | `api.patrick.algo.xyz` AAAA | *(none)* | `@` → `2001:db8::1` | `2001:db8::1` (segment merged in) | | `key.api.patrick.algo.xyz` A | *(none)* | `key` → `3.3.3.3` | `3.3.3.3` (segment serves its subname) | **Scenario C — `api.patrick.algo` is a segment owned by a *****different***** account:** | Query | `patrick.algo` defines | `api.patrick.algo` defines | Resolves to | | ---------------------------- | ---------------------- | -------------------------- | ------------------------------------------------ | | `api.patrick.algo.xyz` A | `api` → `1.1.1.1` | `@` → `2.2.2.2` | `2.2.2.2` (segment authoritative; root ignored) | | `key.api.patrick.algo.xyz` A | `key.api` → `1.1.1.1` | `key` → `3.3.3.3` | `3.3.3.3` (root has no authority inside segment) | | `api.patrick.algo.xyz` A | `api` → `1.1.1.1` | *(no records)* | placeholder (segment exists but empty) | *** ## Bluesky Integration If you've verified your Bluesky account with your NFD, a TXT record for `_atproto` is **automatically added**. You don't need to configure this manually. The system creates: ``` _atproto.patrick.algo.xyz. TXT "did=did:plc:abc123..." ``` This enables your NFD to serve as your Bluesky handle. *** ## Decentralized Websites (IPFS via DNSLink) You can point your NFD at content stored on IPFS — the same idea as ENS's on-chain `contenthash`, but done with a standard DNS record, so it works with existing IPFS gateways and needs no special support. Add a TXT record at `_dnslink.@` whose value is a DNSLink path: * `dnslink=/ipfs/` — an immutable snapshot (the content for that exact CID) * `dnslink=/ipns/` — a mutable pointer you can update without changing DNS ```json { "name": "_dnslink.@", "type": "TXT", "rrData": ["\"dnslink=/ipfs/bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi\""], "ttl": 300 } ``` This serves: ``` _dnslink.patrick.algo.xyz. TXT "dnslink=/ipfs/bafybei..." ``` **Viewing it:** any IPFS gateway resolves it, e.g. `https://ipfs.io/ipns/patrick.algo.xyz/` or `https://dweb.link/ipns/patrick.algo.xyz/`. For direct browser access at `patrick.algo.xyz`, point your `@` record (A/CNAME) at a DNSLink-aware gateway (e.g. a self-hosted Kubo DNSLink gateway or Cloudflare's web3 gateway); the gateway reads the `_dnslink` record by Host header and serves the IPFS content. **Why this works:** unlike ENS — where `contenthash` lives on-chain and a gateway/browser must read the chain to translate it — the NFD DNS service answers DNS directly, so the standard DNSLink TXT convention is all you need. The `_dnslink` label is handled like any other underscore-prefixed name (the same mechanism behind `_dmarc` and `_atproto`). *** ## Limitations 1. **Segment depth**: The `.algo` name may have at most **4 labels**, *not counting* leading `_`-prefixed service labels. So `key.segment.patrick.algo` (4 labels) resolves, but `a.key.segment.patrick.algo` (5 labels) is rejected. Underscore service labels are exempt, so `_http._tcp.segment.patrick.algo` still works. 2. **No NS records for subdomains**: Your NFD subdomains are not delegated zones. NS records only work at the zone apex (`algo.xyz` itself). 3. **Record types**: The following types are supported: A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, SOA, CERT 4. **Expiration**: If your NFD registration expires, DNS records will return a default placeholder until renewed. *** ## Benefits Summary | Feature | Traditional DNS | NFD DNS | | --------------------------- | --------------- | ------- | | Registrar Required | Yes | No | | On-chain ownership | No | Yes | | Smart contract control | No | Yes | | Multisig/domain DAO control | No | Yes | | Trustless resolution | No | Yes | | Global compatibility | Yes | Yes | *** ## Next Steps * [DNS Record Types](/platform/manage/native-dns-for-nfds/dns-record-types) — Complete reference for all supported record types with examples * [Testing & Troubleshooting](/platform/manage/native-dns-for-nfds/testing-and-troubleshooting) — Verify your DNS configuration and debug common issues *** ## Conclusion The `.algo.xyz` DNS bridge transforms your Algorand NFD into a global, resolvable domain using native internet infrastructure. This is a powerful blend of decentralization, security, and real-world interoperability—and it's available now. **Your domain. Your keys. Your records.** Accessible from anywhere. # DNS Record Types Complete reference for DNS record types supported by NFD This page provides detailed examples and configurations for each DNS record type supported by NFD. {% hint style="info" %} In the examples below, `@` is your NFD's apex and bare labels like `www` or `_dmarc` are subnames. You can also write subnames explicitly with the `.@` suffix (e.g. `www.@`). Every `name` you store resolves *under your NFD* —see [Name Field](/platform/manage/native-dns-for-nfds#name-field) for the accepted forms and scope rules. {% endhint %} *** ## Supported Record Types ### A Record — IPv4 Address Point your domain to a server's IPv4 address. ```json { "name": "@", "type": "A", "rrData": [ "192.168.1.1" ], "ttl": 300 } ``` **Multiple IP addresses** (for load balancing): ```json { "name": "@", "type": "A", "rrData": [ "192.168.1.1", "192.168.1.2" ], "ttl": 300 } ``` *** ### AAAA Record — IPv6 Address Point your domain to a server's IPv6 address. ```json { "name": "@", "type": "AAAA", "rrData": [ "2001:db8::1" ], "ttl": 600 } ``` *** ### CNAME Record — Alias Point a subdomain to another domain name. ```json { "name": "www", "type": "CNAME", "rrData": [ "myapp.vercel.app." ], "ttl": 300 } ``` {% hint style="info" %} CNAME targets must end with a trailing dot (e.g., `myapp.vercel.app.`). {% endhint %} **Common uses:** * Point `www` to your hosting provider * Point subdomains to cloud services (Vercel, Netlify, etc.) *** ### MX Record — Email Configure where email should be delivered. ```json { "name": "@", "type": "MX", "rrData": [ "10 mail.example.com.", "20 backup-mail.example.com." ], "ttl": 3600 } ``` The number before the server is the **priority**—lower numbers are tried first. {% hint style="warning" %} MX record hostnames must end with a trailing dot (e.g., `mail.example.com.`). {% endhint %} *** ### TXT Record — Text Data Store text data for verification, email authentication, and more. **SPF (email sender verification):** ```json { "name": "@", "type": "TXT", "rrData": [ "\"v=spf1 include:_spf.google.com ~all\"" ], "ttl": 300 } ``` **DMARC (email policy):** ```json { "name": "_dmarc", "type": "TXT", "rrData": [ "\"v=DMARC1; p=quarantine; rua=mailto:admin@example.com\"" ], "ttl": 3600 } ``` **Domain verification:** ```json { "name": "@", "type": "TXT", "rrData": [ "google-site-verification=abc123xyz" ], "ttl": 300 } ``` *** ### SRV Record — Service Discovery Define the location of specific services. ```json { "name": "_http._tcp", "type": "SRV", "rrData": [ "10 5 80 web.example.com." ], "ttl": 300 } ``` **Format:** `priority weight port target` | Field | Description | | ---------- | -------------------------------------------- | | `priority` | Lower = preferred | | `weight` | Load balancing between same priority servers | | `port` | Service port number | | `target` | Server hostname (must end with `.`) | *** ### CAA Record — SSL Certificate Control Specify which Certificate Authorities can issue SSL certificates for your domain. ```json { "name": "@", "type": "CAA", "rrData": [ "0 issue \"letsencrypt.org\"", "0 issuewild \"letsencrypt.org\"" ], "ttl": 3600 } ``` **Tags:** | Tag | Purpose | | ----------- | -------------------------------------- | | `issue` | Authorize CA for regular certificates | | `issuewild` | Authorize CA for wildcard certificates | | `iodef` | Report violations to an email/URL | *** ## Complete Configuration Examples ### Basic Website Point your NFD to a web server and create a www alias: ```json [ { "name": "@", "type": "A", "rrData": [ "203.0.113.50" ], "ttl": 300 }, { "name": "www", "type": "CNAME", "rrData": [ "@" ], "ttl": 300 } ] ``` *** ### Website + Email (Google Workspace) Host a website and receive email via Google Workspace: ```json [ { "name": "@", "type": "A", "rrData": [ "203.0.113.50" ], "ttl": 300 }, { "name": "www", "type": "CNAME", "rrData": [ "@" ], "ttl": 300 }, { "name": "@", "type": "MX", "rrData": [ "1 aspmx.l.google.com.", "5 alt1.aspmx.l.google.com.", "5 alt2.aspmx.l.google.com." ], "ttl": 3600 }, { "name": "@", "type": "TXT", "rrData": [ "\"v=spf1 include:_spf.google.com ~all\"" ], "ttl": 300 } ] ``` *** ### Vercel/Netlify Deployment Point your domain to a cloud hosting platform: ```json [ { "name": "@", "type": "A", "rrData": [ "76.76.21.21" ], "ttl": 300 }, { "name": "www", "type": "CNAME", "rrData": [ "cname.vercel-dns.com." ], "ttl": 300 } ] ``` *** ### Full Professional Setup Complete configuration with website, email, SSL, and verification: ```json [ { "name": "@", "type": "A", "rrData": [ "203.0.113.50" ], "ttl": 300 }, { "name": "www", "type": "CNAME", "rrData": [ "@" ], "ttl": 300 }, { "name": "@", "type": "MX", "rrData": [ "10 mail.protonmail.ch.", "20 mailsec.protonmail.ch." ], "ttl": 3600 }, { "name": "@", "type": "TXT", "rrData": [ "\"v=spf1 include:_spf.protonmail.ch ~all\"" ], "ttl": 300 }, { "name": "_dmarc", "type": "TXT", "rrData": [ "\"v=DMARC1; p=quarantine\"" ], "ttl": 3600 }, { "name": "@", "type": "CAA", "rrData": [ "0 issue \"letsencrypt.org\"", "0 issuewild \"letsencrypt.org\"" ], "ttl": 3600 } ] ``` *** ## Developer Integration You can manage DNS records on NFDs programmatically using: * Algorand SDKs (Go, JS, Python) * Direct JSON updates to the `dns` property via contract transactions * On-chain logic to automate record updates from a contract The records are stored in a structured format within the NFD's application state. *** ## Quick Reference | I want to... | Record Type | Example rrData | | ---------------------------- | ------------------ | --------------------------------- | | Point domain to IP | A | `["1.2.3.4"]` | | Point to IPv6 | AAAA | `["2001:db8::1"]` | | Create subdomain alias | CNAME | `["target.com."]` | | Receive email | MX | `["10 mail.provider.com."]` | | Add verification | TXT | `["verification-code"]` | | Email authentication | TXT | `["\"v=spf1 include:... ~all\""]` | | Point domain to IPFS content | TXT (`_dnslink.@`) | `["\"dnslink=/ipfs/\""]` | | Restrict SSL issuers | CAA | `["0 issue \"letsencrypt.org\""]` | | Service discovery | SRV | `["10 5 80 server.example.com."]` | # Testing & Troubleshooting Test and debug your NFD DNS configuration After configuring your NFD DNS records, use this guide to verify they're working correctly and troubleshoot common issues. *** ## Testing Your DNS Records Use the `dig` command to verify your records are resolving correctly. ### Test A Record ```bash dig patrick.algo.xyz A ``` ### Test AAAA Record ```bash dig patrick.algo.xyz AAAA ``` ### Test MX Records ```bash dig patrick.algo.xyz MX ``` ### Test TXT Records ```bash dig patrick.algo.xyz TXT ``` ### Test a Subdomain ```bash dig www.patrick.algo.xyz CNAME ``` ### Test Bluesky Verification ```bash dig _atproto.patrick.algo.xyz TXT ``` **Test IPFS DNSLink:** ```bash dig _dnslink.patrick.algo.xyz TXT ``` ### Quick Test (Short Output) Use `+short` for concise results: ```bash dig +short patrick.algo.xyz A dig +short foo.patrick.algo.xyz TXT ``` {% hint style="info" %} You should see your configured records in the ANSWER SECTION of the response. {% endhint %} *** ## NFD Segments (Subdomains) A segment (e.g. `api.patrick.algo`) is its own NFD with its own owner, and it **always serves its own DNS records**. How a segment combines with the root NFD depends on ownership. See the [Subdomain and Delegation Model](/platform/manage/native-dns-for-nfds#subdomain-and-delegation-model) for the full explanation; the table below is a quick reference. ### Rules * If no segment NFD is minted, the **root** NFD serves the subname (set an `api` record on `patrick.algo`). * If a segment is owned by the **same account** as the root, the two are merged and **root records win** on a conflict. * If a segment is owned by a **different account**, the **segment is authoritative**—the root's records pointing into it are ignored. * Maximum depth: the `.algo` name may have at most **4 labels**, not counting leading `_`-prefixed service labels (e.g. `key.api.patrick.algo` resolves; `a.key.api.patrick.algo` is rejected). ### Quick reference | Setup | Query | Resolves to | | ------------------------------------------------------------- | --------------------------- | ----------------------------------- | | Root only, `api` record on `patrick.algo` | `api.patrick.algo.xyz` | root's `api` record | | Segment `api.patrick.algo`, same owner, conflicting `@`/`api` | `api.patrick.algo.xyz` | root's record (root wins) | | Segment `api.patrick.algo`, same owner, only segment has AAAA | `api.patrick.algo.xyz` AAAA | segment's record (merged) | | Segment `api.patrick.algo`, different owner | `api.patrick.algo.xyz` | segment's own record (root ignored) | | Segment exists but defines no records | `api.patrick.algo.xyz` | placeholder | *** ## Troubleshooting ### Records Not Showing Up **Symptoms:** `dig` returns no answer section or old data. **Solutions:** 1. **Wait a few minutes** — There's caching at multiple levels (your local DNS, the resolver, etc.) 2. **Verify JSON syntax** — Malformed JSON will prevent records from being served 3. **Check name format** — Use `@` for the root domain, or a bare subdomain name (e.g., `www`, `grafana`) 4. **Confirm NFD version** — DNS requires NFD v3 or higher 5. **Watch the trailing dot** — A name with a trailing dot that isn't inside your NFD's zone (e.g. `_test._tcp.`) is re-rooted under your NFD, so it serves at an unexpected place like `_test._tcp.patrick.algo.xyz`. Use the `@` or `subdomain.@` form to be explicit. *** ### Getting NXDOMAIN **Symptoms:** `dig` returns `NXDOMAIN` (domain does not exist). **Solutions:** 1. **Ensure your NFD exists** — The NFD must be minted and active 2. **Check expiration** — Expired NFDs return placeholder responses 3. **Verify domain suffix** — You must query `*.algo.xyz` 4. **Check for typos** — Double-check the NFD name spelling *** ### Subdomain Returns Someone Else's Records **Symptoms:** A subdomain like `api.patrick.algo.xyz` returns records you didn't set, and your root NFD's `api` record is ignored. **Cause:** `api.patrick.algo` has been minted as a **separate segment NFD owned by a different account**. A different-owner segment is authoritative for its own subtree, so it serves its own records and any record you set on the root NFD pointing into that subtree is ignored. See the [Subdomain and Delegation Model](/platform/manage/native-dns-for-nfds#subdomain-and-delegation-model). **Solutions:** 1. **Check segment ownership** — If you (or the same account) own both the root and the segment, the segment is merged and your root records win on a conflict. 2. **Set records on the segment** — To control a segment owned by a different account, edit that segment's NFD directly. *** ### Name Rejected or NXDOMAIN on a Deep Name **Symptoms:** A deeply nested name (e.g. `a.key.api.patrick.algo.xyz`) returns `NXDOMAIN` or never resolves. **Cause:** The `.algo` name exceeds the depth limit. A query name may have at most **4 labels**, not counting leading `_`-prefixed service labels. **Solutions:** 1. **Flatten the name** — `key.api.patrick.algo` (4 labels) resolves; `a.key.api.patrick.algo` (5 labels) does not. 2. **Service labels are exempt** — Underscore-prefixed labels like `_http._tcp` don't count toward the limit, so `_http._tcp.api.patrick.algo` is fine. *** ### Email Not Working **Symptoms:** Emails to your domain bounce or don't arrive. **Solutions:** 1. **MX record format** — Priority number must come before the hostname: * Correct: `"10 mail.example.com."` * Wrong: `"mail.example.com. 10"` 2. **Trailing dot** — MX hostnames must end with a period: * Correct: `"10 mail.example.com."` * Wrong: `"10 mail.example.com"` 3. **Add SPF record** — Most email providers require SPF: ```json { "name": "@", "type": "TXT", "rrData": ["\"v=spf1 include:_spf.yourprovider.com ~all\""], "ttl": 300 } ``` 4. **Add DKIM** — Check your email provider's documentation for required DKIM records 5. **Check DMARC** — Some providers require DMARC policy *** ### SSL Certificate Issues **Symptoms:** Certificate Authority won't issue a certificate. **Solutions:** 1. **Check CAA records** — If you have CAA records, ensure they authorize your CA: ```json { "name": "@", "type": "CAA", "rrData": ["0 issue \"letsencrypt.org\""], "ttl": 3600 } ``` 2. **Remove restrictive CAA** — If unsure, you can remove CAA records to allow any CA 3. **Wait for propagation** — Some CAs cache DNS results; wait and retry *** ### CNAME Not Working **Symptoms:** Subdomain doesn't redirect to target. **Solutions:** 1. **Use trailing dot** — Target hostname must end with a period: * Correct: `["myapp.vercel.app."]` * Wrong: `["myapp.vercel.app"]` 2. **CNAME only for subdomains** — You cannot use CNAME for the root (`@`); use A record instead 3. **Check target exists** — Verify the CNAME target domain is accessible *** ## Resources * **NFD Web App:** [app.nf.domains](https://app.nf.domains) * **NFD API Documentation:** [api-docs.nf.domains](https://api-docs.nf.domains/) * **nfd-coredns (open-source resolver):** [github.com/TxnLab/nfd-coredns](https://github.com/TxnLab/nfd-coredns) * **Docker Image:** [txnlab/nfd-dns](https://hub.docker.com/r/txnlab/nfd-dns) — `txnlab/nfd-dns:latest` * **TxnLab Resolver:** [txnlab.dev](https://txnlab.dev) * **Nodely Resolver:** [nodely.io](https://nodely.io) # Marketplace The marketplace for buying & selling NFDs which have already been minted ### Buying on the Marketplace If you find an NFD you're interested in purchasing you can either *Buy now* or *Make an offer.* You'll see the user selling the NFD and if they have social media accounts linked you could message them to negotiate. *** ### Offers and Reserved When you make an offer, it's simply a note to the owner saying 'I am willing to pay X'. If the owner is willing to accept your offer, they can change the sale price and reserve the NFD for your address. If you make an offer and it's accepted, or if someone reserves an NFD for you (same thing), you will find the NFD reserved in your Manage tab where you will need to claim it.

*** ### Selling on the Marketplace Once you own an NFD you're able to resell it through the NFD Marketplace by selecting *List for sale* on any NFD profile you own. {% hint style="info" %} Be aware that putting an NFD up for sale will **remove all metadata** you've attached, including verified fields. Also be aware, [Vault ](/platform/manage/assets-and-vaults#cc1e-1)contents move with the NFD! {% endhint %} You're able to reserve the NFD for sale for a particular address by setting a sale price as well as the wallet address. You're also able to transfer an NFD and optionally cover the fee to claim. NFDomains takes a **5% commission** on all secondary sales conducted through the marketplace. The secondary commission is enforced via the web interface, not the smart contracts. *** # Expirations ### View Your Expirations On the manage page, the *Expirations* tab will show you your expired NFDs. If they are expired but still in auction they will be in the *Reserved* tab where you're able to re-register them.

*** ### Auction When a domain expires it enters a 28-day reverse auction where the price starts at $100,000 and gradually decreases to the standard renewal price. *** ### Grace Period During the 28-day auction, the original owner retains the right to renew the domain at the standard renewal price. They can regain full ownership without needing to pay the current auction price. This gives users a 'grace period' on top of the time they paid to register. *** ### Warnings You will see a warning appear at the top of the page whenever you have NFDs close to expiration or that have already expired.

*** ### Clearing Data All metadata must be cleared before another owner can take over the NFD (via renew method). The UI will provide calls to unlink addresses and delete fields prior to the renew call if the data isn't already cleared. When an NFD is expired, and someone clears the metadata, the MBR for the box storage used by that metadata is paid to the caller. Automated services can take advantage of this and in return for them providing this decentralized service of clearing metadata, receive payment in the form of the returned MBR. # Segments (Subdomains) Segments are distinct, sovereign NFDs that can be minted off root domains, adding an additional level that is separated by a “.” ### The Basics Root domains can enable the minting of segments (subdomains), but these segments cannot mint additional sub-segments. You can mint segments from any root NFD which has segmenting *unlocked*.

Root domains have two segment minting states, *locked* & *unlocked*. This defines who is allowed to mint segments from the domain root. When *locked*, only the root owner can mint. When *unlocked*, anyone can mint at a price specified by the owner. {% hint style="info" %} Example: When **nfd.algo** is *locked*, only the owner can register **pooof.nfd.algo** as a segment. When **nfd.algo** is *unlocked*, anyone can register **pooof.nfd.algo** as a segment at the price specified by the owner. {% endhint %}

You can utilize the Segments filter on the marketplace to find unlocked roots, or segments for sale.

*** ### Fees There are two fees associated with segments, a *platform fee* and a *root owner fee*. The *platform fee* for segments is `$5`/year, see the full pricing schedule [here](/platform/mint#pricing). The *root owner fee* is determined by the root owner. Root owners receive the proceeds from *root owner fees* for their domains. If you are minting a segment from a domain you own you will only pay the *platform fee*. Example:


Segment Sale Price (USD)	Platform Fee (USD)	Root Owner Fee (USD)
5	5	0
10	5	5
25	5	20

*** ### Contract Version The minimum [contract](/platform/manage/smart-contract) version for segments is `2.12`. *** ### Limitations * Segments cannot be used as Bluesky handles * Segments must use the following format for [algo.xyz](/platform/manage/algo.xyz) redirects: `algo.xyz/segment.root` * Segments cannot mint segments *** # Analytics ### Overview NFDomains analytics track: * *Primary sales* - newly registered NFDs * *Secondary sales* - p2p trading of already minted NFDs

*** ### Sales History Sales History shows a ledger of all primary sales, secondary sales & transfers. Use the toggles to filter by sale type.

*** # Consensus Leaderboard To be listed on the Consensus leaderboard, your account needs to be online (participating in consensus). Learn more about participating in consensus [here](https://developer.algorand.org/docs/run-a-node/participate/).

*** # Donation Leaderboard Tracking donations is a great example of what NFDs can do. We currently track 7 charities. For charities we track, we track all payments sent to the specified charity account **from NFD holders** and the accounts they have linked in their NFDs.

*** When you make a donation to a tracked charity, a badge will be added to your NFDs profile.

*** # Charities Policy If you represent and/or know of a charity (501(c)(3) or equivalent) that has an Algorand wallet set-up to accept donations, please send the following information to . * Charity name & webpage * Algorand wallet address (or NFD) that is owned by the charity * Link to webpage that displays proof of their Algorand wallet address * Best contact information for you / them If you're a charity and have done all the above steps, please setup your NFD and we'll be in touch soon. * Set the '**name**' property to your charity name. This will be used in the badge of the tooltip on users' NFDs and on the donations leaderboard page. * Set the NFDs [*verified primary address*](/platform/manage/setting-metadata-records#verified-addresses) to the same address that you emailed NFDomains. If you can't sign for the account to verify it, set it as an *unverified address.* * Add a custom '**ein**' field (if US 501c(3) charity) or equivalent for your country \[ie: regnumber] and enter the EIN. See for an example. * Set the avatar and banner images to recognizable images for your charity. This data will will be used Donations Leaderboard page as well as badging on users NFDs when they have donated to this address. We will do our best to get back to you as soon as possible. Thank you! *** # Bluesky Leaderboard To be ranked on the Bluesky Leaderboard: 1. Link and [verify your Bluesky account](/platform/manage/setting-metadata-records/bluesky-verification) in your NFD 2. You must use your NFD as your Bluesky handle (not display name) The Leaderboard updates roughly once an hour. # Twitter Leaderboard To be ranked on the Twitter Leaderboard: 1. Link and [verify your Twitter account](/platform/manage/setting-metadata-records/twitter-verification) in your NFD 2. Set your display name on Twitter to match your NFD {% hint style="danger" %} **Your Twitter display name must match your NFD exactly** (aside from capitalization). {% endhint %} The Leaderboard updates roughly once an hour. *** # Resolving NFDs ## Off-Chain NFDomains provides a public [REST API](https://api-docs.nf.domains/quick-start) for integrators and the community to utilize. It provides read-only methods, as well as methods that modify the NFD contract states (minting / claiming / updating / selling, etc.) which require the caller to sign returned transactions. The UI for NFDomains uses the very same public API. {% content-ref url="/spaces/MrFth5XKC1eo3nu9xVre" %} [NFD API](https://api-docs.nf.domains/) {% endcontent-ref %} *** ## On-Chain NFDs can be resolved entirely on-chain. See the [On-Chain Reference](https://api-docs.nf.domains/reference/on-chain-reference/name-and-address-lookup) section of the API docs. {% content-ref url="/spaces/MrFth5XKC1eo3nu9xVre/pages/zYPL9zevAJiSryAII093" %} [On-Chain Reference](https://api-docs.nf.domains/reference/on-chain-reference) {% endcontent-ref %} # NFD Registry ## Registry Application IDs These are the Algorand Application IDs of the NFD registry contracts, per Algorand network. MainNet Deployment: [**760937186**](https://allo.info/application/760937186/programs/) TestNet Deployment: **84366825** BetaNet Deployment: **842656530** *** # New to Algorand? ### **Step 1: Set up a Non-Custodial Algorand Wallet** We recommend using the [Pera Wallet](https://perawallet.app/) or [Defly](https://defly.app/). A non-custodial wallet means YOU control your private keys and no-one else. You’re **solely responsible** for the safe keeping of your private keys. If you lose your private key there is no recovery process. #### **Pera Wallet / Defly Wallet Set-Up** 1. Once you’ve downloaded Pera / Defly you can choose to add a new account or recover with a passphrase. If you already have an Algorand account, hit “Recover With Passphrase” and enter in your 25-word private key to import your wallet. 2. If you wish to create a new account, press “Add New Account” 3. Next press “Create New Account” 4. WRITE DOWN your seed phrase on paper and store it safely, this is your private key. Although wallets allow you to create an account without backing up the seed phrase, we highly advise against it! ### **Step 2: Transfer ALGO from an Exchange to a Non-Custodial Wallet** On your exchange account: 1. press *Withdraw* 2. Copy your wallet address from Pera or Defly and paste the address in 3. Confirm withdrawal Now you're free to connect your Pera / Defly wallets to Algorand apps like NFDomains! See our [integrators list](/resources/integrations) to find cool Algorand projects! *** ### NFD Wallet Modal The NFD Wallet Modal allows users to connect any Algorand-supporting wallet to the application. {% hint style="info" %} You can connect multiple accounts at the same time from Defly or Pera Wallet! {% endhint %}

*** # Integrations If you have integrated NFDs in your app, please [DM](https://x.com/NFDomains) us to be added to our integrators list! If you want to integrate NFDs into your app, see the [API Docs](https://api-docs.nf.domains/). *** ### Wallets * **Defly** (Mobile Wallet w/ Vault Sends) * **Pera** **Wallet** (Mobile Wallet) - iOS / Android * **Pera Web Wallet** * **Coinbase Pay** (Coinbase Integration in NFD Wallet Modal) [https://www.coinbase.com](https://www.coinbase.com/pay-sdk) * Can send ALGO or any other supported crypto (BTC, ETH, etc.) referenced in NFDs. * **DaffiWallet** (Wallet) ### Explorers / Directories * **Allo** (Blockchain Explorer) * **Lora** (Blockchain Explorer) * **AlgoGazer** (Blockchain Explorer) * **Dappflow** (Blockchain Explorer) * **Blockpack** (Blockchain Explorer) * **Algo3d** (Block Visualizer) * **Pera Explorer** (Blockchain Explorer) * **ChainTrail** (dApp activity) * **BlockStalker** (Data Aggregation) * **AlgoDirectory** (On-chain Directory) ### DEFI * **Pact** (AMM) * **Tinyman** (AMM) * **Folks Finance** (Borrow/Lend Protocol) * **Alammex** (DEX Aggregator) * **CompX** (Stablecoin xUSD / CDP) ### NFT Ecosystem * **EXA Market** (NFT Marketplace) * **ALGOxNFT** (NFT Marketplace) * **Akita Inu ASA** (Community Token/NFTs) * **Shitty Kitties** (NFT Project) * **Rand Gallery** (NFT Marketplace) * **Shufl** (NFT Marketplace) [https://shufl.app](https://shufl.app/) * **Algogems** (NFT Marketplace) * **Atomixwap** (NFT Swap Tool) * **Fracctal Monsters** (NFT Marketplace & Game) * **AlgoPOAP** (Proof of Attendance Protocol on Algorand) * **Minthol.art** (NFT Explorer) ### Analysis/Tracking * **Asalytic** (NFT Sales & Wallet Explorer) * **StakeTaxCSV** (Tax Exporting Software) * **ASA STATS** (Portfolio Tracker) * **Algorand Stats** (Statistics on Governance) [https://www.algorandstats.com](https://www.algorandstats.com/) * **Asset1** (Portfolio Tracker) ### Activity notifications * **AlgoScout** (Telegram Bot) * **AlgoScout** (Twitter Bot) ### Discord bots * **AlgoVerify Bot** (Discord Bot made by @bykewel) * **Holders Bot** (Discord Bot made by @HI\_NFT) * **ALGOxNFT Listing / Offer / Sales Bot** * **Rand Gallery Offer / Sales Bot** * **NFT Discord Pal** * **Algo Toolchain** (Discord Bot by[ krby.algo](https://app.nf.domains/name/krby.algo)) ### Miscellaneous * **Codex** (NFT Viewer) * **Goanna x MakerX** (ARC19 NFTs) * **AlgoSeas** (NFT Game) * **Karot Hub by Flemish Giants** (NFT Raffles) * **Shrimpbank.algo** (NFT Raffles) * **RaffleBees** (NFT Raffles) * **Flipping Algos** (NFT Staking/Raffles) * **Octorand** (Blockchain Game) * **Fallen Order** (NFT Staking/Raffles) * **Artificial Undead** (NFT Game) * **Evil Tools** (Creator Tools) * **CUPSTAKES** (Blockchain Game) * **We Use Algorand** (Get Wallet Age) * **Thurstober Digital Studios** (NFT Game) * **Aegir Tactics** (NFT Game) * **GamePad3** (Gaming) * **AlgoBambino** (NFT Project) * **Coop.hair** (Community Token/DAO) * **Metapost** (On-Chain Discussion Board) * **Peperium Faucet** (Community Token) *** # FAQ ## What if I buy an NFD but don’t set a deposit address?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-if-i-buy-an-nfd-but-dont-set-a-deposit-address) The address that will resolve when sending to an NFD ([forward resolution](/#forward-resolution)) will be the *owner address* by default*,* **unless** a *verified* or *unverified address* are set. By linking a *verified* or *unverified address* you are selecting that address to receive funds instead of the *owner address.* This address becomes known as the NFD's *primary address*. By setting a *verified primary address*, integrators, such as block explorers, are able to trust the [reverse resolution](/#reverse-resolution), matching your wallet to your NFD. Without the address being verified, the reverse resolution cannot be trusted as anyone can paste an address in an NFD. Read more about setting address and metadata records [here](/platform/manage/setting-metadata-records#setting-metadata-records). *** ## Do NFDs have claw back?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#will-nfds-have-a-claw-back-feature) No. *** ## Are special characters allowed?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#are-special-characters-allowed) No. Only A-Z and 0-9. *** ## Are you launching a token?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#are-you-launching-a-token) No. *** ## What is NFDs policy on trademarked terms?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-will-nfds-policy-be-on-trademarked-terms) Please read our Terms of Service here: . *** ## What are the best ways to receive notifications?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-are-the-best-ways-to-receive-notifications) Follow us on [Twitter](https://twitter.com/NFDomains) and turn on notifications for the most up to date information. Join our [Discord](https://discord.gg/7XcuMTfeZP) for even more updates! To receive notifications when something is sent to your vault, see [here](/platform/manage/assets-and-vaults#notifications). *** ## How do I calculate the price of an NFD in x years? To calculate the price per year of a name in x number of years: `Future Price = Current Price × (1 + Inflation Rate)^ Number of Years` For example: How much will a 4 character name cost in 10 years? (2034)\ $12\*(1+.02)^10 = $14.63 Reference the price table per number of characters in [Mint](/platform/mint). The inflation rate is set at 2%. *** ## What are the benefits of upgrading my V2 NFD to a V3 NFD? The team behind NFDomains will continue adding new features to NFDs and those features will be exclusively for V3 NFDs. As of December 2024, the only feature V3 has that previous versions do not have is Bluesky verification. *** # Links API Docs: *** MainNet App: TestNet App: BetaNet App:: *** Twitter: Discord: YouTube: Medium: GitHub: TxnLab: *** # Welcome to NFDomains! NFDomains is the Algorand name service and marketplace for Non-Fungible Domains — unique, human-readable identities for your wallet. ### Guides: Jump right in Follow our handy guides to get started on the basics as quickly as possible: {% content-ref url="/pages/Sa8g6CcsmvFMSKziBQdz" %} [Connect a wallet](/nfd-docs/guides/connect-a-wallet) {% endcontent-ref %} {% content-ref url="/pages/GoF0ZAfHCDwEFlIWRYr7" %} [Mint an NFD](/nfd-docs/guides/mint-an-nfd) {% endcontent-ref %} {% content-ref url="/pages/cdgFveIRvX9VFYRU7Jjw" %} [Manage NFDs](/nfd-docs/guides/manage-nfds) {% endcontent-ref %} ### Fundamentals: Dive a little deeper Learn the fundamentals of NFDomains to get a deeper understanding of our main features: {% content-ref url="/pages/27Ylw6cLfpSUYjSB0W85" %} [Overview](/nfd-docs/overview) {% endcontent-ref %} {% content-ref url="/pages/zYoIPY9JO1QJ7eDwCqV7" %} [Pricing](/nfd-docs/fundamentals/pricing) {% endcontent-ref %} {% content-ref url="/pages/sNEoqRfWTpPIZF9CtMxH" %} [FAQ](/nfd-docs/fundamentals/faq) {% endcontent-ref %} ### Terms of Service {% embed url="" %} ### Privacy Policy {% embed url="" %} # Overview


	Video Walkthrough of NFDomains		https://youtu.be/dCvoaqknx5Y?si=3e5z-MiS2jlSMNXp	/files/tORlNv0XOv8Xu3GuMztX
	10 Reasons You Should Own an NFD		https://nfdomains.medium.com/10-reasons-you-should-own-an-nfd-28d2ba0457f	/files/QE7rcf0f8dQdHc4vdVrg

## What is an NFD? Non-fungible domains (NFDs) are unique, digital identities built on Algorand. Unlike traditional DNS domains, which are used to identify and locate resources on the internet, NFDs are used to identify and locate resources on the Algorand blockchain. Users can optionally link any metadata they want, with the ability to verify certain fields like Twitter, Discord, Telegram, etc. ### What is a digital identity? In the context of blockchain, digital identities or domains are used to alias an account address into something more readable like (**silvio.algo**). Self-chosen digital identities can be particularly powerful, as they allow individuals to define and control their own online identities, rather than being assigned one at birth. This can give users more control over how they are perceived and represented online, and can enable them to create a more personalized and unique online presence. # Technical Overview Under the hood, NFDs use smart contracts to associate your wallet address with a readable name, like "**silvio.algo**", allowing you to send and receive crypto using an identity that is easy to type and remember. NFDs are owned not leased. This makes it possible to permanently own your identity without fear of forgetting to register it. NFDs support forward and reverse lookups, meaning that a name ("silvio.algo") can be used to find its associated wallet addresses, and vice versa. This opens up a host of discoverability and transparency features for blockchain explorers, NFT marketplaces, DAOs, and other web3 services that integrate with NFDs. There are already over 60 platforms using NFDs in place of addresses. Check out our [integrators](/nfd-docs/fundamentals/integrations) page to find them all. Since every NFD is a distinct contract instance, up to 8KB of metadata (the maximum allowed by Algorand) can be stored in the contract's global state. This enables users to associate profile information, social media, and other data with their NFD. Each NFD mints its own ARC19 NFT, or "identity token", that represents your NFD's contract state, including all metadata you set. This feature is what enables NFDs to "live" in your wallet, giving you full visibility and ownership of your digital identity. Thanks to the mutable ARC19 standard, the NFT can update its own metadata so that it stays up-to-date. When you sell your NFD all metadata is wiped from both the NFD and NFT. The maximum length of an NFD is 27 characters. Emoji's, and 1- & 2-character names will be auctioned in reverse auctions, along with some other curated words. Allowed characters are A-Z, 0-9 & an Emoji library. No special characters are allowed. The amount of ALGO will fluctuate based on the ALGO/USD conversion at the time of purchase. There will be no renewal fees for an NFD. ### **Forward and Reverse Name Resolution** Thanks to the innovative smart contract architecture that underpins NFDs, both forward and reverse lookups are supported. In other words, "silvio.algo" can be used to find a wallet address, and a wallet address can be used to find "silvio.algo". That might not seem like a big deal, but it unlocks exciting features and usability improvements across a wide range of services. For example, using reverse lookups, blockchain explorers can display readable names of exchanges and other services in their tables of transactions, DAOs can provide more transparency by showing information about individual participants in governance votes, and NFT artists can display their name, profile and information about their project in any marketplace that integrates with NFDs. Those are just some of the possibilities. Using our public APIs and smart contracts, we expect developers to discover new and exciting ways to use this powerful combination of bidirectional lookups, unique identity, and user-driven metadata. # New to Algorand? How to buy ALGO and send it to a non-custodial wallet ### **Step 1: Buy ALGO** Start by choosing an exchange to buy some ALGO. Some options: [Coinbase](https://www.coinbase.com/), [Binance](https://www.binance.us/), [FTX](https://ftx.us), [KuCoin](https://www.kucoin.com/) {% hint style="info" %} Some exchanges have limits on withdrawing crypto. Make sure you’re aware of all the rules and restrictions of the exchange you pick. {% endhint %} ### **Step 2: Set up a Non-Custodial Algorand Wallet** We recommend using the [Pera Wallet]() or [Defly](https://defly.app/).\ You can use both at the same time with the same address. {% hint style="info" %} A non-custodial wallet means YOU control your private keys and no-one else. You’re solely responsible for the safe keeping of your private keys. If you lose your private key there is no recovery process. {% endhint %} **Pera Wallet** 1. Once you’ve downloaded Pera you can choose to add a new account or recover with a passphrase. If you’ve already created a wallet with MyAlgo, hit “Recover With Passphrase” and enter in your 25-word private key to import your wallet. 2. If you wish to create a new account, press “Add New Account” 3. Next press “Create New Account” 4. WRITE DOWN your seed phrase on paper and store it safely, this is your private key. ### **Step 3: Transfer ALGO from an Exchange to a Non-Custodial Wallet** On your exchange account, press “Withdraw”. Copy your wallet address from the Pera Wallet or defly, highlighted in yellow, and paste the address in. This will transfer your ALGO from the centralized exchanges wallet to your wallet. Now you're free to connect your Pera / Defly wallets to Algorand dApps like NFDomains! ![Pera Wallet ](https://lh5.googleusercontent.com/mV8pPw5X74JigX8MHMee2ENWVYueYaQpFcCeSlRk9kpQy6hleVzA4K83pihgJojlWnIqgcARER4E2eKOCY2Ui1KZgQJ2N13tea8zKOY9V45AC4VuWtQFnQmmcq5k4MOSpqAr6VXTp_GIW6SqOA) \ # Connect a wallet Connect your wallet at the top right of the page using Pera, Defly or any other Algorand wallet via wallet connect. You're able to use a Ledger device to mint & manage NFDs. **You're able to connect multiple wallets (accounts) at the same time while using Pera or Defly.** This will allow you to verify multiple addresses in one NFD, and allow you to quickly manage all of your wallets without needing to disconnect and reconnect. {% embed url="" %} Wallet Menu Demo {% endembed %} ### Don't have a wallet? Create an Algorand wallet using the links below: {% embed url="" %} {% embed url="" %} {% hint style="danger" %} Make sure you write down your seed phrase and store it safely. Do not take a screenshot of your seed phrase or store it in the cloud. Your seed phrase is the only recovery mechanism for your wallet. {% endhint %} # Wallet Menu ### Features * Ability to connect with any Algorand wallet, and quickly switch between accounts. (**When connecting your wallet to NFDs, connect multiple accounts at once by selecting the accounts you'd like to connect in either Pera or Defly, whichever you're connecting with. This enables the ability to seamlessly switch between accounts, as well as verify multiple addresses in the same NFD.)**

* Easily navigate to your primary NFD by clicking on the PFP. * Quickly change your primary NFD with the 'Set Primary NFD' dropdown. * Send assets from any of your accounts to any account with the send feature.

Find more about managing Assets and Vaults here [Assets & Vaults](/nfd-docs/guides/manage-nfds/assets-and-vaults) # Mint an NFD Minting is purchasing a 'new' NFD, one that has not previously been created. ### How to Mint an NFD On the 'Mint' tab, search for anything you'd like. The NFD must be an alphanumeric containing letters A-Z and/or numbers 0-9, no special characters. You are able to mint using a Ledger device. Make sure you're updated to the latest firmware as well as the latest Algorand Ledger app. You may also need to update your Ledger Live app. Information about pricing can be found [here](/nfd-docs/fundamentals/pricing). {% embed url="" %} Minting Demo {% endembed %} You will need to sign two separate transaction groups to Mint & Claim your NFD. 1. Mint and purchase 2. Claim If you mint a name but don't claim it, the name will be sitting in your accounts '**Reserved**' tab found on the Manage page.

# Search The search bar at the top of the screen can be accessed with hotkey **`/`** This view has the 'send' feature which when selected will pop the send modal. Find more on the send modal in [Wallet Menu](/nfd-docs/guides/connect-a-wallet/wallet-menu) Any verified Social Media accounts the user has will be displayed in the Social links field as an additional verification check before sending assets. This should help users know they're sending to the correct NFD.

Search for an NFD that hasn't been minted

# Marketplace Secondary market for NFDs ### Overview The NFD Marketplace is the place to buy & sell NFDs which have already been minted. ### Buy on the Marketplace {% embed url="" %} Buying on the Marketplace {% endembed %} If you find an NFD you're interested in purchasing you can either 'Buy now' or 'Make an offer'. You'll see the user selling the NFD and if they have social media information filled in you could message them to negotiate. When you make an offer, it's simply a note to the owner saying 'I am willing to pay X'. \ If the owner is willing to accept your offer, they can change the sale price and reserve the NFD for your address.\ \ If you make an offer and it's accepted, or if someone reserves an NFD for you (same thing), you will find the NFD reserved in your 'Manage' tab where you will need to claim it. ### Sell on the Marketplace Once you own an NFD you're able to resell it through the NFD Marketplace by selecting 'List for sale' on any NFD you own. {% embed url="" %} Selling on the Marketplace {% endembed %} {% hint style="info" %} Be aware that putting an NFD up for sale will **remove all metadata** you've attached, including verified fields. {% endhint %} You're able to reserve the NFD for sale for a particular address by setting a sale price as well as the wallet address. You're also able to transfer an NFD and optionally cover the fee to claim. There is always a 1 ALGO minimum when transferring names. NFDomains takes a **5% commission** on all secondary sales. # NFD Profile Everything about an NFD Profile On every NFD profile you're able to see lots of data. On the header you're able to see name, bio, verified social medias, and [influencer](/nfd-docs/guides/analytics/influencer-leaderboard) & [donation](/nfd-docs/guides/analytics/donations-leaderboard) badges. In preferences (edit -> preferences) users are able to toggle the influencer badge on or off. Information is broken up into different tabs on the profile - Details, Assets, Segments & More.

### Details All metadata that is added to an NFD is visible in the 'Details' tab. This includes name, bio, verified & unverified addresses, social media links, email, websites and more. To learn more visit[Manage NFDs](/nfd-docs/guides/manage-nfds) Verified social media accounts show up at the top of the profile view under 'Verified'. ### Assets The NFD Assets tab aggregates all of the users NFTs and tokens between all linked accounts under one view. This is a powerful tool for creators as they can self identify their collections. Marketplaces can rely on creators self labeling their collections via NFDs. You can toggle between Owned, For Sale & Creations. The For Sale tab only displays NFTs listed for sale on Rand Gallery, ALGOxNFT and Exa.market. Find more on the Assets tab in [Assets & Vaults](/nfd-docs/guides/manage-nfds/assets-and-vaults)

### Segments Segments are distinct, sovereign NFDs that can be minted off root NFDs, adding an additional level that is separated by a “.” Commonly known as 'sub-domains'. Read all about Segments in [Segments](/nfd-docs/guides/manage-nfds/segments). ### Details (Sales, Offers & History) Sales shows a chronological list of sales & transfers of the NFD.

Offers shows a chronological list of all offers received for the NFD.

History shows a detailed chronological list of every update made to an NFD. This shows sales history and changes to the metadata.

# Manage NFDs {% embed url="" %} Managing NFDs {% endembed %} # Setting Addresses {% hint style="info" %} The owner address and the linked addresses are **independent**. This is crucial to understanding how NFD name resolution works. {% endhint %} {% embed url="" %} Setting Unverified and Verified Addresses {% endembed %} To link addresses, navigate to the profile page of your NFD and select Edit.

### Verified Addresses By default, the wallet address that will resolve when sending to an NFD will be the owner address **unless** a verified address or unverified address are set. By setting a verified address or an unverified address you are selecting that wallet to receive funds instead of the owners. By setting a verified deposit address, integrators are able to rely on this for matching your wallet to an NFD (reverse lookup). Without verifying the address (signing with the keys), the account cannot be fully trusted as anyone could just paste that address in and that could potentially be abused. If you wish to connect multiple verified addresses to one NFD you need to use a wallet that lets you select multiple accounts at the same time such as Pera or Defly. To verify multiple addresses we require users to sign for both account A and account B in the same transaction group. ### Unverified Addresses To set an unverified address, paste in the wallet address in the 'Addresses' 'Unverified' tab while editing the NFD. Unverified addresses are not treated with the same trust level as verified addresses. However, it's important unverified addresses exist so accounts like a custodial wallet or smart contract can be set as an NFD and work for deposits only. ### Primary NFD Linking the same account to multiple NFDs may cause confusion as to which NFD you want displayed when doing a reverse lookup. To choose which NFD gets displayed for your address, you can select a Primary NFD for your account in the drop-down menu.

One account could own thousands of NFDs, but that doesn't mean you want to or need to set the deposit address for them. You only want to set the deposit address to your NFD if you intend to use it for transactions, and you want it to show up when someone looks up your wallet address. # Setting Metadata Find the "Edit" option on an NFDs profile page (must be connected to the dApp to see the option). {% embed url="" %} To set an avatar & banner, click the Avatar circle or the Banner square and upload an image or select an NFT from your gallery. Your NFT gallery displays all of your NFTs, aggregated across all associated accounts (NFD vault, Owner, & any linked verified accounts). Fill in any metadata you would like to add and then scroll to the bottom and select 'Update metadata' to save these records in your NFD. Certain metadata fields can be verified, find more on this in [Verifying Metadata](/nfd-docs/guides/manage-nfds/verifying-metadata) {% hint style="info" %} Please remember all information is fully public. Do not enter sensitive personal info. {% endhint %} # Verifying Metadata Once records are set in the appropriate metadata fields in the 'Metadata' tab, you're able to verify this data in the 'Verification' tab. Twitter, Web Domain, Email, Avatar & Banner can be verified through this page. Telegram and Discord both require users to interact with NFDs bots to verify. {% embed url="" %} Verifying Metadata {% endembed %} # Twitter Verification To verify Twitter, enter your handle into the Twitter field of your NFD (see [Setting Metadata](/nfd-docs/guides/manage-nfds/setting-metadata)) & update it. Once the field is updated, you will see a 'verify' option show up in the Verification tab, as well as in the Metadata tab below the Twitter field. Tweet out the verification challenge and if successful your Twitter handle will move into a different, Twitter Verified field and show up at the top of your profile. To be ranked on the Influencer Leaderboard, see [Analytics](/nfd-docs/guides/analytics/influencer-leaderboard). {% embed url="" %} Twitter Verification Tutorial {% endembed %} # Discord Verification To verify Discord you must interact with our Discord bot in the **#verify-nfd** channel and follow the instructions. [Discord Verification Channel](https://discord.gg/TazX7rFRu3) {% embed url="" %} # Telegram Verification To verify Telegram you must interact with our Telegram bot which can be found in edit -> verifications -> follow instructions. {% embed url="" %} Verifying Telegram Tutorial {% endembed %} [Telegram Verify Bot](https://t.me/nfd_verify_bot) # Github Verification ## Personal Verification To verify Github, enter your handle into the Github field of your NFD (see [Setting Metadata](/nfd-docs/guides/manage-nfds/setting-metadata)) & update it. Once the field is updated, you will see a 'verify' option show up in the Verification tab, as well as in the Metadata tab below the Github field.

Verifying from Edit -> Verification page

When you click verify, you'll see a dialog to 'start verification'. Click that. You'll next see a modal like this:

Follow the directions, creating a **PUBLIC** gist for your user with the contents as specified. Once completed, come back to the NFD page and click Confirm. If your handle is an organization, do NOT create a gist but follow the changes below. ## Organization Verification Follow the directions above but instead of creating a gist, set the nfd-verify:xxx challenge value into a root file called "**.nfd**" in the **.github** Organization Repo for your organization. If you don't already have a .github repo, one easy way of doing it is to click the 'create readme' link on the right of your organizations github profile page. You can also click the '+' dropdown menu and click New Repository - naming it .github.

If you choose the 'New Repository' route. Here is an example - **notice it must be public** !

If you create the empty .github repo like above, then click the 'creating a new file' link.

followed by naming the file '.nfd' and pasting in the challenge:

Commit the changes and then switch back to the NFD page and click Confirm. Your Organization's Github Handle will now be verified. # Transfer an NFD To transfer an NFD navigate to the NFD profile page and hit '**Transfer**'

NFD profile page when connected as the owner

Once on the transfer page enter the address or NFD of the recipient and then select '**Transfer**'.\ You can optionally gift the NFD by selecting '**Give NFD as a gift**'. This will transfer the recipient 1.108 ALGO to cover the cost of claiming the NFD. The recipient will see the NFD waiting for them in the '**Reserved**' tab on their '**Manage**' page.

# Upgrade Smart Contract ### Overview of Upgradable Smart Contracts \ NFDs are upgradable and NFDomains plans to take full-advantage of this as Algorand releases new features. NFDomains will push updates along with update notes on what has been changed and why. NFDomains only plans to use a force upgrade if there's a TOS violation or a security vulnerability. Otherwise, users will need to update their contracts manually as new features are released. ### Upgrade Smart Contract To upgrade your smart contract, navigate to an owned NFD -> Edit -> Smart Contract -> Upgrade Contract.

### Lock / Unlock Smart Contract To allow for maximum user control, users can toggle between locking and unlocking their NFD to upgrades. If you lock your contract, NFDomains will be unable to upgrade your contract. By default your NFD will come unlocked. To lock your contract, toggle 'Contract is unlocked' to locked. # Algo.xyz Users are able to use the algo.xyz domain to display their NFD profile, NFT gallery, NFT creations, or whatever webpage they'd like to redirect to. To resolve an NFD via DNS, users simply need to append **.xyz** at the end of the name. (silvio.algo -> silvio.algo.xyz) The default option will redirect to your profile page. Users have the option to easily change that to their NFT gallery instead. If you want to redirect to an entirely different page, paste the URL in the "Redirect to" field. To confirm your changes make sure to hit "Update URL" in the bottom right corner.\ \ For segments you have to use the following format for redirects: algo.xyz/segment.root

# Segments Definition: Distinct, sovereign NFDs that can be minted off root NFDs, adding an additional level that is separated by a “.” {% embed url="" %} Minting a Segment {% endembed %} {% hint style="info" %} Minimum contract version 1.16, see [Lock or Unlock Contract](/nfd-docs/guides/manage-nfds/upgrade-smart-contract) {% endhint %} ### The Basics [Roots ](https://docs.nf.domains/nfd-docs/guides/manage-nfds/pages/sNEoqRfWTpPIZF9CtMxH#what-is-a-root-vs.-a-segment)can mint an unlimited number of segments, but segments cannot mint other segments. Root NFDs have two segmenting states, locked & unlocked. This defines who is allowed to mint segments. Example : nfd.algo (Root) -> can then create pooof.nfd.algo (segment off nfd.algo) ### Locked vs. Unlocked When you have a root NFD segmenting will be locked by default. This means that only you as the owner of the root can mint segments off the NFD. If you want to open your NFD so that anyone can mint a segment navigate to the 'Edit' Segments tab. There you are able to unlock your NFD and set a sale price.

Click on 'unlocked' to navigate to the Segments settings page

On the Segments settings page you can lock / unlock your NFD

You can also keep it locked, mint some segments for yourself, and then unlock it for others to mint. The root owner has control over whether the NFD is locked or unlocked to segmenting, but if unlocked and segments get minted, the owner of the root will have NO control over those segments. If the NFD is locked and the owner mints the segments themselves, they will have full control over the segments and can transfer them or sell them if they wish. Resale of minted segments will have the same 5% commission enforced. ### Costs There are two costs associated with minting a segment, the Platform Fee & the [Carry Cost](/nfd-docs/fundamentals/faq#what-is-carry-cost). If you're minting a segment off a root you don't own, you will likely also pay a premium set by the root owner. The **platform fee** will be **$4**, or **25%** of the sales price, whichever is greater. The platform fee scales down as more segments get minted. See Fee Tiers below. The [**carry cost**](/nfd-docs/fundamentals/faq#what-is-carry-cost) for an NFD is always 5 ALGO and paid by whoever mints the NFD. For open segments, the owner of the root gets to set the price for segmenting and keeps a portion of the proceeds from segment sales. To understand how the $4 or 25% Platform Fee breaks down, see an example below. Example: | Segment Sale Price (USD) | Platform Fee (USD) | Owner Proceeds (USD) | | ------------------------ | ------------------ | -------------------- | | 15 | 4 | 11 | | 16 | 4 | 12 | | 17 | 4.25 | 12.75 | | 18 | 4.50 | 13.50 | ### Fee Tiers (only for self minted segments) The more segments that get minted from a root, the cheaper the platform fee per segment becomes. This is to account for large projects & organizations that plan to utilize segments. This only works when the segments are minted by the owner of the root. | Number Minted | Discount Rate | Price (USD) | | ------------- | ------------- | ----------- | | | | 4 | | 10 | 20% | 3.20 | | 100 | 30% | 2.80 | | 1,000 | 40% | 2.40 | | 10,000 | 50% | 2.00 | | 100,000 | 60% | 1.60 | | 1,000,000 | 70% | 1.20 | # Assets & Vaults {% embed url="" %} ### Assets The Assets Owned tab aggregates NFTs and Tokens across all your accounts (owner account, linked accounts, and vault). If your NFTs are in your Vault you’ll see a ‘Vaulted’ icon on the asset in your Assets Owned tab. You're able to filter based on a specific account, or a specific type of Asset (NFTs, NFDs and Tokens).

Owned View - Shows Assets Aggregated Across all Accounts

### What is a Vault? Vaults are distinct Algorand accounts associated with an NFD. These accounts have the ability to auto opt-in to assets that are sent to it. ### What’s an Opt-In? Before an Algorand account can receive a specific asset it must opt-in to receive it. While this is a nice feature to prevent unwanted assets from entering your wallet, it adds friction when trying to transact new assets. This is a major issue for airdrops and giveaways, but also for regular users sending each other NFTs which all have unique ASA IDs. ### NFD Vault Features Newly minted NFDs will have Vault functionality. **Existing NFDs will need to be upgraded** **to the latest contract version** to enable Vaults. See [Upgrade Smart Contract](/nfd-docs/guides/manage-nfds/upgrade-smart-contract) to find learn how to upgrade your NFDs contract. **Auto opt-in / opt-out** Vaults will auto opt-in to any asset they are sent, and they will also auto opt-out when you send an asset resulting in a zero balance which helps manage the minimum balance requirement (MBR) of the account. The sender pays the .1 ALGO MBR and does not get it back, preventing the spamming of unwanted assets by adding a cost. **Vaults default to being unlocked.** The Vault can be unlocked or locked at will, offering a high degree of control to the user. Don’t want random tokens showing up? Keep your Vault locked! Find the toggle in your Assets -> Vault page, or in Edit -> Vault. **Asset Management** NFD Vaults offer seamless asset management, allowing users to transfer assets between their accounts and Vault, or to any other NFD account or its Vault. You can also access the Send feature through the [Wallet Menu](/nfd-docs/guides/connect-a-wallet/wallet-menu) and through [Search](/nfd-docs/guides/search).

### Lock & Unlock Vault Newly minted or upgraded NFDs come with unlocked Vaults. If you wish to lock your NFD, there is a toggle on the Assets -> Vault page to lock or unlock. Alternatively, you can go into an owned NFD and go to Edit -> Vault -> toggle locked or unlocked -> Update Vault.

### Send to a Vault / From a Vault Currently to utilize Vaults you will need to do so within the NFDs app. The wallets have not integrated Vaults yet so sending from a wallet to a Vault will not currently work! 1\) Generic 'Send' can be found in the Wallet Modal at the top right of your screen, or through the search bar when looking for a name. You can send to any NFD or any NFDs Vault as long as they have an upgraded contract and an unlocked Vault.

2\) From the Assets Owned or Vault page of an NFD, click the three little dots for options. You can Move to Vault, Move to Deposit Account, and Send from this menu.

Expand the Three Dots for Additional Options

Vault Contains Assets Warning When Selling an NFD

### Notifications To get notifications of assets sent to your Vault, add the Vault address as a 'Watch Account' in Pera or Defly and ensure notifications are turned on. Find the Vault address in your NFDs Details.

To add a watch account in Pera, hit the `+` icon -> I want to create an account -> Add watch account -> Paste in the Vault address To add a watch account in Defly, hit the `+` icon -> Contact -> Paste in the Vault Address # Analytics ### Overview NFDomains has two types of sales that it tracks on the Analytics Overview. Primary sales are newly minted NFDs and curated auctions. Secondary sales are p2p trading of already minted NFDs.

### Sales History Sales History shows a ledger of all primary sales, secondary sales & transfers. It shows the amount in ALGO, the buyer, the seller, and a link to the transaction. You can use the toggles to filter by sale type.

### # Sales Leaderboard The Sales Leaderboard displays the 20 highest sales of all time in ALGO.

# Influencer Leaderboard If you would like to be ranked on the Influencer Leaderboard, once your [Twitter is verified](/nfd-docs/guides/manage-nfds/verifying-metadata/twitter-verification), set your display name on to match your NFD. The twitter name must match your NFD exactly (aside from capitalization). For example, if your NFD is **trilemma.algo**, then your Twitter name needs to be set to trilemma.algo as well (Different case is fine - ie: Trilemma, TRIlemma, etc). This is your twitter name, not your twitter handle. The handle never needs to change. The Leaderboard will update roughly once an hour!

Top 10 Influencers by Twitter Follower Count

# Donations Leaderboard We think tracking donations via NFDs is a great example of what NFDs can do! For charities we track, we will track all payments sent to the specified charity account **from NFD holders** and the accounts they have linked in their NFDs. There are currently 7 charities recognized by NFDs. You can see all 6 by clicking on the dropdown menu on the right-hand side of the screen.

When you make a donation to a charity that NFDs tracks a donation badge will be added to your NFDs profile.

Goanna Profile View Showing Donation Badges

# Charities Policy If you represent and/or know of a charity (501(c)(3) or equivalent) that has an Algorand wallet set-up to accept donations, please send the following information to 1. Charity name & webpage 2. Algorand wallet address (or NFD) that is owned by the charity 3. Link to webpage that displays proof of their Algorand wallet address 4. Best contact information for you / them If you're a charity and have done all the above steps, please setup your NFD and we'll be in touch soon. Set the '**name**' property to your charity name. This will be used in the badge of the tooltip on users' NFDs and on the donations leaderboard page. Set the deposit account in the NFD the same as the account provided to NFDomains. They should match. Add a custom '**ein**' field (if US 501c(3) charity) or equivalent for your country \[ie: regnumber] and enter the EIN. See for an example. Set the avatar and banner images to recognizable images for your charity. This data will will be used Donations Leaderboard page as well as badging on users NFDs when they have donated to this address. We will do our best to get back to you as soon as possible. Thank you! # Integrations Current Count: 64 ### Ecosystem Highlights


https://perawallet.app/				/files/9zHw2PXoxKxfPHfvnXrU
https://defly.app/				/files/Emf4EyzTy2yxpgUW8yKV
https://www.daffione.com/				/files/OS3FURbzmwA2jOmhup2K
https://allo.info/				/files/HoVkrbh46BtEM1mqLeHX
https://explorer.perawallet.app/				/files/PSaPa4VcmksgMpUuGFLb
https://algo3d.live/				/files/7wENEhWhZizpaws9QZG6
https://app.folks.finance/				/files/xUpUge9ajkdZkh536R2w
https://tinyman.org/				/files/Eki3vPaEbYIRrohPb7aw
https://www.nftexplorer.app/				/files/A1nvtZY2E3nqXOoeOMZx
https://www.randgallery.com/algo-collection/				/files/YEzcHBR5eVESdQH0AA6A
https://algoxnft.com/				/files/x0hr4NUO24SQKzpsn7cW
https://www.minthol.art/				/files/VA8rse4awXpieqX6a5Jk

This list is constantly evolving so this list should not be considered to include ALL integrations. If you know of an integration missing from this list, please reach out in our discord. ### Wallets * **Pera** **Wallet** (Mobile Wallet) - iOS / Android * **Pera Web Wallet** * **Defly** (Charts, Swaps, Stats and Wallet App) * **AlgoSigner** (Chrome Wallet Extension) * *Still works but has been removed by Purestake and is no longer downloadable.* * **Coinbase Pay** (Coinbase Integration in NFD Wallet Modal) [https://www.coinbase.com](https://www.coinbase.com/pay-sdk) * Can send ALGO or any other supported crypto (BTC, ETH, etc.) referenced in NFDs. * **DaffiWallet** (Wallet) ### Explorers * **Allo** (Blockchain Explorer) * **Algo3d** (Block Visualizer) * **Pera Explorer** (Blockchain Explorer) * **ChainTrail** (dApp activity) ### NFT Ecosystem * **ALGOxNFT** (NFT Marketplace) * **NFTExplorer** (NFT Explorer) * **Rand Gallery** (NFT Marketplace) * **Shufl** (NFT Marketplace) [https://shufl.app]()[ ]() * **Algogems** (NFT Marketplace) * **Atomixwap** (NFT Swap Tool) * **EXA** (NFT Marketplace) * **Fracctal Monsters** (NFT Marketplace & Game) * **AlgoPOAP** (Proof of Attendance Protocol on Algorand) * **Minthol.art** (NFT Explorer) ### DEFI * **Pact** (AMM) * **Tinyman** (AMM) * **Folks Finance** (Borrow/Lend Protocol) * **Alammex** (DEX Aggregator) * **Xbacked** (Stablecoin xUSD) ### Analysis/Tracking * **Asalytic** (NFT Sales & Wallet Explorer) * **COMPX** (Portfolio Tracker) * **StakeTaxCSV** (Tax Exporting Software) * **ASA STATS** (Portfolio Tracker) * **Algorand Stats** (Statistics on Governance) * **Asset1** (Portfolio Tracker) ### Activity notifications * **NFTX Sales Bot** (Twitter Bot) * **Rand Gallery Mech** (Twitter Bot) * **CGF Sales Bot** (Twitter Bot) * **AlgoScout** (Telegram Bot) ### Discord bots * **AlgoVerify Bot** (Discord Bot made by @bykewel) * **Holders Bot** (Discord Bot made by @HI\_NFT) * **ALGOxNFT Listing / Offer / Sales Bot** * **Rand Gallery Offer / Sales Bot** * **NFT Discord Pal** * **SpaceVerify** (Discord Bot by Tiger Chi) [discord.gg/spacechi](https://t.co/a06pDQG0Bd) * **Algo Toolchain** (Discord Bot by[ krby.algo](https://app.nf.domains/name/krby.algo)) ### Miscellaneous * **Octorand** (Blockchain Game) * **Codex** (NFT Viewer) * **Goanna x MakerX** (ARC19 NFTs) * **AlgoSeas** (NFT Game) * **Karot Hub by Flemish Giants** (NFT Raffles) * **Shrimpbank.algo** (NFT Raffles) * **RaffleBees** (NFT Raffles) * **Flipping Algos** (NFT Staking/Raffles) * **Fallen Order** (NFT Staking/Raffles) * **Artificial Undead** (NFT Game) * **Evil Tools** (Creator Tools) * **CUPSTAKES** (Blockchain Game) * **We Use Algorand** (Get Wallet Age) * **Akita Inu ASA** (Community Token/NFTs) * **Shitty Kitties** (NFT Project) * **Thurstober Digital Studios** (NFT Game) [https://discord.gg/eBZzRJMeXc]() * **Aegir Tactics** (NFT Game) * **GamePad3** (Gaming) * **AlgoBambino** (NFT Project) * **Coop.hair** (Community Token/DAO) * **Metapost** (On-Chain Discussion Board) * **Peperium Faucet** (Community Token) [
]() # Pricing Current fee model for NFDs NFDomains has announced plans to move from a one-time purchase model to a yearly renewal model to deter domain squatters and build a more long term sustainable economic model for the protocol. **All existing NFDs will be grandfathered into Legacy status**. Please read the blog post [here](https://nfdomains.medium.com/2024-and-beyond-dbfff7d28910) for more details. ### Roots NFDs are a one-time purchase at a fixed USD value. The amount of ALGO will fluctuate based on the ALGO/USD conversion at the time of purchase. #### Common (Buy it now) - These names make up the majority of character variations[](https://docs.nf.domains/docs/NFD%20Overview/Pricing#common-buy-it-now---these-names-make-up-the-majority-of-character-variations) | # of Characters | Price (USD) | | --------------- | ----------- | | 3 | 375 | | 4 | 200 | | 5 | 125 | | 6 | 75 | | 7 | 50 | | 8 | 37.50 | | 9 | 25 | | 10+ | 20 | #### Premium (Buy it now) - Around 100k words & names that are commonly used[](https://docs.nf.domains/docs/NFD%20Overview/Pricing#premium-buy-it-now----100k-words--names-that-are-commonly-used) | # of Characters | Price (USD) | | --------------- | ----------- | | 4 | 300 | | 5 | 187.50 | | 6 | 112.50 | | 7 | 100 | | 8 | 75 | | 9 | 50 | | 10+ | 40 | #### Curated - Highly significant words or phrases[](https://docs.nf.domains/docs/NFD%20Overview/Pricing#curated-dutch-auction---highly-significant-words-or-phrases-specifically-those-related-to-crypto) - Auctioned in Dutch Auction format, those not sold are now resting at the floor price.

# of Characters	Price Floor (ALGO)	Price Ceiling (USD)
Any	2,750	20,000

### Segments (subdomains) ### Costs There are three costs associated with minting a segment, the Platform Fee, the [Carry Cost](/nfd-docs/fundamentals/faq#what-is-carry-cost), and the premium set by the root owner (the portion of the sale they receive). If you're minting a segment off a root you own, you will only pay the Platform Fee and Carry Cost. The **platform fee** will be **$4**, or **25%** of the sales price, whichever is greater. If minting from a root you own, the platform fee scales down as more segments get minted. See Fee Tiers below. The [**carry cost**](/nfd-docs/fundamentals/faq#what-is-carry-cost) for an NFD is always 2.5 ALGO and paid by whoever mints the NFD. For open segments, the owner of the root gets to set the price for segmenting and keeps a portion of the proceeds from segment sales. To understand how the $4 or 25% Platform Fee breaks down, see an example below. Example: | Segment Sale Price (USD) | Platform Fee (USD) | Owner Proceeds (USD) | | ------------------------ | ------------------ | -------------------- | | 15 | 4 | 11 | | 16 | 4 | 12 | | 17 | 4.25 | 12.75 | | 18 | 4.50 | 13.50 |
# FAQ ### When I buy an NFD, do I own it forever?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#when-i-buy-an-nfd-do-i-own-it-forever) Yes. This is not a subscription service. Any NFD you buy belongs to you forever unless you decide to resell it on the secondary market. ### What about other naming services?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-about-other-naming-services) We sat for an interview with [@Algorandintern](https://twitter.com/Algorandintern), a community member who was concerned about the existence of two Algorand naming services using the same suffix. Find his article here: {% embed url="" %} ### Are you launching a token?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#are-you-launching-a-token) Nope. Teams focused on launching tokens are not 100% focused on the project. ### Will NFDomains ever offer a different suffix or only the ‘.algo’?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#will-nfdomains-ever-offer-a-different-suffix-or-only-the-algo) We are Algorand maximalists, and we don’t plan to offer any other suffix for the foreseeable future. We are dedicated to building a best-in-class naming service for Algorand. ### Are NFDs also NFTs?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#are-nfds-also-nfts) Yes. NFDs are smart contracts that mint their own ARC-19 NFT that acts as a dynamic representation of the NFD in your wallet. Update the avatar in an NFD and the NFT's image and properties will automatically update to reflect the change in the metadata. TxnLab has developed the ARC-19 standard for this purpose. The NFT moves with the ownership of the NFD. The NFT is assigned to the owner's wallet and frozen until the NFD is sold. You must use the NFD Marketplace to transfer ownership of NFDs. ### What are the best ways to receive notifications?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-are-the-best-ways-to-receive-notifications) Follow us on [Twitter](https://twitter.com/NFDomains) and turn on notifications for the most up to date information. Join our [Discord](https://discord.gg/7XcuMTfeZP) for even more updates! ### What NFDs policy on trademarked terms?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-will-nfds-policy-be-on-trademarked-terms) Please find our Terms of Service here: ### Do NFDs have a claw back feature?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#will-nfds-have-a-claw-back-feature) No. We don’t believe we should control your property once you’ve bought it. Individuals are responsible for not losing their keys just like with any other on-chain asset. The NFTs have clawback enabled to claw it back from owner to owner when the NFD is resold. This does not give TxnLab the ability to claw it back. ### What is the maximum length of an NFD?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-is-the-maximum-length-of-an-nfd) 27 characters – The max length of an ASA name is 32 characters which would leave five characters for ‘.algo’. ### What is a Root vs. a Segment Root NFDs (e.g., micali.algo) are distinct, sovereign NFDs that can mint an unlimited number of segments. A root will have the following format - \[xxx..].\[algo] Segment NFDs (e.g., silvio.micali.algo) are distinct, sovereign NFDs that can be minted off root NFDs, adding an additional level that is separated by a “.” Segments cannot mint other segments. A segment will have the following format - \[xxx..].\[xxx..].\[algo] ### Are there costs associated with using an NFD once I own it?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#are-there-costs-associated-with-using-an-nfd-once-i-own-it) Each NFD is a distinct contract instance and accounts. Accounts to hold state require a minimum ALGO balance. On top of the minimum ALGO balance, each transaction costs .001 ALGO. NFDs require 5 ALGO from each purchase to mint & fund the NFD which is included in the price, not on top of the price. This is known as [carry cost](#what-is-carry-cost). ### Are special characters allowed?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#are-special-characters-allowed) No. Only A-Z, 0-9, and an Emoji library (supported in the future). ### What are Curated auctions?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-are-curated-auctions) Curated names, like emojis and other names with great significance or rarity, will be released during scheduled Dutch auctions. Common and premium names can be bought for a flat price at any time. See [Pricing](/nfd-docs/fundamentals/pricing) ### Is there a commission on secondary sales?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#is-there-a-commission-on-secondary-sales) Yes, a 5% fee will be paid to TxnLab. This allows us to maintain the marketplace. ### Can you make an offer on an NFD?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#can-you-make-an-offer-on-an-nfd) Yes, you're able to make an offer on unlisted or listed NFDs. ### How do I set my address to resolve my NFD?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#how-do-i-set-my-address-to-resolve-my-nfd) See [Broken mention](broken://pages/anQ6RYOam8tgtvdo2oKS) ### What if I buy an NFD but don’t set a deposit address?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-if-i-buy-an-nfd-but-dont-set-a-deposit-address) The deposit address when set takes precedence over the owner address. If no verified or unverified addresses are set, then integrators will just resolve the owner address. Find more info in [Metadata and Addresses](broken://pages/anQ6RYOam8tgtvdo2oKS). ### What are verified fields and how are they different from user defined fields?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-are-verified-fields-and-how-are-they-different-from-user-defined-fields) NFDomains offers off-chain verification services for certain fields such as Twitter and Discord. These offer a greater level of authentication that the NFD represents who it says it represents. ### What makes an NFD real? Can someone fake it?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#what-makes-an-nfd-real-can-someone-fake-it) What defines a 'true' NFD is a global registry contract instance and local state against that. All NFDs ever created are permanent and linked w/ that registry contract instance. If someone created a fake, it wouldn't match the registry contract and wouldn't function like an NFD. ### Is it possible to delete an NFD?[ ](https://docs.nf.domains/docs/NFD%20Overview/FAQ#is-it-possible-to-delete-an-nfd) Nope. You can wipe the metadata associated with an NFD, but the name itself cannot be destroyed. ### Can I transfer an NFD to myself?[](https://docs.nf.domains/docs/NFD%20Overview/FAQ#can-i-transfer-an-nfd-to-myself) Yes, you can reserve the NFD for another wallet and then have the other wallet claim it. There is a minimum of 1 ALGO enforced on any transfer. You can also gift NFDs this way only knowing the recipients wallet address. There is a built in 'transfer' feature where you can optionally send the 1 ALGO to the recipient so the NFD is truly free. ### Can I mint an NFD using a Ledger? Yes! NFDs are fully supported in the Algorand Ledger app. ### What is Carry Cost? The carry cost of an NFD is \~5 ALGO due to the minimum balance requirement on Algorand. NFDs purchase the maximum amount of contract storage at create time. Box storage may enable us to drastically reduce the carry cost of NFDs in the future. ### Do you have an NFD you'd like to reserve for an individual or organization? Introducing [http://nfdwizard.algo.xyz](https://t.co/IBN53DNGTa) To redeem a name please message us on twitter ([twitter.com/NFDomains](https://twitter.com/NFDomains)) or email (). The Wizard will accept any NFD transferred to it for 1 ALGO and hold it until it's ready to be claimed. When the NFD is claimed, the user who sent it will receive the ALGO from the sale. Reserve an NFD for someone you'd like to onboard into #Algofam!