# [EP 6.34] Register on.eth to the ENS DAO wallet and set the resolver

- Space: [ENS](https://snapshot.box/eth:0x323A76393544d5ecca80cd6ef2A560C6a395b7E3.md)
- Author: 0xb8c2C29ee19D8307cb7255e1Cd9CbDE883A267d5
- State: Queued
- Voting type: Basic
- Start: 2026-02-12 14:50 UTC
- End: 2026-02-19 00:10 UTC
- Votes: 280
- Open in Snapshot: https://snapshot.box/#/eth:0x323A76393544d5ecca80cd6ef2A560C6a395b7E3/proposal/69304512515872868228453463730257567312488838925636819022683533220991373699419

## Results

- For: 99.3%
- Against: 0.0%
- Abstain: 0.7%

## Proposal

# Previous Context

* [\[Temp Check\] Registration of on.eth to support interoperable addressing standards](https://discuss.ens.domains/t/temp-check-registration-of-on-eth-to-support-interoperable-addressing-standards/21541)
* [\[Temp Check\] l2.eth to Enable Chain-Specific Addresses](https://discuss.ens.domains/t/temp-check-l2-eth-to-enable-chain-specific-addresses/20862)
* [Allowing the DAO to manually issue .eth 2LDs, including 1- and 2- character ones](https://discuss.ens.domains/t/allowing-the-dao-to-manually-issue-eth-2lds-including-1-and-2-character-ones/20851)

# Description

This proposal registers the \`on.eth\` ENS name to the ENS DAO wallet (`0xfe89cc7abb2c4183683ab71653c4cdc9b02d44b7`) and sets the resolver to an on-chain registry-resolver contract (`0x2a9B5787207863cf2d63d20172ed1F7bB2c9487A`).

# Motivation

The Chain Registry-Resolver is a smart contract that acts as a **canonical, on-chain registry** for blockchain metadata. It serves as the resolver for the `on.eth` namespace and enables applications and users to retrieve metadata for **any** blockchain using a single human-readable identifier, such as \`base\` or \`solana\`.

Historically, blockchain metadata has been stored in centralized, fragmented repositories maintained by third parties. The Chain Registry-Resolver brings this metadata on-chain into a single, extensible registry, where control and update authority are delegated to the relevant chain operators.

# Specification

## Relevant Contracts

* &#x20;\`wallet.ensdao.eth\` • `0xfe89cc7abb2c4183683ab71653c4cdc9b02d44b7`
* \`registry.ens.eth\` • `0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e`&#x20;
* \`registrar.ens.eth\` • `0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85`
* ChainResolver (Proxy)\` • `0x2a9B5787207863cf2d63d20172ed1F7bB2c9487A`
* \`ChainResolver (Implementation)\` • `0x97df70ef350a5d2f606e0baf6d38de2ec26f7290`

### ChainResolver

The \`ChainResolver\` GitHub repo can be found here: [https://github.com/unruggable-labs/chain-resolver.](https://github.com/unruggable-labs/chain-resolver.)

In depth documentation outlining the functionality, interfaces, and implementation approach for the smart contract is available here: [https://github.com/ensdomains/docs/pull/508/changes.](https://github.com/ensdomains/docs/pull/508/changes.)

## Proposal

This proposal includes four components.

**1. Adding the DAO wallet as a controller on the \`BaseRegistrarImplementation\` smart contract.**

`To: 0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85`

`Value: 0`

`Calldata: 0xa7fc7a07000000000000000000000000fe89cc7abb2c4183683ab71653c4cdc9b02d44b7`

Simulation: [https://www.tdly.co/shared/simulation/709dde20-78e2-47e0-a952-d80d9772e5eb](https://www.tdly.co/shared/simulation/709dde20-78e2-47e0-a952-d80d9772e5eb)

**2. Registering the name \`on.eth\` to the DAO wallet.**

`To: 0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85`

`Value: 0`

`Calldata: 0xfca247ac6460d40e0362f6a2c743f205df8181010b7f26e76d5606847fb7be7fb6d135f9000000000000000000000000fe89cc7abb2c4183683ab71653c4cdc9b02d44b70000000000000000000000000000000000000000000000000000000012cc0300`

Simulation: [https://www.tdly.co/shared/simulation/2b0f1049-6820-4661-88bf-3b9fbee8ae84](https://www.tdly.co/shared/simulation/2b0f1049-6820-4661-88bf-3b9fbee8ae84)

**3. Setting the deployed \`ChainResolver\` as the resolver for**

\*\*\*\*  `on.eth`

The Resolver proxy is deployed at `0x2a9B5787207863cf2d63d20172ed1F7bB2c9487A`.

`To: 0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e`

`Value: 0`

`Calldata: 0x1896f70acabf8262fe531c2a7e8cd86e06342bc27fc0591ecd562fbac88280abc18ef8990000000000000000000000002a9b5787207863cf2d63d20172ed1f7bb2c9487a`

Simulation: [https://www.tdly.co/shared/simulation/291142ff-d41a-45ab-8263-34fad6b781b5](https://www.tdly.co/shared/simulation/291142ff-d41a-45ab-8263-34fad6b781b5)

**4. Removing the DAO wallet as a controller on the \`BaseRegistrarImplementation\` smart contract.**

`To: 0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85`

`Value: 0`

`Calldata: 0xf6a74ed7000000000000000000000000fe89cc7abb2c4183683ab71653c4cdc9b02d44b7`

Simulation: [https://www.tdly.co/shared/simulation/e2430d87-5475-4cea-a320-0e44640b1d3d](https://www.tdly.co/shared/simulation/e2430d87-5475-4cea-a320-0e44640b1d3d)

# Notes

The Registry-Resolver contract is currently owned by an Unruggable controlled deployment wallet (`0x81c11034fe2b2f0561e9975df9a45d99172183af`). This temporary ownership is limited to initial bootstrapping of chain identifiers and will be transferred to a neutral multisig once the initial registry state is established.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

