# ENS Documentation ## Docs - [🪲 Bug Bounty Program](/bugs): The ENS bug bounty program rewards anyone who finds a bug in covered ENS smart contracts and ENS Labs assets. This page provides a brief overview of the program which is operated by Immunefi and ENS Labs. - [📝 Changelog](/changelog): This page contains a list of changes and events that happened to the ENS protocol & ecosystem. - [FAQ](/faq): ENS is supported by a wide range of wallets and dApps, some notable ones can be found on the [integrations page](https://ens.domains/). This page is currently under construction however a link to add yourself will be put here soon. - [Terminology](/terminology): This page contains a glossary of terms used in the ENS documentation. - [Name Wrapper Contract Details](/wrapper/contracts): The Name Wrapper contract is deployed on these chains: - [Creating a Subname Registrar](/wrapper/creating-subname-registrar): In the [Use Cases](/wrapper/usecases#sell-or-rent-subnames) section, we talked about the ability to stand up your own "registrar" to allow other people to register/claim subnames automatically. Maybe you want to give wrapped subnames out for free, or maybe you want to charge for them. Maybe you want to apply specific rules to the subnames, such as only allowing alphanumeric names. All of this is possible, and this article will break down what you need to do. - [Name Wrapper Expiry](/wrapper/expiry): In order to burn any fuses on a name, you must also set an **expiry** on it. This expiry determines how long any burned fuses are active for, and may also determine whether the name itself has expired. - [Name Wrapper Fuses](/wrapper/fuses): A "fuse" is a permission or perk that can be granted/revoked on a name. As the name implies, once the fuse is "burned", it cannot be unburned. - [Name Wrapper Overview](/wrapper/overview): Are you looking for user-facing guides on how to interact with the Name Wrapper in the ENS Manager App? If so, see here instead: [Name Wrapper Guides](https://support.ens.domains/en/collections/4194784-name-wrapper-guides) - [Wrapped States](/wrapper/states): Taking the Name Wrapper into account, an ENS name can be in one of these possible states: - [Name Wrapper Use-Cases](/wrapper/usecases): By default, newly registered names will use the Public Resolver, which just allows the current manager/controller of the name to update any records. - [Avatars](/web/avatars): Personalization of profiles is what makes identity great. This page covers the very special **avatar** record that enables users to take their avatar with them across the web. - [Design Guidelines](/web/design): Guidelines for designing interfaces that use ENS names - [Preparing for ENSv2](/web/ensv2-readiness): Everything you need to know to prepare your application for ENSv2. - [Listing a Users Names](/web/enumerate): In some cases you might want to show off all names that a user owns. Due to the nature of how the ENS Protocol works under the hood, this might be a slightly more difficult task than expected. - [Getting Started](/web): Integrate ENS into your dApp - [Tools & Libraries](/web/libraries): Tools to help you interface with the ENS protocol - [Multichain](/web/multichain): L2 & Crosschain Resolution - [Naming Contracts](/web/naming-contracts): Learn how to name your smart contracts with ENS - [Quickstart](/web/quickstart): Hey there 👋, this is the quickstart guide. If you want to learn the process checkout [everything about ENS in dApps](/web/). If you would rather just clone an example repository checkout these: - [Text Records](/web/records): Text records are key-value pairs that can be used to store any arbitrary data associated with a name. Think of this as a user's **digital backpack** utilized for the storage of preferences, public details, and more. - [Address Lookup](/web/resolution): Learn how to resolve blockchain addresses from human-readable names with ENS. - [Primary Names](/web/reverse): Primary names are now supported on both Ethereum Mainnet and popular L2s (Base, OP Mainnet, Arbitrum One, Scroll, and Linea). This enables users to have an end-to-end experience with ENS on their preferred L2! - [Sign In With Ethereum (SIWE)](/web/siwe): A specification that leverages Ethereum signatures to perform authentication - [Subdomains](/web/subdomains): We believe that any place an address is used, a name should be able to be used instead. The smart contracts you interact with have names, the deposit address for your favorite exchange has a name, your favorite DAO has a name, or maybe you use subnames to keep your wallets organized. - [Subgraph](/web/subgraph): This is a page covering the graph's ENS subgraph. The ENS subgraph indexes onchain events of second-level .eth names, and DNS imported names. It allows us to build a reasonable approximation of the ENS names an address owns. - [Offchain / L2 Resolvers](/resolvers/ccip-read): While ENS name resolution always starts from Ethereum Mainnet, it's possible to store almost all data associated with a name and its subdomains elsewhere. By leveraging [EIP-3668](https://eips.ethereum.org/EIPS/eip-3668) (CCIP Read) in a [Resolver](/resolvers/quickstart), developers can effectively defer resolution to an L2 or offchain API. - [Interacting with a Resolver](/resolvers/interacting): Set Addresses, Text Records, and more - [Resolver Interface Standards](/resolvers/interfaces): This page is a collection of methods that a resolver MAY implement. - [Public Resolver](/resolvers/public): Find the address of the latest public resolver on the [deployments page](/learn/deployments). - [Resolvers Quickstart](/resolvers/quickstart): At the heart of every ENS name is its resolver. A resolver is a smart contract that implements a specific set of Resolver features (see [Resolver Interface](/resolvers/interfaces)). The resolvers smart contract functions have control over the resolution process of a ["node"](/resolution/names#namehash) (a name or subdomain) and onwards (subdomains of itself). - [Universal Resolver](/resolvers/universal): A swiss army knife for resolution. - [Writing a Resolver](/resolvers/writing): Every ENS name has a resolver, which is responsible for resolving information about a name. - [Resolution](/resolution): The process by which we load information about a name is called resolution. It's a simple process, but it's important to understand. Here is a diagram of some of the contracts involved when resolving a name. - [Name Processing](/resolution/names): Normalization and recommendations for how to handle names - [DNS Registrar](/registry/dns): In [DNS on ENS](/learn/dns) we learned how ENS aims to extend the functionality of the DNS. On this page we will explore the implementation of DNSSEC, the DNSRegistrar, and the building blocks for gasless DNSSEC. - [The Registry](/registry/ens): Root Registry of the Ethereum Name Service - [ETH Registrar](/registry/eth): Smart contracts responsible for the ".eth" TLD - [Reverse Registrars](/registry/reverse): Reverse resolution is part of the [primary name](/web/reverse) feature. If you're just trying to fetch a name for an address, you should start there. - [Layer 2 & Offchain Resolution](/learn/ccip-read): All ENS resolution starts on Ethereum Mainnet (or testnet). However, by leveraging [CCIP Read](/resolvers/ccip-read) and [Wildcard Resolution](/ensip/10), name resolution can be taken cross-chain, offchain, and more. This allows for a lot of flexibility in how you can use your ENS and for storage of your ENS records on your favourite Layer 2, or even offchain. - [Deployments](/learn/deployments): This page contains information that is only relevant to developers who would like to interact with the contract manually. Most libraries will handle this for you. - [DNS on ENS](/learn/dns): ENS supports DNS names, allowing users to import DNS names into ENS. - [What is the Ethereum Name Service?](/learn/protocol): The Ethereum Name Service (ENS) is a distributed, open, and extensible naming system based on the Ethereum blockchain. - [Resolution](/learn/resolution): The ENS Resolution Process - [ENSIP-1: ENS](/ensip/1): This ENSIP describes the details of the Ethereum Name Service, a proposed protocol and ABI definition that provides flexible resolution of short, human-readable names to service and resource identifiers. This permits users and developers to refer to human-readable and easy to remember names, and permits those names to be updated as necessary when the underlying resource (contract, content-addressed data, etc) changes. - [ENSIP-10: Wildcard Resolution](/ensip/10): Provides a mechanism to support wildcard resolution of ENS names (formerly [EIP-2544](https://eips.ethereum.org/EIPS/eip-2544)). - [ENSIP-11: EVM compatible Chain Address Resolution](/ensip/11): Introduces coinType for EVM compatible chains (amending [ENSIP-9](https://docs.ens.domains/ensip/9)). - [ENSIP-12: Avatar Text Records](/ensip/12): A standard for storage of the avatar text record in ENS. - [ENSIP-13: SAFE Authentication For ENS](/ensip/13): Using ENS Text Records to facilitate safer and more convenient signing operations. | - [ENSIP-14: On Chain Source Parameter](/ensip/14): Using the reveal secret as a way to have on chain information about the source of the registration. - [ENSIP-15: Name Normalization](/ensip/15): This ENSIP standardizes Ethereum Name Service (ENS) name normalization process outlined in [ENSIP-1 § Name Syntax](/ensip/1#name-syntax). - [ENSIP-16: Metadata Event Discovery](/ensip/16): This ENSIP specifies APIs for querying metadata directly on the resolver for EIP-3668 (CCIP Read: Secure offchain data retrieval) enabled names. EIP-3668 will power many domains in the future, however since the retrieval mechanism uses wildcard + offchain resolver, there is no standardised way to retrieve important metadata information such as which L2/offchain database the records are stored on and where JSON RPC endpoint is to find event log information. - [ENSIP-17: Gasless DNS Resolution](/ensip/17): This standard describes a mechanism by which users can specify ENS resolvers and resolution data as DNS TXT records, resulting in a system where DNS names are resolvable in ENS with no onchain actions required. - [ENSIP-18: Profile Text Records](/ensip/18): This ENSIP which extends [ENSIP-5: Text Records](https://docs.ens.domains/ensip/5) defines a set of text records that should be used for profile information, along with the format that each should have. - [ENSIP-19: Multichain Primary Names](/ensip/19): This ENSIP standardizes [reverse](#reverse-resolution) and [primary name](#algorithm) resolution for all coin types, and defines how this resolution process operates across the [multichain Ethereum](#multichain-ethereum) ecosystem. - [ENSIP-2: Initial Hash Registrar](/ensip/2): This ERC describes the implementation, as deployed to the main ethereum network on 2017-05-04, of a registrar contract to govern the allocation of names in the Ethereum Name Service (ENS). The corresponding source code is [here](https://github.com/ethereum/ens/blob/mainnet/contracts/HashRegistrarSimplified.sol). - [ENSIP-20: Wildcard Writing](/ensip/20): This ENSIP proposes a standardized mechanism for managing offchain domains within the Ethereum Name Service (ENS) ecosystem. It addresses the growing trend of storing domains off the Ethereum blockchain to reduce transaction fees while maintaining compatibility with existing ENS components. The proposal outlines methods for domain registration, transferring, and setting records, ensuring a consistent approach to offchain domain management. - [ENSIP-21: Batch Gateway Offchain Lookup Protocol](/ensip/21): This standard establishes the Batch Gateway Offchain Lookup Protocol (BGOLP). - [ENSIP-22: Contract Features](/ensip/22): This ENSIP standardizes [ERC-7996](https://eips.ethereum.org/EIPS/eip-7996) contract features relevant to ENS, enabling new optimizations while preserving compatibility with existing deployments. - [ENSIP-23: Universal Resolver](/ensip/23): This ENSIP standardizes [IUniversalResolver](#specification) (UR), an universal entrypoint for resolving ENS names. UR incorporates onchain algorithms for [ENSIP-1: ENS](./1), [ENSIP-10: Wildcard Resolution](./10), [ENSIP-19: Multichain Primary Names](./19), [ENSIP-21: Batch Gateway](./21), and [ENSIP-22: Contract Features](./22) to reduce integration complexities. - [ENSIP-24: Arbitrary Data Resolution](/ensip/24): This ENSIP proposes a new resolver profile for resolving arbitrary `bytes` data. - [ENSIP-3: Reverse Resolution](/ensip/3): Specifies a TLD, registrar, and resolver interface for reverse resolution of Ethereum addresses using ENS (formerly [EIP-181](https://eips.ethereum.org/EIPS/eip-181)). - [ENSIP-4: Support for contract ABIs](/ensip/4): A mechanism for storing ABI definitions in ENS, for easy lookup of contract interfaces by callers (formerly [EIP-205](https://eips.ethereum.org/EIPS/eip-205)). - [ENSIP-5: Text Records](/ensip/5): A standard for storage of text records in ENS (formerly [EIP-634](https://eips.ethereum.org/EIPS/eip-634)). - [ENSIP-6: DNS-in-ENS](/ensip/6): Defines a resolver profile for ENS that provides features for storage and lookup of DNS records (formerly [EIP-1185](https://eips.ethereum.org/EIPS/eip-1185)). - [ENSIP-7: Contenthash field](/ensip/7): Introduces a field for storing content addresses and hashes in ENS (formerly [EIP-1577](https://eips.ethereum.org/EIPS/eip-1577)). - [ENSIP-8: Interface Discovery](/ensip/8): Defines a method of associating contract interfaces with ENS names and addresses, and of discovering those interfaces (formerly [EIP-1844](https://eips.ethereum.org/EIPS/eip-1844)). - [ENSIP-9: Multichain Address resolution](/ensip/9): Introduces new overloads for the `addr` field for ENS resolvers, which permit resolution of addresses for other blockchains via ENS (formerly [EIP-2304](https://eips.ethereum.org/EIPS/eip-2304)). - [ENS Improvement Proposals](/ensip): This page contains a summary of all the ENS Improvement Proposals (ENSIPs) that have been proposed, and their current status. Improvement Proposals have included anything from new contract features, to text record standards, protocol features, and more. - [Hosting a Decentralized Website](/dweb/intro): Introduction to hosting a decentralized website using ENS - [Supported TLD List](/dns/tlds): Any DNS TLD that supports DNSSEC can be used with ENS - [ENS DAO Constitution](/dao/constitution): The ENS constitution is a set of binding rules that determine what governance actions are legitimate for the DAO to take. - [The ENS Foundation](/dao/foundation): Having a legal entity that represents the DAO in the "real world" is valuable for a number of reasons: - [Welcome to ENS DAO](/dao): The ENS DAO governs the ENS protocol and treasury - [ENS DAO Security Council](/dao/security-council): The ENS DAO Security Council is a 4-of-8 multi-sig with a limited mandate: to cancel malicious proposals that threaten the DAO, particularly those that would compromise the treasury. It was created to address vulnerabilities stemming from low voter participation relative to treasury size. - [ENS DAO Stewards](/dao/stewards): The DAO is governed through a democratic process in which all major matters are decided through a vote open to all holders of governance tokens. Those who wish can also delegate their voting power, entrusting somebody else to keep tabs on the latest DAO matters. - [The ENS Token](/dao/token): ENS Airdropped tokens to anyone who held an ENS name on *October 31st, 2021*. **THERE ARE NO PLANS FOR ANOTHER AIRDROP**. Please be weary of any notices of airdrops as these could turn out fraudulent. - [ENS DAO Working Group Rules](/dao/wg/rules): *This document represents the current state of the Working Group Rules as created by [EP0.4](https://snapshot.box/#/s:ens.eth/proposal/0x899ead1d9b9b98f63f6a60dc0939bef55dbe365e78c6a550f07be969a47f148b), and amended by [EP1.8](https://snapshot.box/#/s:ens.eth/proposal/0xc7186cf8bebe47600f8d847e76f7971ea97b48bc04eda1e07780aff91fb6410d) and [EP4.8](https://snapshot.box/#/s:ens.eth/proposal/0x26a5c8dec547837495707e70446d1e7cd874a91f75753c602998f6e70083a266). These should represent the canonical version of the rules and any social proposal to amend it should include a PR to this document.* - [undefined](/dao/proposals/6.8): We have identified that the legacy ENS multisig, which originally controlled ENS before the DAO was created, still has the 'controller' role on the ENS root. This means that a majority of multisig keyholders could create or replace any ENS TLD other than .eth. .eth is locked and cannot be modified by the DAO or anyone else. - [undefined](/dao/proposals/0.1): *Note: This was previously numbered EP1.* - [undefined](/dao/proposals/0.2): *Note: This was previously numbered EP2.* - [undefined](/dao/proposals/0.3): *Note: This was previously numbered EP3.* - [undefined](/dao/proposals/0.4): *Note: This was previously numbered EP4.* - [undefined](/dao/proposals/1.1): *Note: This was previously numbered EP5.* - [undefined](/dao/proposals/1.2.1): *Note: This was previously numbered EP6.1.* - [undefined](/dao/proposals/1.2.2): *Note: This was previously numbered EP6.2.* - [undefined](/dao/proposals/1.3.1): *Note: This was previously numbered EP7.1.* - [undefined](/dao/proposals/1.3.2): *Note: This was previously numbered EP7.2.* - [undefined](/dao/proposals/1.3.3): *Note: This was previously numbered EP7.3.* - [undefined](/dao/proposals/1.3.4): *Note: This was previously numbered EP7.4.* - [undefined](/dao/proposals/1.4): *Note: This was previously numbered EP8.* - [undefined](/dao/proposals/1.5): *Note: This was previously numbered EP9.* - [undefined](/dao/proposals/1.6): *Note: This was previously numbered EP10.* - [undefined](/dao/proposals/1.7): *Note: This was previously numbered EP11.* - [undefined](/dao/proposals/1.8): *Note: This was previously numbered EP12.* - [undefined](/dao/proposals/1.9): *Note: This was previously numbered EP13.* - [undefined](/dao/proposals/2.1): *Note: This was previously numbered EP14.* - [undefined](/dao/proposals/2.2.1): *Note: This was previously numbered EP16.1.* - [undefined](/dao/proposals/2.2.2): *Note: This was previously numbered EP16.2.* - [undefined](/dao/proposals/2.2.3): *Note: This was previously numbered EP16.3.* - [undefined](/dao/proposals/2.2.4): The DAO is seeking a fund manager to manage an endowment fund. This fund will be established from some combination of current treasury and ongoing revenue, and will exist to insulate the DAO from economic fluctuations, ensuring it can continue its core operations regardless of the wider economic outlook. - [undefined](/dao/proposals/2.2.5): Following the RFP process approved in EP2.2.4, the Meta-Governance Working Group stewards have selected a short list of potential fund managers for the DAO to elect to manage the ENS Endowment. - [undefined](/dao/proposals/3.1.1): The ENS Ecosystem Working Group requests funding of 935,000 USDC and 254 ETH from the ENS DAO for Q1/Q2 2023. - [undefined](/dao/proposals/3.1.2): The Meta-Governance Working Group requests funding of 364,000 USDC, 125 ETH, and 3,500 $ENS from the ENS DAO for Q1/Q2 2023. - [undefined](/dao/proposals/3.1.3): The Public Goods Working Group requests funding of 250,000 USDC and 50 ETH from the ENS DAO for Q1/Q2 2023. - [undefined](/dao/proposals/3.2): This proposal executes all three Working Group funding requests for Q1/Q2 2023 as passed in EP 3.1.1, EP 3.1.2, and EP 3.1.3. For more detail, view the [ENS Governance docs](https://docs.ens.domains/v/governance/governance-proposals/term-3) or view the links below. - [undefined](/dao/proposals/3.3): This proposal executes a swap of 10,000 ETH into USDC, to ensure ENS DAO has enough to cover operating expenses for 18 - 24 months. - [undefined](/dao/proposals/3.4): First tranche to fund the Endowment with 16,000 ETH sent from [ENS DAO](https://etherscan.io/address/0xfe89cc7abb2c4183683ab71653c4cdc9b02d44b7) to the [ENS Endowment](https://etherscan.io/address/0x4F2083f5fBede34C2714aFfb3105539775f7FE64) and an additional 150 ETH sent to the [Meta-Gov Pod](https://etherscan.io/address/0x91c32893216dE3eA0a55ABb9851f581d4503d39b) to account for karpatkey and Steakhouse monthly fees. - [undefined](/dao/proposals/3.5): With the new Name Wrapper, we will add a new .eth controller that allows registering wrapped names directly as well as registering with multiple records and adding a reverse record in 1 transaction. This will reduce the transactions required from 4 to 2 (for adding records + reverse). This will be added as a controller to the NameWrapper, and the NameWrapper will be added as the new controller of the existing .eth Base Registrar. - [undefined](/dao/proposals/3.6): This is a vote to elect a new director of the ENS Foundation. - [undefined](/dao/proposals/3.7): This is a vote to approve [ENSIP-15: Normalization Standard.](https://docs.ens.domains/ens-improvement-proposals/ensip-15-normalization-standard) - [undefined](/dao/proposals/4.1): This proposal introduces additional actions and strategies to the [ENS Endowment](https://discuss.ens.domains/t/ep3-4-executable-fund-the-endowment-first-tranche/16277?u=alisha.eth), which enhance the Endowment's performance, adaptability, and diversification. - [undefined](/dao/proposals/4.10): The ENS DAO has established itself as the key governance entity for the Ethereum Name Service (ENS) and has demonstrated capability and responsibility in ownership of several aspects of the protocol. We now propose the further decentralization of the ENS governance structure by transferring ownership of the ENS root key from the current multisig system (multisig.ens.eth) to the ENS DAO (wallet.ensdao.eth). - [undefined](/dao/proposals/4.2): This proposal outlines the allocation of the second tranche, comprising 16,000 ETH, from the [ENS DAO](https://etherscan.io/address/0xfe89cc7abb2c4183683ab71653c4cdc9b02d44b7) to the [ENS Endowment](https://etherscan.io/address/0x4F2083f5fBede34C2714aFfb3105539775f7FE64). Additionally, it introduces minor adjustments to the existing permissions preset for maintenance purposes. - [undefined](/dao/proposals/4.3): This proposal initiates a transfer of 117 ETH to the Meta-Governance Working Group to facilitate the refunding of .eth names invalidated by ENSIP-15, the latest ENS name normalization standard. - [undefined](/dao/proposals/4.4.1): The ENS Ecosystem Working Group requests funding of 409,000 USDC to support operations until the March 2024 funding window. This is the only funding request of this term. - [undefined](/dao/proposals/4.4.2): The ENS Meta-Governance Working Group requests funding of the below to **support operations until the March 2024 funding window**. This means the Working Group will not be requesting funds in the January 2024 Funding Window. - [undefined](/dao/proposals/4.4.3): The ENS Public Goods Working Group requests funding of the below to **support operations until the March 2024 funding window**. The Working Group intends to refrain from requesting funds in the upcoming January 2024 Funding Window. - [undefined](/dao/proposals/4.5): This proposal introduces new actions and strategies to the Endowment with the aim of enhancing diversification and adapting to current market conditions. Notable additions include ETH-neutral strategies involving Liquid Staking Protocols and established Money Markets. - [undefined](/dao/proposals/4.6): This proposal executes all three Working Group funding requests for the October 2023 funding window as passed in EP 4.4.1, EP 4.4.2, and EP 4.4.3. For more detail, view the ENS Governance docs at [https://basics.ensdao.org](https://basics.ensdao.org) 1 [Draft Discourse link](https://discuss.ens.domains/t/ep-4-6-executable-october-2023-working-group-funding/18064) - [undefined](/dao/proposals/4.7): The intent of this proposal is to add new Streams for service providers and propose a structure on how to elect them. - [undefined](/dao/proposals/4.8): The intent of this proposal is to modify the working group guidelines to enhance the DAO's ability to attract and retain talent. - [undefined](/dao/proposals/4.9): Following the approval of [EP4.7](/dao/proposals/4.7) by the DAO, prospective service providers have submitted applications to be considered by the DAO for funding. This proposal collects successful applications for a vote by the DAO. - [undefined](/dao/proposals/5.1): The ENS labs team has been working on a new version of the DNSSEC oracle and the DNS registrar that, combined with wildcard resolution (ENSIP 10) and CCIP-Read, allow for 'gasless DNSSEC' - enabling the use of DNS names inside ENS with no onchain transactions required. This proposal replaces the existing DNSSEC registrar with the new one. - [undefined](/dao/proposals/5.10): Following the successful passing of the [EP5.7](https://snapshot.org/#/ens.eth/proposal/0xf3a4673fe04a3ecfed4a2f066f6ced1539a5466d61630428333360b843653c54), this proposal aims to confirm the 8 individuals who will form the Security Council with the permissions defined in [EP5.7](https://snapshot.org/#/ens.eth/proposal/0xf3a4673fe04a3ecfed4a2f066f6ced1539a5466d61630428333360b843653c54). The Security Council will be responsible for protecting the organization from potential governance attacks by having the ability to cancel malicious proposals using the [SecurityCouncil](https://github.com/blockful-io/security-council-ens/blob/main/README.md) smart contract. - [undefined](/dao/proposals/5.11): Meta-Governance is seeking funding to support DAO-wide operations, including Working Groups, treasury management, and governance initiatives. This request aligns with Rule 10.1.1 of the [Working Group Rules](https://docs.ens.domains/dao/wg/rules) and amendments introduced in [EP 4.8](https://docs.ens.domains/dao/proposals/4.8). This proposal will execute the funding specification according to [EP 5.9](https://snapshot.org/#/ens.eth/proposal/0x66d355555c24ed0d2fed0aee89e4fe009e2925c84144c4edc707d33e7c19e554), as amended by [EP 5.8](https://snapshot.org/#/ens.eth/proposal/0x1f328fd1fda5f3cabfdace3e521403def7ad41b0b0582e27334c135cd23c511d). - [undefined](/dao/proposals/5.12): This proposal aims to roll out an updated version of the Zodiac Roles Modifier module. The new version improves usability and transparency of treasury management operations. Upon approval, the Roles Modifier v2 module will be activated. - [Roles v2 Migration](/dao/proposals/5.12): As [previously stated](https://discuss.ens.domains/t/endowment-initiation/15952#a-list-of-zodiac-roles-modifier-permissions-for-the-manager-role-9), the Zodiac Roles Modifier facilitates karpatkey’s proxy management of the Endowment by ensuring that only pre-approved transactions, defined by the permissions policy voted on by the DAO, can be executed. In collaboration with karpatkey, the Gnosis Guild team has significantly upgraded the Zodiac Roles Modifier module and the Zodiac Roles app. These enhancements have resulted in a more powerful and robust on-chain permissions infrastructure with the following improvements: - [Changes to Permissions policy](/dao/proposals/5.12): **Introduction of Allowances**: Implementation of spending limits within permissions. - [Audit Considerations](/dao/proposals/5.12): **Introduction of Allowances**: Implementation of spending limits within permissions. - [Additional Considerations](/dao/proposals/5.12): **Introduction of Allowances**: Implementation of spending limits within permissions. - [undefined](/dao/proposals/5.13): The primary mission of ENS DAO is to govern the protocol and allocate resources from the treasury in line with the DAO's constitution and broader objectives. However, due to changing economic dynamics, the DAO is increasingly vulnerable to attacks aimed at draining its treasury. - [undefined](/dao/proposals/5.14): This proposal aims to introduce new permissions for deploying Endowment funds, focusing on improved diversification and alignment with the evolving market landscape and liquidity. We are also introducing an independent audit report together with the Permissions Update; this will be the standard practice for Permissions Updates going forward. - [Abstract](/dao/proposals/5.14): This proposal aims to introduce new permissions for deploying Endowment funds, focusing on improved diversification and alignment with the evolving market landscape and liquidity. We are also introducing an independent audit report together with the Permissions Update; this will be the standard practice for Permissions Updates going forward. - [Motivation](/dao/proposals/5.14): Effective treasury management strategies must be adapted to market conditions and protocol updates; for existing Permissions, there might be migrations and introductions of new pools; for new Permissions, protocols and pools that were previously considered immature and unsuitable for the Endowment’s risk appetite may become viable options as they become more time- and battle-tested. This proposal seeks to request new permissions from the ENS DAO for karpatkey, enabling the introduction of new yield-generation strategies for the Endowment. - [Specification](/dao/proposals/5.14): Deposit osETH on Aave v3; - [Auditing process](/dao/proposals/5.14): Deposit osETH on Aave v3; - [undefined](/dao/proposals/5.15): The proposal threshold for propose new executable ENS proposals is high, and rightly so. ENS is one of the most popular DAOs and community in the Web3 community and keeping the quality bar of proposals to the highest standard is very important. However, ENS also has the treasury and the desire to expand the community and make proposing easier and more accessible to enable more builders to come and build in ENS. - [undefined](/dao/proposals/5.16): This executable proposal seeks to implement the reimbursement payment to ENS Labs for the legal fees incurred while pursuing litigation to protect the eth.link domain. The reimbursement was approved in the previously passed social proposal [EP 5.3](./5.3). - [undefined](/dao/proposals/5.17.1): The Meta-Governance Working Group is responsible for providing governance oversight and supporting the management and operation of working groups through DAO tooling and governance initiatives as well as treasury management for the DAO. - [undefined](/dao/proposals/5.17.2): The ENS Ecosystem Working Group requests funding of 836,000 USDC to support operations through April 2025. This is the only funding request of Term 5. - [undefined](/dao/proposals/5.17.3): The ENS Public Goods Working Group requests funding to support operations until the next funding window in April 2025. - [undefined](/dao/proposals/5.18): The ENS DAO Working Group Rules place the responsibility for steward compensation on the Metagov working group. - [undefined](/dao/proposals/5.19): This proposal establishes a pilot program to distribute ENS governance to eligible DAO contributors who have been selected by the DAO to receive a grant, bounty, or other payment for services. The program would also serve as a pilot, and if successful, could become a long-term initiative, aiming to cover all DAO USDC and ETH recipients, while setting a policy for future governance distribution. - [undefined](/dao/proposals/5.2): This EP will initiate the Streams for Service Providers as selected on [EP4.9](https://docs.ens.domains/dao/proposals/4.9) - [undefined](/dao/proposals/5.20): This proposal suggests introducing and implementing an [Investment Policy Statement (IPS)](https://github.com/ensdomains/docs/blob/master/src/public/governance/dao-investment-policy.pdf) for the ENS Endowment. - [undefined](/dao/proposals/5.21): This proposal aims to compensate the blockful team for their work in identifying, analyzing, reporting and mitigating a severe vulnerability in ENS DAO's governance structure. - [undefined](/dao/proposals/5.22): This executable proposal seeks to implement the revised budget stream to ENS Labs develop, maintain and audit [ENSv2](https://discuss.ens.domains/t/ens-labs-development-proposal-ensv2-and-native-l2-support/19232). The motivation, justification, budget breakdown, and development plan was previously detailed in a [Temp Check](https://discuss.ens.domains/t/temp-check-ensv2-development-funding-request/19762) request. - [undefined](/dao/proposals/5.23): This proposal aims to compensate the blockful team for their work in identifying, analyzing, reporting and mitigating a severe vulnerability in ENS DAO's governance structure. - [undefined](/dao/proposals/5.24): This proposal executes all three Working Group funding requests for the October 2024 funding window as passed in [EP 5.17.1](https://discuss.ens.domains/t/5-17-1-social-funding-request-ens-meta-governance-working-group-term-5-oct-window/19677), [EP 5.17.2](https://discuss.ens.domains/t/5-17-2-social-funding-request-ens-ecosystem-working-group/19678), and [EP 5.17.3](https://discuss.ens.domains/t/5-17-3-social-funding-request-ens-public-goods-working-group/19679) as well as [EP 5.21](https://snapshot.org/#/ens.eth/proposal/0x5067725bef9cde0de0024adedb653a7a1752aefa726adf628b77048d85821a6d) and [EP 5.19](https://snapshot.org/#/ens.eth/proposal/0xfa54ff2b55f0495c96ec2d8645241bcff48ca6afe1f4925fb51f29c4667252df). - [undefined](/dao/proposals/5.25): This is a resubmission of \[EP 5.24], with no changes to the funding amounts or technical specifications. - [undefined](/dao/proposals/5.26): This executable proposal implements the Governance Distribution Pilot Program approved in [EP5.19](https://snapshot.org/#/ens.eth/proposal/0xfa54ff2b55f0495c96ec2d8645241bcff48ca6afe1f4925fb51f29c4667252df). Following the community's selection of the 30k ENS distribution option, this proposal authorizes the transfer of ENS tokens from the treasury to implement the program. - [undefined](/dao/proposals/5.27): The Name Wrapper's upgrade mechanism contains a vulnerability whereby a malicious DAO could use the upgrade mechanism to seize control of wrapped names without the owner's consent, documented [here](https://discuss.ens.domains/t/security-advisory-a-malicious-dao-update-could-reduce-the-registration-duration-of-registered-eth-2lds/17576/1). - [undefined](/dao/proposals/5.28): This proposal aims to reimburse eth.limo for ongoing legal fees related to the operation of the eth.limo/eth.link gateway services. - [undefined](/dao/proposals/5.29): We are requesting funding from the ENS DAO to build a production network of gateways. These gateways will support the rollout of reverse resolution for **Arbitrum, Base, Linea, Optimism, and Scroll.** We also plan to continue our research and development on the ENS protocol and actively contribute to the ENS ecosystem with a focus on resolving names from L2s. Our funding request focuses on infrastructure, talent acquisition and retention, and ongoing development to sustain this critical ENS infrastructure. - [undefined](/dao/proposals/5.3): Since 2017, ENS Labs has been operating eth.link as a public gateway for the Ethereum community, providing access to ENS+IPFS sites. Eth.link has been used by some of the largest projects in the space, including Uniswap. - [undefined](/dao/proposals/5.4.1): The ENS Meta-Governance Working Group requests funding of the below to **support operations until the September 2024 funding window**. - [undefined](/dao/proposals/5.4.2): The ENS Public Goods Working Group requests funding of the below to **support operations until the September 2024 funding window**. - [undefined](/dao/proposals/5.5): The ENS Public Goods Working Group requests funding to **support operations until the September 2024 funding window**. - [undefined](/dao/proposals/5.6): Authorizes metagov to withdraw 30 ETH from the endowment each month for fees, and reimburses metagov for 43.54 ETH in fees already incurred. - [undefined](/dao/proposals/5.7): The primary mission of ENS DAO is to govern the protocol and allocate resources from the treasury in line with the DAO's constitution and broader objectives. However, due to changing economic dynamics, the DAO is increasingly vulnerable to attacks aimed at draining its treasury. - [undefined](/dao/proposals/5.8): Following discussion in the Metagov funding request thread and feedback on the Temp Check Proposal, we have put together this amendment proposal which looks to add the requirement of vesting to ENS distributions to stewards for the current term. - [undefined](/dao/proposals/5.9): In March 2024, The ENS Metagov funding request for Q1/Q2 failed to gain the support needed to pass.\ The ENS Meta-Governance Working Group is now using the June 2024 funding window to request the Q1/Q2 funding to cover operations until the next funding window in September 2024. - [undefined](/dao/proposals/6.1): We propose to convert 6,000 ETH into USDC to replenish the USDC reserves in the [DAO's treasury](https://etherscan.io/address/0xfe89cc7abb2c4183683ab71653c4cdc9b02d44b7). - [undefined](/dao/proposals/6.10): This vote will select the Service Providers for the next installment of the program, as approved in [EP 6.3](https://discuss.ens.domains/t/ep-6-3-social-renew-service-provider-budget/20272) and [EP 6.5](https://discuss.ens.domains/t/6-5-amendment-metagovs-facilitation-plan-for-spp2/20638). - [undefined](/dao/proposals/6.11): This proposal executes funding requests for the Meta-Governance and Public Goods Working Groups for the April 2025 funding window as passed in [EP 6.6.1](https://discuss.ens.domains/t/6-6-1-social-april-funding-request-ens-meta-governance-working-group-term-6/20536) and [EP 6.6.2](https://discuss.ens.domains/t/6-6-2-social-april-funding-request-ens-public-goods-working-group-term-6/20532). This bundled executable proposal follows the requirements set out in Rule 10.1 of the Working Group Rules ([EP 1.8](https://docs.ens.domains/dao/proposals/1.8/)). - [undefined](/dao/proposals/6.12): [EP6.7](https://discuss.ens.domains/t/ep-6-7-executable-transfer-ceo-tld-to-the-dnssec-registrar/20594) reconfigured the .ceo TLD, setting the owner record to the DNSSEC registrar contract. This allowed onchain claiming of .ceo 2LDs to resume, reclaiming control from a custom registrar that had been set by a previous owner of .ceo. - [undefined](/dao/proposals/6.13): The previous version of this proposal has incorrect text in the description. This version is corrected. - [undefined](/dao/proposals/6.14): This social proposal seeks to authorize the formation of the **OpenBox Investment Committee,** a temporary committee tasked with evaluating a potential $5 million equity investment by the ENS DAO into OpenBox Inc. The proposal does **not** commit the DAO to any investment. Instead, it empowers a select group—including ENS Foundation directors, DAO delegates, and an ENS Labs observer—to conduct due diligence, assess the proposal, and deliver a formal recommendation to the DAO. - [undefined](/dao/proposals/6.15): Tally proposes a formal enterprise level service agreement that elevates ENS governance UX, broadens the distribution of ENS primitives across all governance users on Tally, and furnishes the DAO with battle-tested uptime, reporting, and support guarantees. This proposal formalises a service agreement that ensures the DAO can hold us to explicit uptime and delivery standards. - [undefined](/dao/proposals/6.16): This proposal enables five chain-specific reverse resolvers for L2 EVM networks, and one default reverse resolver as a fallback mechanism. The five chains are Arbitrum, Base, Linea, OP Mainnet and Scroll. - [Abstract](/dao/proposals/6.16): This proposal enables five chain-specific reverse resolvers for L2 EVM networks, and one default reverse resolver as a fallback mechanism. The five chains are Arbitrum, Base, Linea, OP Mainnet and Scroll. - [Motivation](/dao/proposals/6.16): The current implementation of reverse resolution is limited to Ethereum Mainnet and assumes that every entity (a generic smart contract or user account) has the same address across every EVM chain. This has been falling out of line with reality given the rise in smart contract accounts, indicating that reverse resolution should be resolved via a namespace for each chain, rather than a single reverse namespace for the Ethereum ecosystem at large. - [Specification](/dao/proposals/6.16): Batch transaction for ENS DAO execution - [undefined](/dao/proposals/6.17): Orange Domains LLC is requesting the transfer of ownership of the “locker” Top Level Domain (TLD) in the ENS ecosystem. As the ICANN-accredited registry operator of the .locker TLD and controller of the .locker namespace on the Bitcoin Naming System (BNS), Orange Domains operates a comprehensive Web2-to-Web3 bridge that launched in general availability on October 23rd, 2024. - [undefined](/dao/proposals/6.18): This proposal reactivates the Service Provider Program Season 2 (SPP2) streams that were interrupted due to a failure in Superfluid’s autowrap system. The issue has been resolved, and Superfluid has committed to covering any liquidation fees incurred by providers during the interruption. This proposal resumes the original payment streams approved in EP 6.3 and EP 6.10, including retroactive funding for the downtime. - [undefined](/dao/proposals/6.19): This proposal outlines ENS’s adoption of the SEAL ([Security Alliance](https://www.securityalliance.org/)) Whitehat Safe Harbor Agreement (“Safe Harbor Agreement”). By adopting the Safe Harbor Agreement, ENS improves the security of its on-chain assets by allowing whitehats to intervene during active exploits to save protocol funds. - [undefined](/dao/proposals/6.2): This proposal aims to expand the Endowment by funding a third tranche, comprising 5,000 ETH, from the ENS DAO to the ENS Endowment. - [undefined](/dao/proposals/6.20): [Temp Check Discourse link](https://discuss.ens.domains/t/temp-check-reimbursement-for-eth-limo-s-legal-fees/21435) - [undefined](/dao/proposals/6.21): Several ENS DAO contracts lack primary names. This proposal establishes reverse records for core DAO addresses. - [undefined](/dao/proposals/6.22): *After positive discussion, feedback and support on the forum, we now move this proposal to a vote.* - [undefined](/dao/proposals/6.23): This proposal introduces updated permissions for the Endowment, with a continued focus on diversification and alignment with the evolving market landscape and liquidity. - [Abstract](/dao/proposals/6.23): This proposal introduces updated permissions for the Endowment, with a continued focus on diversification and alignment with the evolving market landscape and liquidity. - [Motivation](/dao/proposals/6.23): The proposed new permissions focus on strategies involving: - [Specification](/dao/proposals/6.23): Airdrop claim: Claim the SPK airdrop and add permissions to swap the SPK token - [Zodiac Roles Modifier Permissions Policy](/dao/proposals/6.23): Airdrop claim: Claim the SPK airdrop and add permissions to swap the SPK token - [undefined](/dao/proposals/6.24.1): The Meta-Governance Working Group is responsible for providing governance oversight and supporting the management and operation of working groups through DAO tooling and governance initiatives as well as treasury management for the DAO. - [Success Criteria](/dao/proposals/6.24.1): For this social proposal to pass, the following quorum and voting requirements must be met: - [undefined](/dao/proposals/6.24.2): The ENS Ecosystem Working Group requests funding of 470,000 USDC to support operations through April 2026. This is the only funding request of Term 6. - [Success Criteria](/dao/proposals/6.24.2): For this social proposal to pass, the following quorum and voting requirements must be met: - [undefined](/dao/proposals/6.24.3): The Public Goods Working Group exists to fund initiatives that advance public goods funding within the wider ecosystem. We support builders, stewards, and community members working on public goods that are aligned with the values and goals of ENS. - [Success Criteria](/dao/proposals/6.24.3): [Remix & Fabric](https://discuss.ens.domains/t/ens-public-goods-working-group-funding-remix-labs-fabric/20866/2) - [undefined](/dao/proposals/6.25): This proposal calls for winding down the Meta-Governance, Ecosystem, and Public Goods Working Groups at the end of Term 6 (Dec 31, 2025) and the creation of the ENS Admin Panel on Jan 1, 2026. - [undefined](/dao/proposals/6.26): DAOs have had almost a decade of history, during which there have been very few retrospective reviews of DAO treasury spend. This proposal aims to bring more accountability to the DAO’s spending, developing clear and measurable datapoints that the DAO can use to continue to build its processes and decision making mechanisms. - [Summary](/dao/proposals/6.26): DAOs have had almost a decade of history, during which there have been very few retrospective reviews of DAO treasury spend. This proposal aims to bring more accountability to the DAO’s spending, developing clear and measurable datapoints that the DAO can use to continue to build its processes and decision making mechanisms. - [Motivation](/dao/proposals/6.26): ENS DAO has grown significantly since its launch in 2021, supported by a wide range of contributors, funded initiatives, working groups, and service providers. While the high-level success of ENS is objective and clear, the DAO lacks some elements of structure and accountability. DAOs have already made immense impact on the growth and opportunity within Ethereum and we see this proposal as a way to continue improving these structures. The motivation of this proposal is to examine ENS DAO’s purpose, practices, desired outcomes, spending, outputs, and outcomes. - [Timeline & Contributors](/dao/proposals/6.26): What has been funded - What has not - [Request for Working Group Steward Term Extension](/dao/proposals/6.26): What has been funded - What has not - [Budget Requirements](/dao/proposals/6.26): What has been funded - What has not - [Specification](/dao/proposals/6.26): What has been funded - What has not - [Conclusion](/dao/proposals/6.26): What has been funded - What has not - [undefined](/dao/proposals/6.27): This proposal introduces a routine update to the permissions for the Endowment Manager. These updates continue to evolve diversification to lending markets. This update also removes a permission no longer needed. - [undefined](/dao/proposals/6.3): The Service Provider's streams were initiated almost exactly a year ago, and while it's approved for 18 months, it is supposed to be a program reevaluated yearly. Here is the proposed format for this year. This vote intends to be a DAO check on whether to renew the program and if so, under what budget. - [undefined](/dao/proposals/6.4): EP 6.3 was passed with a budget of $4.5M for 2025 on the 25th of February and pertains to Service Provider budgets and allocation mechanisms for 2025. After broad discussion between delegates, working groups and service providers, a proposed change to the voting process is now being presented for vote. - [undefined](/dao/proposals/6.5): Season 2 of the Service Provider Program was approved with a $4.5M budget on February 25th of this year. During the Delegate All Hands meeting on April 1st, delegates expressed a desire for more granular voting — not only to approve candidates, but also to vote on individual budget allocations. - [undefined](/dao/proposals/6.6.1): The Meta-Governance Working Group is responsible for providing governance oversight and supporting the management and operation of working groups through DAO tooling and governance initiatives as well as treasury management for the DAO. - [undefined](/dao/proposals/6.6.2): *This is an updated budget for this funding window to account for better treasury management at this time - a new funding request may be put forward in the October window which was not initially planned when scoping out this budget* - [Abstract](/dao/proposals/6.6.2): The Public Goods Working Group exists to fund initiatives that advance public goods funding within the wider ecosystem. We support builders, stewards, and community members working on public goods that are aligned with the values and goals of ENS. - [Specification](/dao/proposals/6.6.2): This specification is the amount requested from the DAO treasury to the Public Goods Multisig to fulfill anticipated budgetary needs through the next formal funding window in October 2025. - [Description](/dao/proposals/6.6.2): Current Public Goods Wallet Balances as of April 2, 2025 - [Expenditures](/dao/proposals/6.6.2): The Public Goods Working Group allocates funds to support the public goods ecosystem through strategic grants, builder grants, and discretionary initiatives. While we aim to estimate expenditures accurately, actual spending may shift based on new opportunities or unforeseen needs. - [Description of Initiatives](/dao/proposals/6.6.2): **1. Strategic Grants:** High-impact funding for initiatives aligned with the long-term vision of ENS and the broader public goods ecosystem. We are working on developing strategic initiatives focused on foundational infrastructure alongside our existing grants. - [undefined](/dao/proposals/6.7): The .ceo TLD, formerly owned by Kred Pty, has since been acquired by XYZ. Prior to the formation of the DAO, the previous owner asked for .ceo to be delegated to a custom address so they can manage a bespoke DNS integration. The new owner has requested that this change be undone, and that ownership of .ceo be reverted to the DNSSEC registrar so owners of .ceo TLDs can use the standard integration to claim their names on ENS. - [undefined](/dao/proposals/6.9): We have identified that the legacy ENS multisig, which originally controlled ENS before the DAO was created, still has the 'controller' role on the ENS root. This means that a majority of multisig keyholders could create or replace any ENS TLD other than .eth. .eth is locked and cannot be modified by the DAO or anyone else. - [Process of Submitting a Proposal](/dao/proposals/submit): There are three main types of governance proposals you can make: - [Moderator Checklists](/dao/governance/moderator): Process documentation and checklists for DAO moderators handling proposals - [Governance Process](/dao/governance/process): An overview of the ENS DAO's governance processes, and how you can get involved - [Smart Contracts](/contracts): The Ethereum Name Service is made up of a set of smart contracts. These smart contracts are responsible for storing and managing information associated with names. - [ENSv2 Smart Contracts Overview](/contracts/ensv2/overview): Welcome to the next evolution of the Ethereum Name Service!