πŸ“–
Pulse Domains
  • πŸ‘‹Introduction
  • 🟒Registration FAQ
  • πŸ“’Terminology
  • Guides
    • πŸͺ„Domain Registration
    • πŸ§β€β™€οΈUpdating Your Profile
    • πŸ₯·Preserving Your Privacy
    • πŸ‘₯Creating Subdomains
    • πŸ›©οΈDomain Transfer
    • 🀝DNS Domain Setup
    • 🍭Brand Guidelines
    • πŸ’ΈReferrals
    • πŸ“œWhitelist & Claims
    • 🌟Registration Widget
    • πŸͺ…CCIP & PNS
    • πŸͺ…Name Renewal
  • Deep Dives
    • 🍬Name Wrapper
      • πŸ”₯Fuses
      • ⏳Expiry
      • βœ…Approved Operators
    • πŸ‘¨β€πŸ”§Managing a Name
    • πŸ”€Homoglyphs
  • pls.fyi Profile
    • ✨Your Web3 Profile
  • PLS.TO dWeb
    • πŸͺInterPlanetary FileSystem (IPFS)
    • 🌐Your Decentralized Website
    • πŸ’»IPFS & PLS.TO Guide
  • Partner Sites
    • πŸ“ˆPulseCoinList.com
    • πŸ’±PulseSwap.io: The Aggregator of Aggregators
      • πŸ“ˆ Integration for Developers and Projects
  • Dapp Developer Guide
    • πŸ› οΈGetting Started
      • PNS Enabling your DApp
      • PNS Libraries
      • Working with PNS
      • Resolving Names
      • Managing Names
      • Registering & Renewing Names
      • PNS Front-End Design Guidelines
      • PNS as NFT
      • PNS Data guide
    • πŸ›Bug Bounty Program & Audit
  • βš™οΈContract Api Reference
    • πŸ“œDeployed Contracts
    • Name Processing
    • Registry
    • ReverseRegistrar
    • TestRegistrar
    • PublicResolver
    • .pls Permanent Registrar
      • Registrar
      • Controller
    • DNS Registrar
    • Name Wrapper
      • Expiry
      • Fuses
      • Wrapped States
    • Subgraph
      • Entities
      • Queries
  • πŸ“™Contract Developer Guide
    • Resolving Names On-chain
    • Writing a Resolver
    • Writing a Registrar
  • πŸ¦Έβ€β™‚οΈCommunity
    • Community Dev Resources
  • Links
    • πŸ•ΉοΈPNS App
    • 🐦Twitter
    • ✈️Telegram
    • πŸ’‘PNS Name Ideas (Community Site)
Powered by GitBook
On this page

Was this helpful?

  1. Dapp Developer Guide
  2. Getting Started

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 PulseChain library such as pns-sdk or ethers.js. See the Contract API Reference for details on each registrar's interface.

Deployed Registrars

  • .pls: The Permanent Registrar.

  • .test (testnets only): The test registrar.

  • .addr.reverse: The reverse registrar.

PreviousManaging NamesNextPNS Front-End Design Guidelines

Last updated 1 year ago

Was this helpful?

πŸ› οΈ