ENS Documentation
HomeTechnical DocsGovernance Docs
Search…
Technical Documentation
Introduction
Terminology
Frequently Asked Questions
ENS Deployments
Registrar Frequently Asked Questions
Deploying ENS on a Private Chain
DNS Registrar guide
Bug Bounty Program
ENS Improvement Proposals
Dapp Developer Guide
ENS Enabling your DApp
ENS Libraries
Working with ENS
Resolving Names
Managing Names
Registering & Renewing Names
ENS Front-End Design Guidelines
ENS as NFT
Contract API Reference
Name Processing
Registry
ReverseRegistrar
TestRegistrar
PublicResolver
.eth Permanent Registrar
DNS Registrar
Contract Developer Guide
Resolving Names On-chain
Writing a Resolver
Writing a Registrar
ENS Discussion Forum
ENS Support Chat
ENS Migration (February 2020)
Guide for DApp Developers
Technical Description
Powered By GitBook
Registering & Renewing Names
When users want to obtain a domain for the first time, they must interact with a registrar. Registrars are smart contracts that own a domain, and have a defined process for handing out subdomains. The registrar a user needs to interact with depends on the domain they want to obtain; for instance, a user wanting a .eth name will have to interact with the .eth registrar. Each registrar defines its own API for name registrations (and renewals, where appropriate).
At present, there are no libraries for interacting with registrars; DApps wishing to do so must interact with the registrar contract using a generic Ethereum library such as web3.js or web3.py. See the Contract API Reference for details on each registrar's interface.

Deployed Registrars

Dapp Developer Guide - Previous
Managing Names
Next - Dapp Developer Guide
ENS Front-End Design Guidelines
Last modified 3mo ago
Copy link
Edit on GitHub
Contents
Deployed Registrars