Logo
    Logo
    XDiscordGitHub
    πŸ€–

    Executable Proposals

    Getting started

    About ENSAbout ENSπŸ—³οΈ$ENS Token🎨ContractsπŸ’΅Protocol Revenue🐒ENS FoundationπŸ“–ENS DAO ConstitutionπŸ“ˆENS EndowmentπŸ›‘οΈENS DAO Security Council

    Voting

    βœ…Voting🀝Delegating $ENS🍿Governance Environments

    Proposals

    πŸ’‘ProposalsπŸ’¬Social ProposalsπŸ€–Executable ProposalsπŸ’°Funding Requests

    Working Groups

    πŸ’ΌWorking GroupsπŸ”¨Meta-Governance WG🌱ENS Ecosystem WGπŸ”†Public Goods WG

    Useful Information

    🌐LinksπŸ§ͺENS LabsπŸ‘‹SIWEπŸ§‘β€πŸš€CCIP-Read 🧭Sitemap
    β€£
    Proposals > Executable Proposals

    Executable Proposals

    Passed on-chain, Executable Proposals execute code related to ENS and ENS DAO contracts, as voted on by the DAO

    Overview

    Executable Proposals can be passed by the DAO to enact a range of smart contract operations executed by accounts controlled by the ENS DAO.

    Examples of past Executable Proposals include:

    • distributing funding to Working Group multisig wallets
    • ending the $ENS airdrop and sweeping remaining tokens to the DAO wallet
    • changing temporary premium price on ENS name registrations

    An Executable Proposal is an on-chain proposal. In order to cast a vote, a delegate must sign a transaction on the Ethereum blockchain, which costs gas. Once a delegate has voted on a proposal, the vote cannot be changed.

    Proposers are solely responsible for the submission of a proposal. No other person is obligated to help or assist in any way.

    Process

    Executable Proposals can be submitted by any delegate controlling an Ethereum address with 100,000 or more delegated $ENS votes.

    The current governance process advises that proposals are submitted to the governance forum for discussion before being advanced to a vote. This gives delegates and the broader community a chance to provide feedback and guidance on an idea.

    Following an initial feedback period, the proposal may be advanced to a draft proposal on the governance forum.

    Once the proposer is satisfied that the proposal is in its final form, it can be advanced to a vote as an active proposal

    Proposal Threshold

    An address must be delegated 100,000 or more $ENS in order to propose an Executable Proposal.

    Format

    This template can be followed when drafting Executable Proposals in the governance forum. Please see this proposal as an example of a correctly formatted executable proposal.

    A popular platform for drafting proposals is HackMD, which gives you the ability to copy markdown from HackMD across many platforms, such as Discourse and Github, without affecting the formatting.

    Numbering

    Before advancing an Executable Proposal from draft to active, the proposal should be assigned an EP number.

    The EP numbering system follows working group terms.

    For example, proposals submitted during Q1/Q2 2023 started with a β€œ3” while proposals submitted during Q3/Q4 2023 started with a β€œ4”. The first proposal in term 3 was EP3.1, the second proposal in term 3 was EP3.2, etc.

    The best practice is to look at the sidebar on this page to determine the latest EP number.

    Drafting

    A popular platform for drafting proposals is HackMD, which gives you the ability to copy markdown from HackMD across many platforms, such as Discourse and Github, without affecting the formatting.

    Example of an Executable Proposal drafted with HackMD
    Example of an Executable Proposal drafted with HackMD

    Testing

    If an Executable Proposal is passed, there is nothing that can be done to stop the execution prescribed in the proposal.

    πŸ‰
    It is ⚠️STRONGLY⚠️ recommended that, where possible, all code related to Executable Proposals is simulated using Tenderly prior to a proposal being submitted.

    If you need help testing code for a proposal, please reach out to a Meta-Governance Steward for help.

    Location

    Executable Proposals can be submitted on-chain and voted on using vote.ensdao.org, or other decentralized governance platforms. Once a proposal has received feedback in the forum, the last step is to submit the proposal to a vote.

    View Executable Proposals for ENS DAO on
    View Executable Proposals for ENS DAO on vote.ensdao.org

    Voting method

    Executable Proposals are on-chain.

    Delegates may vote yes, no, or abstain on a proposal.

    To cast a vote, you need to sign a transaction which is committed to the Ethereum blockchain. This transaction costs gas.

    Timing

    Executable Proposals have a voting period of 7 calendar days.

    There is a 2-day time-lock period at the end of the voting period before a successful Executable Proposal is executed.

    Example of vote timing for EP 16
    Example of vote timing for EP 16

    Quorum

    An Executable Proposal will pass if 1% of the total supply of $ENS (1m votes) votes in favor of the proposal.

    Record keeping

    You can find a history of Social Proposals on Github, which is the source of truth for the ENS Governance Docs site.

    All proposals can be found in the ENS Governance Docs.
    All proposals can be found in the ENS Governance Docs.

    ← Previous

    Social Proposals

    Next β†’

    Funding Requests

    ---
    description: A short (1-2 sentence) description of the proposal.
    ---
    
    # [Executable] Proposal Title
    
    | **Status**            | Pending                                                                                                                                   
    | **Discussion Thread** | [Discuss](https://discuss.ens.domains/t/...)                                                                                                
    | **Votes**             | Pending                                                                                                                                  
    
    # Abstract
    <!--
      Abstract is a multi-sentence (short paragraph) summary.
      This should be a very terse and human-readable version of the specification section. Someone should be able to read only the abstract
      to get the gist of what this proposal does.
    -->
    
    # Specification
    <!-- The specification should describe the proposal in detail. The specification should be detailed enough to cover all the details of the proposal. -->
    
    # Transactions
    <!-- The transactions section describes all the calls that should be encoded in the onchain version of this proposal. Use the table below as a starting point. -->