# ENSv2 Launches on Ethereum: New .eth Prices and Grace Period

![ENSv2 Launches on Ethereum: New .eth Prices and Grace Period](hero.webp)

**Ethereum Name Service (ENS) launched ENSv2 on Ethereum mainnet on October 27, 2026. Existing `.eth` names do not need to migrate to keep working, but ENS has introduced new registration and renewal pricing, payments in USDC, and a shorter grace period for names operating under ENSv2.** The upgrade also changes how names, subnames, permissions and resolvers are organized. For wallet users, the most important immediate question is not whether they must move their crypto—it is whether they understand their name's renewal status and the address to which it resolves.

ENS Labs announced the launch in its [official mainnet release](https://ens.domains/blog/post/ensv2-live-on-mainnet) on October 27. Its separate [October 22 pricing and expiration explanation](https://ens.domains/blog/post/ensv2-eth-pricing-grace-period) details the changes that affect name holders. The upgrade is **not an Ethereum network hard fork**, a new cryptocurrency wallet, or the launch of a separate ENS Layer 2.

> **Short answer:** ENSv2 is live on Ethereum mainnet. Existing `.eth` names still work, and upgrading is optional. The base annual price of a name with five or more characters is now **$8** rather than $5; official ENS registration and renewal use **USDC**. Names on ENSv2 have a **28-day grace period** during which expired names stop resolving, while unmigrated ENSv1 names keep their **90-day** grace period. When an eligible existing name upgrades, ENS adds **62 days to its expiration date** to preserve its previous release date. Users should verify the name, expiry, resolver records and checkout details in official ENS tools before signing.

## What happened

ENS Labs confirmed that **ENSv2 went live on Ethereum mainnet on October 27, 2026**. Its new registry and management design ships alongside updated name-management tools. Owners of existing `.eth` names can continue using them without mandatory migration; the launch also comes with updated renewal pricing and expiry rules that differ between ENSv1 and ENSv2.

### ENSv2 at a glance: what changed on October 27?

| Question | Confirmed position as of October 28, 2026 |
| --- | --- |
| Is ENSv2 live? | Yes, on Ethereum mainnet since October 27, 2026. |
| Must existing `.eth` holders migrate? | No; existing names continue working without re-registration. |
| Main technical upgrade | Hierarchical registries, per-name management, more granular access roles and linked records. |
| User-facing tools | Updated ENS App for everyday name management and ENS Explorer for technical inspection. |
| Base annual price for names of 5+ characters | $8, up from $5; the updated fee is **not limited to migrated names**. |
| Base annual price for 4-character / 3-character names | $160 / $640 respectively; unchanged before duration discounts. |
| Multi-year discounts | 12.5% for two years; about 31% for three to five; about 44% for six or more. |
| Registration and renewal payment | USDC through official ENS App or ENS Explorer; network fee is also shown and paid in USDC in those flows. |
| Grace period | 28 days for ENSv2; 90 days for names still on ENSv1. |
| What happens to an expired ENSv2 name? | It stops resolving during grace but can be renewed; ownership is not transferred during grace. |
| Upgrade transition adjustment | Eligible existing names receive 62 extra days on the expiry date when upgrading. |
| Does ENSv2 require moving ETH or importing a seed phrase? | No. |

The launch, upgrade option and new protocol features are described by [ENS Labs](https://ens.domains/blog/post/ensv2-live-on-mainnet). Prices, payment methods and expiration mechanics are documented by [ENS Support](https://support.ens.domains/en/articles/15180000-pricing-fees-and-multi-year-discounts) and the [ENS pricing announcement](https://ens.domains/blog/post/ensv2-eth-pricing-grace-period).

## What is ENS, and why should a wallet owner care?

Ethereum Name Service associates human-readable names such as `alex.eth` with records that applications can look up, including cryptocurrency destination addresses. A compatible wallet may display or resolve a name instead of asking its user to handle a long hexadecimal identifier. ENS can also store identity-related text records and support subnames, so it serves as both a payment convenience and a naming infrastructure layer for Web3 applications.

**An ENS name is not a crypto wallet.** Registering, upgrading or renewing a name does not replace a wallet's private keys, recovery phrase or underlying address. A name points to records configured by authorized parties, and those records can change. If a sender resolves an unfamiliar or compromised name, the apparently friendly label does not make the destination safe.

For context, see Terenval's [Ethereum address glossary](https://wallet.terenval.com/glossary/ethereum-address/) and [guide to sending cryptocurrency safely](https://wallet.terenval.com/answers/how-to-send-crypto-safely-between-wallets/). These are educational references, not a claim that every version of Terenval Wallet already supports all ENSv2 functions.

## What ENSv2 changes technically: registries, roles and records

### Hierarchical registries make names more independent

ENSv1 relied on a shared registry model, supplemented over time with tools such as the Name Wrapper. Under ENSv2, individual names can control their own registries for subnames. An organization controlling `example.eth`, for instance, can design separate rules for `team.example.eth` and other subnames instead of administering every name through the same flat structure.

This can help communities issue membership identifiers, projects coordinate team names and service providers manage larger namespaces. It **does not automatically verify** that every subname represents the person or entity it appears to represent. The underlying permission choices remain consequential.

### More precise roles can reduce overbroad access

ENSv2 adds enhanced, role-based access controls. Instead of giving one operator unrestricted authority, an owner may delegate narrower tasks, such as managing specific records or subnames. That is an architectural improvement, but the risk reduction is conditional: a mistakenly assigned role, compromised administrative wallet or malicious resolver setting can still lead to incorrect destination records.

### Name resolution still depends on compatible applications

ENSv2 introduces per-account permissioned resolvers and supports record linking. The new ENS Explorer provides visibility into ownership, roles, records and resolution. ENS documentation tells developers to use a compatible library and the **Universal Resolver** rather than hardcoding older contract addresses or assuming a particular shared resolver. New ENSv2 registrations and migrated names use new write paths, while non-migrated ENSv1 names may retain their existing record-management paths.

This is an implementation distinction, not merely an interface redesign. Developers maintaining wallet, DeFi, checkout or identity products should review the [ENSv2 readiness guide](https://docs.ens.domains/web/ensv2-readiness/) and [application integration documentation](https://docs.ens.domains/ensv2/tutorial-app-developers/).

## New .eth pricing: $8 a year, but the final bill depends on name length and term

The clearest price change is for **five-character-or-longer `.eth` names**: the annual base rate moves from **$5 to $8**. ENS Support specifies that this base-rate change applies whether or not an existing name has already upgraded to ENSv2. The annual base rates for four-character and three-character names remain **$160** and **$640**, respectively, before term discounts.

ENS also introduced term-based discounts for registrations and renewals. The discount is calculated on **the number of years added in that individual transaction**, not on how many years of registration the holder has accumulated in total.

| Years added in one transaction | Discount | 5+ character `.eth`: per year | Example total before network fee |
| --- | ---: | ---: | ---: |
| 1 year | 0% | $8.00 | $8.00 |
| 2 years | 12.5% | $7.00 | $14.00 |
| 3 years | Approximately 31% | $5.50 | $16.50 |
| 5 years | Approximately 31% | $5.50 | $27.50 |
| 6 years | Approximately 44% | $4.50 | $27.00 |

**Our calculation highlights a counterintuitive result:** at the published tiers, adding **six years costs $27 in base fees, while five years costs $27.50**, before network costs. It is therefore worth comparing the *total* displayed for several durations rather than assuming a shorter term always costs less. This is a simple arithmetic comparison of published rates, not a forecast of future pricing or gas.

The checkout amount can also reflect network fees, which are distinct from the base name price. ENS states that users can review the per-year rate and full total before approving a registration or renewal. Consult the [official pricing table](https://support.ens.domains/en/articles/15180000-pricing-fees-and-multi-year-discounts) for the current figures.

## USDC payments: what changed, and what still needs ETH?

Under the updated official ENS App and ENS Explorer, **registration and renewal are paid in USDC**, including the network fee shown for those flows. ENS Support says users may pay from Ethereum or a supported payment network, such as Base, Arbitrum, Optimism or Polygon, where offered by the application. The payment network is **not** the same thing as moving ENSv2's underlying naming contracts away from Ethereum mainnet.

ENS also notes that other actions—for example, upgrading a name, transferring it or editing records—may still require a little **ETH for gas**. Do not assume that holding USDC alone covers every operation. When an application requests a USDC token approval, verify the spender and amount; approval is separate from the subsequent registration or renewal payment.

The change is operationally useful because the base registration fee is denominated in dollars and now settled in a dollar-pegged token rather than requiring the user to calculate an ETH-denominated amount. It does **not** eliminate variable network fees or the need to verify the payment network and official application. See [ENS's stablecoin payment explanation](https://support.ens.domains/en/articles/17133064-can-i-pay-with-stablecoins).

## Expiration: 28 days on ENSv2 versus 90 days on ENSv1

**This is the change most likely to surprise someone who treats a `.eth` name like a permanent address.** Unmigrated ENSv1 names retain a **90-day grace period** after expiry. ENSv2 names receive **28 days**. During the ENSv2 grace period, an expired name **does not resolve**, its records cannot be modified and it cannot be transferred. The name can still be renewed, and another party cannot take ownership during grace.

ENS's [expiration guide](https://support.ens.domains/en/articles/15180020-expiry-grace-period) adds an important point: **anyone can pay to renew an expired name during grace, but renewal returns it to its existing owner**, not the payer. That distinction matters for users helping a colleague or family member restore a name.

After the ENSv2 grace period, the name enters a **21-day price-cooldown phase** with a declining premium above the base registration price. This is not an extension of the former owner's exclusive renewal window. If nobody registers the released name during the cooldown, it can eventually be registered at the ordinary base rate.

### Why the 62-day adjustment is not an extra permanent grace period

To avoid bringing forward an existing name's release date during an eligible ENSv1-to-ENSv2 upgrade, ENS adds **62 days to its expiration date**. The arithmetic is deliberate: **62 added days + 28 grace days = the former 90-day post-expiration window** for the original transition timeline. The name's recorded expiry moves later, but its ENSv2 grace period remains **28 days**.

For example, suppose an eligible name's original expiration date was **December 1, 2026**. Its prior ENSv1 90-day grace window would have ended around **March 1, 2027**. With the upgrade adjustment, the displayed expiry shifts approximately 62 days later to **February 1, 2027**; a subsequent 28-day grace period still ends around the same original release date. The illustration ignores boundary-time details and is **not** a substitute for the exact timestamp shown in the official ENS App.

This transition mechanism does not imply that future ENSv2 expirations receive 90-day protection. Once on ENSv2, renew in advance and confirm the updated expiry in the official interface.

## Why it matters

### Terenval's analysis: the bigger risk is name availability, not token custody

**Our assessment:** ENSv2's most consequential consumer-facing change is how **an expired identifier can stop resolving before the original owner loses it**. A payment address held in a non-custodial wallet does not disappear when its ENS name expires, and the underlying coins do not move. However, an application attempting to resolve the expired name may fail to obtain the destination. That can disrupt a payment request, login flow or identity profile even if the wallet's blockchain address itself remains valid.

This creates **two different continuity questions** that users should not confuse:

| Continuity question | What should users verify? | What ENSv2 does not do |
| --- | --- | --- |
| Does my wallet still control its address and funds? | Check the underlying address and relevant blockchain balance independently. | It does not move ETH, rotate private keys or replace your recovery phrase. |
| Will other applications still resolve my `.eth` name? | Confirm the name is unexpired, records point to the intended address and the app supports current ENS resolution. | It does not guarantee every older app immediately supports every ENSv2 integration. |

For individuals, the low-risk default is to **renew an important identifier before expiry and avoid rushed migration decisions**. For teams, review who has the authority to modify resolution records and who monitors expirations. For developers, test the actual resolution path instead of treating a green wallet connection indicator as proof of ENS compatibility.

This is Terenval's editorial assessment based on the technical behavior described in ENS documentation; it is not a claim of measured payment failures or an ENS Labs risk ranking.

## What crypto users should know

### What existing `.eth` owners should do now

1. **Confirm the real name and its expiration date** in the official [ENS App](https://app.ens.domains/). Do not trust a renewal link received in an unsolicited message.
2. **Decide whether migration is useful.** Existing names still work on ENSv1; upgrade only when you understand the new permissions, registration timeline and application compatibility.
3. **Compare renewal durations.** Check the full USDC amount and network fee; do not calculate solely from the one-year headline rate.
4. **Verify your records.** If you use the name to receive funds, check the resolver and the precise destination address on the intended network.
5. **Renew ahead of expiry.** An ENSv2 name that enters grace stops resolving, even though its owner can still recover it by renewing.
6. **Review role delegation.** For shared or organizational names, confirm which accounts can change records or manage subnames.
7. **Treat unsolicited upgrades, NFT claims and recovery requests as suspicious.** No legitimate ENSv2 migration requires sharing your seed phrase or private key.

ENS Labs has announced an optional commemorative NFT for eligible upgraded users. Any claim should be checked through verified ENS channels; do not connect a wallet or sign an unrelated transaction merely because a message refers to the launch.

## What does ENSv2 mean for wallets, Ethereum L2s and developers?

For **wallet users**, a recognizable name may make it easier to request or receive payment, but users should still confirm the resolved address before transferring cryptocurrency. A familiar `.eth` label does not prove ownership of a social account, business identity or destination token contract. This remains important for [safe wallet-to-wallet transfers](https://wallet.terenval.com/answers/how-to-send-crypto-safely-between-wallets/).

For **Ethereum**, the protocol's main contracts are deployed on mainnet. ENSv2 is a naming infrastructure release, not an Ethereum consensus change. **For L2s**, using USDC from a supported L2 to pay in the official app does not merge L1 and L2 balances or make bridges unnecessary. The chain and asset used for an actual payment still matter.

For **app and wallet developers**, ENS guidance recommends supported name-resolution libraries and Universal Resolver integration. An app that only reads records may need a library update; an app that registers names, edits records or manages permissions may require changes to its ENSv1/ENSv2 write paths. This rollout does not establish that **Terenval Wallet specifically** has implemented ENSv2 name resolution or administration; users should judge support by verified product functionality.

**For businesses and communities**, the new hierarchy and delegation model opens possibilities for managed subnames, but the same delegation flexibility increases the importance of documenting access control and recovery procedures. This conclusion is an implementation inference, not evidence that specific organizations have adopted the system.

## ENSv2 FAQ: quick answers for owners and wallet users

### Is ENSv2 live on Ethereum mainnet?

Yes. ENS Labs announced the ENSv2 mainnet launch on **October 27, 2026**. The protocol, ENS App and ENS Explorer were launched together.

### Do I need to migrate or buy my existing `.eth` name again?

No. Existing names continue to work without mandatory re-registration or migration. Upgrading is optional and may be appropriate for owners who want ENSv2 features.

### Does an unupgraded five-character `.eth` name still cost $5 a year?

No. According to ENS's current pricing documentation, the base price for names with five or more characters is **$8 a year**, **upgraded or not**, before applicable multi-year discounts and network costs.

### Does the 28-day grace period apply to names still on ENSv1?

No. Names remaining on ENSv1 retain the **90-day** grace period. The **28-day** rule applies to ENSv2 names.

### Can I still receive ETH if my ENSv2 name expires?

The underlying Ethereum address can continue receiving onchain transfers, but the expired ENSv2 name stops resolving during grace. Someone trying to pay using that name may not be able to obtain the address. Never equate the name's availability with control of the wallet's private keys.

### Why did my expiry date move 62 days after migration?

ENS designed the one-time adjustment to preserve the existing name's previously expected release date when the grace period changes from 90 to 28 days. It is not a permanent 62-day bonus on each renewal.

### Can I register or renew with ETH instead of USDC?

In the updated official ENS App and ENS Explorer, registration and renewal use **USDC**, including their network fees. Other operations may still require ETH for gas; check the current official checkout before approving any transaction.

### Does ENSv2 automatically work in every cryptocurrency wallet?

No. ENSv2 compatibility depends on each application's implementation. ENS recommends compatible libraries and Universal Resolver-based resolution. An ENS name can also have records for multiple networks, but that does not mean any particular wallet has built support for every type of record.

### Does ENSv2 change Bitcoin transactions or Ethereum private keys?

No. It does not change Bitcoin consensus or require holders to move ETH, rotate keys or import a recovery phrase.

## Sources

The following links document the launch and pricing rules; primary ENS sources are listed first.

1. **ENS Labs** — [ENSv2 Is Live on Mainnet](https://ens.domains/blog/post/ensv2-live-on-mainnet). October 27, 2026; mainnet launch, features and migration status.
2. **ENS Labs** — [ENSv2 .eth Pricing and Grace Period](https://ens.domains/blog/post/ensv2-eth-pricing-grace-period). October 22, 2026; fees, duration discounts and grace rules.
3. **ENS Support** — [Pricing, Fees and Multi-Year Discounts](https://support.ens.domains/en/articles/15180000-pricing-fees-and-multi-year-discounts). base rates and multi-year discount mechanics.
4. **ENS Support** — [Expiry and Grace Period](https://support.ens.domains/en/articles/15180020-expiry-grace-period). ENSv1 versus ENSv2 expiry and renewal behavior.
5. **ENS Support** — [Can I Pay with Stablecoins?](https://support.ens.domains/en/articles/17133064-can-i-pay-with-stablecoins). USDC payments and network considerations.
6. **ENS Documentation** — [ENSv2 Overview](https://docs.ens.domains/ensv2/overview/). registry architecture and protocol context.
7. **ENS Documentation** — [ENSv2 Readiness](https://docs.ens.domains/web/ensv2-readiness/). wallet and application migration guidance.
8. **ENS Documentation** — [ENSv2 Tutorial for App Developers](https://docs.ens.domains/ensv2/tutorial-app-developers/). developer integration and resolver guidance.
9. **The Block** — [ENS Labs Scraps Namechain L2, Shifts ENSv2 to Ethereum Mainnet](https://www.theblock.co/news/ecosystems/2026-02-06-ens-labs-scraps-namechain-l2-shifts-ensv2-fully-ethereum-mainnet-388932). February 6, 2026; independent background on the mainnet architecture decision.

## Editorial context and reporting methodology

**Editorial distinction:** Launch date, feature availability and published prices are sourced facts; the continuity-risk analysis, cost comparisons and name-owner checklist are Terenval's own interpretation and calculations based on those facts. The figures for discounted base registration do not include the variable network fee. This article does not represent live checkout testing, independent auditing of ENS contracts, or confirmation that every wallet already supports all ENSv2 functionality.

*Reporting cutoff: October 28, 2026. Name-management features, gas costs and platform integration may change after publication. Verify transaction details in official ENS applications before signing.*

## Editorial & technical review

- Published by: Adrian Vance
- Editorial standards and corrections: https://wallet.terenval.com/newsroom/
- Last reviewed: 2026-10-28T09:34:24Z

## Sources

- [ENS Labs — ENSv2 Is Live on Mainnet (October 27, 2026)](https://ens.domains/blog/post/ensv2-live-on-mainnet)
- [ENS Labs — ENSv2 .eth Pricing and Grace Period (October 22, 2026)](https://ens.domains/blog/post/ensv2-eth-pricing-grace-period)
- [ENS Support — Pricing, Fees and Multi-Year Discounts](https://support.ens.domains/en/articles/15180000-pricing-fees-and-multi-year-discounts)
- [ENS Support — Expiry and Grace Period](https://support.ens.domains/en/articles/15180020-expiry-grace-period)
- [ENS Support — Can I Pay with Stablecoins?](https://support.ens.domains/en/articles/17133064-can-i-pay-with-stablecoins)
- [ENS Documentation — ENSv2 Overview](https://docs.ens.domains/ensv2/overview/)
- [ENS Documentation — ENSv2 Readiness](https://docs.ens.domains/web/ensv2-readiness/)
- [ENS Documentation — ENSv2 Tutorial for App Developers](https://docs.ens.domains/ensv2/tutorial-app-developers/)
- [The Block — ENS Labs Shifts ENSv2 to Ethereum Mainnet (February 6, 2026)](https://www.theblock.co/news/ecosystems/2026-02-06-ens-labs-scraps-namechain-l2-shifts-ensv2-fully-ethereum-mainnet-388932)

Official article: https://wallet.terenval.com/news/ensv2-ethereum-mainnet-launch-domain-pricing-grace-period-2026-10-28/

[Machine-oriented Terenval index](https://wallet.terenval.com/llms.txt)
