Skip to main content

Registration Process Troubleshooting

Fix common registration errors: insufficient balance, expired commits, stuck transactions.

Updated over a week ago

Good to Know

  • Registration has 3 steps: commit β†’ wait 60 seconds β†’ register. Both the commit and register steps are separate transactions

  • You need ETH on Ethereum Mainnet for: the registration fee, gas costs, and a 10% buffer (refunded if unused)

  • You have 24 hours to complete Step 3 after Step 1. After that, you need to start over

  • Do not speed up or replace the commit transaction (Step 1) β€” the ENS App tracks it by hash, and replacing it will cause the registration to get stuck


Warnings

"Insufficient balance"

The "Insufficient balance" warning appears when your wallet doesn't have enough ETH on Ethereum Mainnet to cover the registration. Your wallet needs ETH for:

  • Registration fee

  • Gas costs

  • 10% buffer (refunded if unused)

Add more ETH and try again.

"Commitment Too Old"

The "Commitment Too Old" error means more than 24 hours passed between Step 1 (commit) and Step 3 (register). Start over from the beginning.

Fix: Clear site data or use a different browser, then restart.

"UnexpiredCommitmentExists"

The "UnexpiredCommitmentExists" error means a previous commit transaction is still active but wasn't fully picked up in your browser. Try:

  1. Disconnect wallet

  2. Close the page

  3. Reopen and reconnect

  4. Try again


Stuck Transactions

Registration page stuck on "Almost there"

If the registration page is stuck on "Almost there", your browser has lost track of the commit transaction. If this happens:

  1. Open your developer console

    • Chrome / Edge: Control + Shift + I

    • Safari / Mac: Option + ⌘ + J

  2. Run the following command: localStorage.getItem("registration-status")

  3. Open a chat with support and share:

    • Your wallet address

    • The ENS name

    • The returned text

This provides debug information we can pass to the engineering team.

Note: If you sped up or replaced the 'commit' transaction, the new hash isn't tracked. Fix: Clear site's browser cache and local storage, or use a different browser, then restart.


Related Articles

Did this answer your question?