NFD API
  • NFDomains API
  • Quick Start
  • Reference
    • On-Chain Reference
      • On-Chain Diagram V3+
        • On-Chain Diagram V2+
        • V1 On-Chain Diagram
      • Registry Application IDs
      • Contract methods
      • Name & Address Lookup
        • V1 Resolution example (go)
          • Example PyTeal name/ID validity check
      • NFDs owned by Address
      • Reading of NFD metadata
      • Properties
      • Contract Changelog
    • NFDomains REST API Reference
    • Integrators Guide
      • Using an NFD for sending assets to Algorand accounts
      • Using an NFD to sending to non-Algorand chains.
      • Resolving an Algorand address to an NFD name / avatar
      • Interactive NFD lookup
      • Discord / Telegram bots
      • Linking an Application to an NFD
      • Using Vaults (2.x+)
      • Expirations / MBR liquidation
    • API Changelog
    • Status Page
  • Community
Powered by GitBook
On this page
  1. Reference

On-Chain Reference

NFDomains .algo names are controlled by the NFD Registry Contract which controls pricing, and the minting of new NFDs.

Each NFD is a standalone contract instance, with its own Algorand account (Vault) it controls. The registry acts as a contract factory, creating the NFDs and acting as the registrar and registry of record. Creation and resolving of names and addresses to names is via the registry.

The following pages provide details on the on-chain storage of NFDs and the manner in which they're located.

PreviousQuick StartNextOn-Chain Diagram V3+

Last updated 8 months ago