# 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](https://docs.nf.domains/readme#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](https://docs.nf.domains/readme#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 ](https://docs.nf.domains/resources/new-to-algorand)or [Defly](https://docs.nf.domains/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](https://docs.nf.domains/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 %} *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nf.domains/platform/manage/setting-metadata-records.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.