Setting Metadata Records
Last updated
NFD Docs (V3)
Last updated
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.
The address that will resolve when sending to an NFD (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, 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.
The owner address and the linked addresses are independent.
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 or Defly. 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.
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, 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.
