Skip to content
Logo

How Hyndle works

Hyndle separates the reservation request from on-chain NFT registration. This gives every request a clear review stage while keeping ownership, pricing, and final settlement verifiable on Base.

Registration flow

  1. Search: Enter a name to check its current status and policy eligibility.
  2. Create a request: The signed-in wallet creates a reservation candidate. An unpaid candidate does not lock the name.
  3. Pay the reservation fee: The user pays exactly 0.00053 ETH, plus Base network gas. Within one availability round, the first valid on-chain reservation payment confirmed by Hyndle becomes the review candidate.
  4. Review: Hyndle reviews the winning paid request. Other requests for the same name and round become superseded.
  5. Choose duration: After approval, select how many whole years you want to register the name.
  6. Review the price: The registration price is calculated from the name's effective length and selected duration.
  7. Protect the registration: Submit a salted commitment before the 72-hour approval window ends. The commitment conceals the name and mint parameters while the transaction is pending.
  8. Reveal and mint: After the minimum commitment age, reveal the approved registration and submit the exact mint payment. A commitment must be revealed before it becomes 24 hours old and before the signed authorization expires.
  9. Confirm: Once the receipt and expected contract event are verified, the name appears as your Hyndle NFT.

What Hyndle verifies

Hyndle independently verifies the important details of every registration:

  • normalized name and nameId
  • reservation ownership
  • recipient wallet
  • registration duration
  • required payment
  • payment amount and destination
  • transaction success and required confirmations
  • commitment ownership, age, and authorization deadline

Recovery

If you close or reload the page while a transaction is pending, return to the reservation page with the same wallet. Hyndle continues checking the transaction and restores the latest confirmed state.

Competing requests

Creating a reservation request is not a hold. More than one wallet may request the same available name, but the payment contract accepts only one successful claim for that name's current availability round. A later conflicting transaction can fail on-chain and may still consume network gas.