🤖
LNS Documentation
  • Introduction
  • Terminology
  • Frequently Asked Questions
  • Tokenomics
  • LNS Deployments
  • Registrar Frequently Asked Questions
  • Deploying LNS on a Private Chain
  • DNS Registrar guide
  • Bug Bounty Program
  • ENS Improvement Proposals
    • ENSIP-1: ENS
    • ENSIP-2: Initial Hash Registrar
    • ENSIP-3: Reverse Resolution
    • ENSIP-4: Support for contract ABIs
    • ENSIP-5: Text Records
    • ENSIP-6: DNS-in-ENS
    • ENSIP-7: Contenthash field
    • ENSIP-8: Interface Discovery
    • ENSIP-9: Multichain Address Resolution
    • ENSIP-10: Wildcard Resolution
    • ENSIP-11: EVM compatible Chain Address Resolution
    • ENSIP-12: Avatar Text Records
  • Dapp Developer Guide
    • LNS Enabling your DApp
    • LNS Libraries
    • Working with LNS
    • Resolving Names
    • Managing Names
    • Registering & Renewing Names
    • LNS Front-End Design Guidelines
    • LNS as NFT
  • Contract API Reference
    • Name Processing
    • Registry
    • ReverseRegistrar
    • PublicResolver
    • .bch Permanent Registrar
      • Registrar
      • Controller
    • DNS Registrar
  • Contract Developer Guide
    • Resolving Names On-chain
    • Writing a Resolver
    • Writing a Registrar
    • LNS Support Chat
Powered by GitBook
On this page
Edit on GitHub

LNS Deployments

PreviousTokenomicsNextRegistrar Frequently Asked Questions

Last updated 2 years ago

Most of the time you can use a to do what you need. If for whatever reason, you need to interact with LNS directly, details for the currently supported deployments are detailed here.

The LNS registry is deployed at 0xCfb86556760d03942EBf1ba88a9870e67D77b627 on mainnet, and 0x32f1FBE59D771bdB7FB247FE97A635f50659202b on amber testnet.

On mainnet, the following registrars are deployed:

  • .bch, using the .bch Permanent registrar.

To find out the contract address of each tld, check the "controller" address of the tld (eg: for .bch

In addition, the test networks also have a deployment of the .bch registrar for testing purposes.

For other contract addresses such as root, multisig, controller, public resolver, and so on, you can see their address under

LNS library
https://app.bch.domains/name/bch
https://app.bch.domains/name/lns.bch/subdomains