Getting started
About ENS$ENS TokenContractsProtocol RevenueENS FoundationENS DAO ConstitutionENS EndowmentVoting
VotingDelegating $ENSGovernance EnvironmentsProposals
ProposalsSocial ProposalsExecutable ProposalsFunding RequestsWorking Groups
Working GroupsMeta-Governance WGENS Ecosystem WGPublic Goods WGUseful Information
LinksENS LabsSIWECCIP-Read SitemapExecutable 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 directly to Tally 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 on Tally.
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.
---
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. -->
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.
The first working group term took place in Q1/Q2 2022. Proposals submitted during this term start with a “1”.
The second working group term took place in Q3/Q4 2022. Proposals submitted during this term start with a “2”.
We are currently in the third working group term (Q1/Q2 2023). Proposals submitted during this term start with a “3”.
The best practice is to look at this page to determine the correct EP number.
For ease of reference, the first proposal in term 3, was EP3.1, the second proposal in term 3 was EP3.2 etc. Contact nick.eth if you need help numbering or formatting your proposal.
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.
Testing
If an Executable Proposal is passed, there is nothing that can be done to stop the execution prescribed in the proposal.
If you need help testing code for a proposal, please reach out to a Meta-Governance Steward, or alisha.eth for help.
Location
Executable Proposals are submitted on-chain and voted on using Tally. Once a proposal has received feedback in the forum, the last step is to submit the proposal to a vote on Tally.
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.
Proposals should be added to the ENS Calendar when they are scheduled.
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 Executable Proposals on Github, which is the source of truth for the ENS Governance Docs site.
← Previous
Next →