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
  • V3 ARC 32 ABI
  • V3 ARC56 ABI
  • V2 Non-ABI Methods
  1. Reference
  2. On-Chain Reference

Contract methods

PreviousRegistry Application IDsNextName & Address Lookup

Last updated 4 months ago

For more explicit help, pflease reach out on our discord and the nfd-api channel

This list is just for reference. There is no formal compatibility guarantee of these contract calls into the future as new NFD versions are created, particularly any methods that are part of minting/registration as they will evolve/change greatly (as they're often called only once - at mint time).

If you plan to read NFDs entirely on-chain, please let us know as the exposed methods are assumed to evolve as the AVM conventions evolve and mature (notably ABI specs) likely only being put into a versioned compatibility guarantee at that point.

V3 ARC 32 ABI

V3 ARC56 ABI

V2 Non-ABI Methods

222KB
NFDRegistry.arc32.json
Registry ABI Calls
240KB
NFDInstance.arc32.json
NFD V3 ABI Calls
766KB
NFDRegistry.arc56.json
Registry ABI Calls
839KB
NFDInstance.arc56.json
NFD V3 ABI Calls