📌 Term 6 Proposal Bulletin

October 2025

Executable Proposals:

  1. [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
  2. [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
  3. [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
  4. [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:

  1. [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.

  2. [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.

  3. [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