🥷
Namespace
  • [ Introduction ]
    • ENS
    • Namespace
      • Use Cases
  • [ Namespace Platform ]
    • Overview
    • Search & Registration
    • Manager
      • Listing an ENS Name
      • Features List
    • ENS Widget
    • Farcaster Frames
      • Default Frame
      • Custom Frame
    • Tutorials and Demos
  • [ Dev Docs ]
    • Overview
    • How-To Guides
      • Mint L1 or L2 subnames using SDK
    • Smart contracts
      • Namespace Minter
    • Backend API
      • POST /api/v1/mint
      • POST /api/v1/mint/verified
      • GET /api/v1/listings/availabe
    • Offchain Subnames API
      • Setting Up Offchain Resolver
      • Minting
        • Create a new ENS subname
      • Subnames
        • Resolve subname address
        • Check subname availability
        • Retrieve Complete Subname Dataset
        • Subname Search
        • Delete Subname
      • Text Records
        • Create or update subname text record
        • Delete a subname text record
        • Retrieve single subname text record
        • Retrieve all of subname's text records
      • Custom Data
        • Create or update custom subname data
        • Delete custom subname data
        • Retrieve single custom data object
        • Retrieve all of subname's custom data
    • Namespace SDK
      • Offchain Manager
        • Installation
        • Methods
        • Generate API key
        • CreateSubname
        • DeleteSubname
        • IsSubnameAvailable
        • GetFilteredSubnames
        • TextRecords
        • DataRecords
      • Indexer Manager
        • Installation
        • Methods
        • GetL2Subname
        • GetL2Subnames
        • GetL1Subnames
        • GetL1Subnames
        • GetL1Subname
      • Namespace Client (deprecated)
        • Installation
        • GetListedName
        • GetMintDetails
        • GetMintTransactionParameters
        • IsSubnameAvailable
        • GenerateAuthToken
    • Namespace L2 Subnames
  • [ ecosystem ]
    • Partnerships
    • Integrations
    • Links
    • ENS ideas and projects
  • [ Legal ]
    • Disclamer
    • Terms of Service
    • Privacy Policy
Powered by GitBook
On this page
  1. [ Dev Docs ]
  2. Offchain Subnames API

Setting Up Offchain Resolver

PreviousOffchain Subnames APINextMinting

Last updated 10 months ago

The OffchainResolver was introduced by ENS to allow on-chain resolution of ENS domain and subdomain records that are stored off-chain. OffchainResolver is configured with the URL of the gateway application that has access to the records stored by this API. Clients such as MetaMask will get records from the gateway, and send them to OffchainResolver for verification and resolution.

Thus, in order to have your records records resolved setting up the resolver, as described below, will be required:

  1. Choose the ENS domain for which you are minting subnames

  2. Go to the resolver section of your name, under the More tab, for example: https://app.ens.domains/name.eth?tab=more

  3. Choose Edit in the Resolver section

  1. Select the Custom Resolver option

  2. Provide the resolver address, and click Update to proceed with the update transaction

    • for the resolver on Mainnet use 0xF12d6Aa997F7c9Fc2E8968A19623211e8C8C1bF4

    • for Sepolia use 0x48243237e97257bCC97e53E53149Cbd49DD218EB

    • for Goerli use 0x0aBA2351994423770A35218c202c34B88BEa8041

Example adding Sepolia Resolver