Term 6 Proposal Bulletin
About the Proposal Bulletin
The Proposal Bulletin provides updates on recent ENS DAO proposals. Its primary objective is to inform community members about the nature, status, and outcomes of both social and executable proposals under consideration or recently concluded.
By consolidating this information, the bulletin aims to enhance transparency and ensure stakeholders remain informed about governance activities.
About Proposals
Proposals serve as the mechanism for implementing changes within the ENS DAO. There are two types of proposals:
- Social Proposals: Offchain proposals that seek the DAO’s agreement on social considerations that cannot be enforced onchain.
- Executable Proposals: Onchain proposals that execute code related to the ENS Protocol and ENS DAO smart contracts, as determined by DAO votes.
How to Submit a Proposal
The ENS DAO proposal process ensures structured, transparent decision-making. It consists of three phases:
- Temperature Check – An informal discussion on the Forum to gauge community interest.
- Draft Proposal – A draft proposal is created and refined with feedback from the ‘Temp Check’.
- Active Proposal – The proposal goes to either an offchain or onchain vote.
Anyone who meets the minimum threshold can submit a proposal directly. Alternatively, proposers may seek a sponsor. For full details, refer to the ENS Proposal Submission Guide and explore the ENS Agora Governance interface when preparing to submit a proposal.
Proposal Table
| Criteria |
Social Proposals |
Executable Proposals |
| Type of proposal |
Offchain |
Onchain |
| Location |
Snapshot |
Tally |
| Minimum threshold |
10,000 ENS |
100,000 ENS |
| Quorum |
≥ 1m $ENS, 50% Approval |
≥ 1m $ENS, 50% Approval (Votes ‘For’ + Abstain count towards quorum) |
| Voting period |
5 days |
7 days |
| Subject to time-lock? |
No |
Yes, 2-day timelock |
2 Likes
January 2025
Executable Proposals:
-
[6.1] [Executable] Convert 6,000 ETH to USDC for DAO Operating Expenses
The proposal suggests converting 6,000 ETH into USDC to replenish the ENS DAO’s USDC reserves, ensuring a 12-month operational runway for expenses such as payments to ENS Labs, Working Groups, and Service Providers.
- Vote: Tally
- Discussion: Open
- Call Data: View
- Action: Executed—view onchain results here.
-
[6.2] [Executable] Endowment Expansion (Third Tranche)
The proposal aims to transfer 5,000 ETH from the ENS DAO to the ENS Endowment to enhance financial self-sufficiency, and to adjust the ETH allowance reset time from 30 to 25 days to address payment delays.
- Vote: Tally
- Discussion: Open
- Call Data: View
- Action: Executed—view onchain results here.
Warning : Exercise caution when clicking external links, as they may be outdated, broken, or potentially compromised.
2 Likes
April 2025
Executable Proposals:
-
[6.7] [Executable] Transfer .ceo TLD to the DNSSEC registrar
This proposal transfers the .ceo top-level domain back to the DNSSEC registrar to enable standard ENS integration for .ceo domain holders.
- Vote: Tally
- Discussion: Open
- Call Data: View
- Action: .ceo TLD Control transferred to the DNSSEC registrar, enabling standard ENS integration for .ceo domain holders.
- Results: Dhive
-
[6.8] [Executable] Revoke root controller role from legacy ENS multisig
This proposal seeks to revoke the controller role from the legacy ENS multisig on the ENS root contract to prevent outdated keyholders from modifying top-level domains other than .eth, thereby enhancing security and aligning control with the ENS DAO.
- Vote: Tally
- Discussion: Open
- Call Data: View
- Action: Legacy ENS multisig’s controller permissions have been removed from the ENS root contract, ensuring only the DAO governs non-.eth TLDs going forward.
- Results: Dhive
-
[6.9] [Executable] Endowment permissions to karpatkey - Update #5)
This proposal introduces new permissions for deploying ENS DAO endowment funds into diversified assets—including USDT, real-world assets, and updated LST providers—while aligning with evolving market conditions and updating the Investment Policy Statement accordingly.
- Vote: Tally
- Discussion: Open
- Call Data: View
- Action: New permissions granted to karpatkey to diversify the ENS endowment.
- Results: Dhive
Social Proposals:
-
[6.4] [Social] SP Season 2 Vote Amendement
This proposal introduces ranked voting for Service Providers, letting voters choose between basic or extended budgets per team. It compares only a team’s own budget options and enforces adjacency in rankings to simplify Copeland-based allocation.
-
[6.5] [Social] SP Season 2 Vote Amendment II
This proposal enables voters to rank basic and extended budgets independently across all teams, allowing nuanced prioritization. It treats each budget option as a standalone candidate and aligns more closely with voter intent and UI display.
-
[6.6.1] [Social] April Funding Request - ENS Meta-Governance Working Group Term 6
This proposal requests funding to support the Meta-Governance Working Group through October 2025, allocating $589,000 USDC and 100,000 $ENS tokens to cover steward and secretary compensation, contract audits, DAO tooling, and governance initiatives—including a new program to reward delegates and delegators.
- Vote: Snapshot
- Discussion: Open
- Action: Approved for inclusion in the collective proposal during a subsequent funding window. View results here.
-
[6.6.2] [Social] April Funding Request - ENS Public Goods Working Group Term 6
This proposal requests $521,000 USDC to fund the Public Goods Working Group through October 2025, focusing on strategic grants, builder grants, and a discretionary buffer. The discretionary buffer is included to address emergent opportunities like hackathon sponsorships.
- Vote: Snapshot
- Discussion: Open
- Action: Approved for inclusion in the collective proposal during a subsequent funding window. View results here.
Special Note:
Both EP6.4 and EP6.5 aim to improve the voting process for the Service Providers Program by allowing more granular input on budgets. They emerged from extensive delegate and working group discussions following feedback during the April 1 All Hands meeting.
While similar in intent, they differ in how ballot preferences are interpreted, how budget types compete, and the degree of expressiveness allowed. EP6.4 bundles each team’s budget options together, while EP6.5 treats them as separate candidates for finer-grained prioritization.
How the vote will be resolved:
- If both proposals pass, the one with more votes will take effect.
- If only one passes, that proposal becomes the official amendment.
- If neither reaches a passing threshold, the current SPP process remains unchanged.
3 Likes
July 2025
Executable Proposals:
-
[EP 6.16] [Executable] Enable L2 Reverse Registrars and new .eth registrar controller
This proposal enables chain-specific reverse resolvers for five L2 EVM networks, sets a fallback default resolver, introduces a new .eth registrar controller with a referrer field, and assigns reverse records to certain ENS contracts to support L2 primary names and improve registration workflows.
- Vote: Tally
- Discussion: Open
- Action: Deploys L2-specific reverse resolvers, a default fallback resolver, a new .eth registrar controller with referral support, and updated reverse records
- Status: Queued
- Call Data: Github
Social Proposals:
-
[EP 6.15] [Social] Enhancing ENS Governance with Tally’s Enterprise Support
This proposal seeks a one-year, renewable enterprise agreement between Tally and the ENS DAO to deliver webhook notifications, deeper ENS integrations (including Namechain and offchain proposals), enhanced governance transparency, and enterprise-grade support with clear SLAs and milestone-based payments.
- Vote: Snapshot
- Discussion: Open
- Action: Approves a one-year enterprise agreement with Tally, with milestone-based payments
- Status: Rejected
- Pull Request: Github
—
Curious to learn more about how ENS DAO works? Check out the Term 6 Dashboard for a quick overview, and visit basics.ensdao.org for the full documentation.
October 2025
Executable Proposals:
- [Executable] Endowment permissions to karpatkey - Update #6
This proposal introduces updated permissions for the Endowment, with a continued focus on diversification and alignment with the evolving market landscape and liquidity.
- Vote: Tally
- Discussion: Open
- Action: Authorize karpatkey to claim SPK, expand Aave, Spark, Compound, Morpho, Balancer, Curve, and Convex LP and TWAP swap permissions, enable Origin OETH rebasing, and remove all USDM permissions.
- Status: Live
- Call Data: Github
- [Executable] Reimbursement for eth.limo’s Legal Fees
This proposal seeks to reimburse eth.limo 109,818.82 USDC from the ENS DAO treasury to cover ongoing legal fees incurred in operating the eth.limo/eth.link gateway services, ensuring continued reliable access to ENS-powered infrastructure.
- Vote: Agora
- Discussion: Open
- Action: Transfers 109,818.82 USDC from the ENS DAO treasury to ethdotlimo.eth to cover eth.limo’s ongoing legal fees.
- Status: Executed
- Call Data: Github
- [Executable] Set Primary Names for Core DAO Addresses
This proposal sets primary names for core DAO addresses, including the DAO wallet, the token contract, and the Endowment wallet. By setting reverse records for these core addresses, ENS DAO demonstrates best practices by fully using its own protocol—making contracts easier to identify and navigate, and enabling names to resolve on sites that list contracts, such as enswallets.xyz.
- Vote: Tally
- Discussion: Open
- Action: Sets primary names and reverse records for for ENS DAO contracts
- Status: Executed
- Call Data: Github
- [Executable] ENS Contract Naming Season
This proposal launches ENS Contract Naming Season, a six-month program led by ENScribe and the Temporary Contract Naming Pod—with a $75,000 USDC and 10,000 ENS budget—to incentivize and coordinate the adoption of ENS contract naming across major protocols, DAOs, and infrastructure projects through outreach, leaderboards, and naming incentives.
- Vote: Tally
- Discussion: Open
- Action: Empowers a dedicated pod to drive widespread ENS contract naming adoption.
- Status: Live
- Call Data: Github
Collective Proposal:
The purpose of the Collective Proposal is to coordinate funding requests from all working groups under the DAO into a single, executable proposal, ensuring transparency and consistency in how funds are allocated. According to Rule 10.1, Stewards of all working groups must collaborate to submit this Collective Proposal during designated Funding Windows (January, April, July, and October).
To be included, each group’s funding request must first pass as a Social Proposal within the same window:
-
[Social] Funding Request: ENS Meta-Governance Working Group Term 6
This proposal requests 379K USDC from the DAO treasury for the ENS Meta-Governance Working Group to fund operations through April 2026, covering compensation, contract audits, DAO tooling, and discretionary initiatives, ensuring governance continuity and DAO transparency.
-
[Social] Funding Request: ENS Ecosystem Working Group Term 6
This proposal requests 470K USDC from the DAO treasury for the ENS Ecosystem Working Group to fund operations through April 2026, supporting hackathons, grants, ecosystem support, bug bounties, and IRL events to strengthen ENS builders, tools, and community growth.
-
[Social] Funding Request: ENS Public Goods Working Group Term 6
This proposal requests 110K USDC and 15 ETH from the DAO treasury for the ENS Public Goods Working Group to fund strategic and builder grants through April 2026, supporting impactful public goods, developer tools, and ecosystem projects aligned with ENS’s long-term vision.
1 Like