🥷
Namespace
  • [ Introduction ]
    • ENS
    • Namespace
  • Official Links
  • [ Dapps ]
    • Overview
    • Onchain Subs (App)
      • Search & Register
      • Wizard
        • Listing an ENS Name
        • Features List
      • ENS Widget
      • Farcaster Frames
        • Default Frame
        • Custom Frame
    • Offchain Subs (DevPortal)
      • Subname create/manage
      • Resolver set
      • API keys
  • How-to Guides and Demos
  • [ Dev Docs ]
    • SDK
      • Offchain Manager
        • Installation
        • Generate API key
        • Create or Update Subname
        • DeleteSubname
        • IsSubnameAvailable
        • GetFilteredSubnames
        • AddressRecords
          • ChainName
        • TextRecords
        • DataRecords
      • Indexer Manager
        • Installation
        • Methods
        • GetL2Subname
        • GetL2Subnames
      • Mint Manager
        • Installation
        • GetMintDetails
        • GetMintTransactionParameters
        • IsSubnameAvailable
        • How To Mint L1 & L2 subname via mint-manager
      • Namespace Client (deprecated)
        • Installation
        • GetListedName
        • GetMintDetails
        • GetMintTransactionParameters
        • IsSubnameAvailable
        • GenerateAuthToken
    • APIs
      • Offchain Manager
      • Mint Manager
    • Infrastructure
      • Namespace L2 Subnames
  • [ ecosystem ]
    • Use Cases
  • [ Jobs ]
    • 🧑‍💻 Full-Stack Dev
    • 🥷 Dev-Rel Lead
    • 💼 BD Lead
Powered by GitBook
On this page
  1. [ Introduction ]

ENS

ENS Premier

NextNamespace

Last updated 18 hours ago

One of the major challenges in the blockchain industry is the complex and confusing user experience, particularly in transaction processes. Wallets with their public addresses, private keys, seed phrases, and especially long 42-character addresses (e.g. 0x3Kp6…17D3) pose a significant barrier to entry and navigating the space comfortably for the average user. This complexity not only deters adoption and long-term use but has also led to substantial losses due to address input errors among other things.

The blockchain user base, which is constantly growing, is often intimidated by these complexities. To solve this issue, ENS or has done a great job and has become an industry leader. ENS maps the long-format Wallet address to the human-readable .eth names. And so 0x3Kp6…17D3 becomes something like alice.eth, or neywork.eth or anon.eth, and so on.

Similar to what DNS does for IP addresses, ENS does the same for all blockchain-based resources: wallet addresses, contract addresses, token addresses, domains, or any onchain assets. Unlike DNS, however, which only maps IP addresses to human-readable .com, .net, .xyz, etc. domains to resolve websites in browsers, ENS names can be used much more broadly (wallet names, contract names, multichain identifiers, AI agent identity, in-app usernames, decentralized website domains, and many other cases), and as ERC721 or ERC1155 NFTs stay in full control of their owner with no centralized entity over them!

The Focus

Where ENS can and should rely on its Ecosystem Service Providers is to expand its face-on value and utility by building products and solutions that streamline its adoption for everyone who wishes to implement a Web3-native naming service powered by ENS protocol. Ease of implementation needs to be given for a range of users, and it should not be expected that they dedicate months of work to implement it.

Recognizing this opportunity, has built a , , , , and ENS Widget to offer a service that simplifies and streamlines the subname implementation and management.

Namespace
Platform
Dev Portal
Namespace SDK
Subpages
Ethereum Naming Service