Minting Flow

All dotHYPE registrations follow a shared lifecycle—from name search to NFT minting. This page breaks down that flow so developers and users alike can understand what happens under the hood.

Regardless of whether you're minting via whitelist, reserved access, or public signature, the registration process moves through the same stages.

High-Level Flow

1. Search a name → Check availability and pricing

2. Validate eligibility → Based on mint phase (whitelist, reserved, or public)

3. Submit transaction → Confirm duration and pay with $HYPE

4. Mint NFT → Registry issues the .hype name as an ERC-721 token

5. Record expiration → Expiry timestamp is stored in the Registry

The Controller contract orchestrates all of this and ensures only valid requests make it through.

UX Flow Example

Let’s walk through what happens when a user mints a name:

1. User connects wallet to the mint UI

2. User types a name (e.g. artist.hype)

3. UI checks name availability via available(name)

4. UI fetches price for 1-year term via getPrice(name, duration)

5. Depending on the phase:

   • If whitelisted: user submits a Merkle proof

   • If reserved: contract verifies the address matches

   • If public: user signs an EIP-712 message and submits it

6. Controller processes payment in $HYPE

7. Registry mints the name and logs expiration

8. UI shows confirmation, name dashboard becomes active

On-chain Processing Summary

Behind the scenes:

• All logic is routed through the dotHYPEController

• The Controller ensures:

  • The name meets eligibility criteria

  • Duration and price are valid

  • Payment is processed and refunded if overpaid

• Once verified, the Controller:

  • Calls the Registry to mint the NFT

  • Sets expiration timestamp (now + duration)

Duration and Pricing

All names:

• Must be registered for at least 365 days

• Can be extended in 1-year increments

• Are priced according to character length:

  • 3 characters → higher tier

  • 4 characters → mid tier

  • 5+ characters → base tier

Pricing is in USD and converted to $HYPE using an oracle at time of mint.

Payment Details

• All mint payments are made in $HYPE

• Overpayments are refunded automatically

• A designated recipient receives mint funds (e.g. treasury multisig)

No approvals or token swaps needed—users only need $HYPE in their wallet.

Mint Result

Once minting is complete:

• The user owns a .hype name NFT

• It appears in their wallet

• It can be resolved across Web3 using the Resolver

• Expiration is stored and can be extended via renewal