Hyperliquid Names
  • What is Hyperliquid Names?
  • Resolution
  • Fair Launch
  • How To
    • Getting funds on Hyper EVM
    • Auctions
      • FAQ
      • Video Walkthru
    • Minting a name
  • Hyperliquid Names on MetaMask
  • Smart Contracts
    • Core Smart Contracts
    • Technical Details
    • Deployments
  • dApp Integration
    • dApp Integration
    • Brand Kit
Powered by GitBook
On this page
  • Overview
  • Hyperliquid Names (ERC721)
  • Registrator (current: V1)
  • Router
  1. Smart Contracts

Core Smart Contracts

Hyperliquid Names is made up of a set of 3 core smart contracts: Hyperliquid Names, Registrator, and Router.

PreviousHyperliquid Names on MetaMaskNextTechnical Details

Last updated 7 months ago

Overview

The Hyperliquid Names protocol uses the namehash algorithm from ENS, but does not follow the ENS architecture. Like ENS, it handles forward and reverse resolution, but does not attempt to achieve 100% technical parity onchain with general DNS.

Hyperliquid Names (ERC721)

Hyperliquid Names is the ERC721 smart contract responsible for ownership, transfers, and resolving addresses or primary names. .hl names are converted to their namehash using the and its used as the unique tokenId.

Registrator (current: V1)

The Registrator smart contract is responsible for expiration and text records. New Registrators can be deployed and be automatically understood by the Hyperliquid Names smart contract through the Router. This allows us to both add new functionality to the protocol without limitations and ensure backwards compatibility. Additionally, the Registrator handles issuing of new names and reissuing expired names.

Router

The Router smart contract handles versioning of the Registrator. It is mainly used by the Hyperliquid Names smart contract to lookup the latest Registrator.

ERC137 namehash algorithm