This document defines the rules governing the ENS DAO Coordination Layer (“Coordination Layer”).
These rules are intended to replace the existing ENS DAO Working Group Rules for the duration of the Coordination Layer pilot period approved by governance.
The Coordination Layer exists to provide bounded operational coordination, governance support, contributor coordination, and DAO-facing operational execution on behalf of ENS DAO.
The Coordination Layer is not ENS DAO governance itself, nor does it supersede the ENS DAO Constitution, executable governance proposals, or broader delegate authority.
These rules should be considered subordinate to the ENS DAO Constitution and any passed governance proposals.
1.1. The DAO Coordination Layer (“Coordination Layer”) shall exist as a singular DAO operational coordination structure established by Social Proposal.
1.2. The Coordination Layer shall replace the existing ENS DAO Working Group structure for the duration of the approved pilot period.
1.3. The Coordination Layer shall operate as a bounded operational coordination body responsible for DAO-facing operational responsibilities delegated to it by ENS DAO governance.
1.4. The Coordination Layer is not a Working Group as previously defined under the ENS DAO Working Group Rules.
1.5. The Coordination Layer shall operate subject to:
- ENS DAO governance,
- the ENS DAO Constitution,
- transparency obligations,
- timelock requirements,
- veto mechanisms,
- and these rules.
2.1. The Coordination Layer shall initially operate for a pilot period of twelve (12) calendar months commencing June 1st 2026.
2.2. Prior to the conclusion of the pilot period, the Coordination Layer shall publish a retrospective report evaluating:
- operational effectiveness,
- governance coordination outcomes,
- contributor engagement,
- initiatives undertaken,
- financial activity,
- and recommendations for continuation, modification, expansion, or dissolution.
2.3. ENS DAO governance may:
- extend,
- modify,
- replace,
- or dissolve the Coordination Layer at any time through Social Proposal.
3.1. The Coordination Layer shall initially consist of two elected members (“Members”).
3.2. Members are responsible for:
- operational coordination,
- governance coordination,
- contributor coordination,
- ecosystem-facing DAO initiatives,
- administrative execution,
- and management of Coordination Layer responsibilities.
3.3. Members serve on behalf of ENS DAO and are expected to act in good faith and in accordance with the ENS DAO Constitution.
3.4. Members are required to publicly disclose relevant conflicts of interest.
3.5. Members may voluntarily recuse themselves from decisions where material conflicts exist.
3.6. Members may resign at any time through public notice posted to the ENS governance forum.
3.7. ENS DAO governance may remove Members through Social Proposal.
4.1. The Coordination Layer is responsible for DAO-facing operational coordination activities including, but not limited to:
- governance coordination,
- proposal process support,
- contributor onboarding,
- ecosystem coordination,
- operational execution,
- governance communication,
- DAO operational administration,
- and coordination of DAO-facing initiatives.
4.2. The Coordination Layer may establish temporary initiatives, committees, contributor groups, or operational programs where reasonably required to advance ENS DAO operational objectives.
4.3. The Coordination Layer may allocate discretionary operational funding within its approved budget subject to these rules.
4.4. The Coordination Layer shall not:
- supersede ENS DAO governance,
- override passed governance proposals,
- directly oversee ENS Labs,
- directly manage Service Provider Program funding decisions delegated to the SPP committee,
- or represent itself as ENS DAO governance itself.
5.1. The Coordination Layer may receive funding from ENS DAO governance through executable proposal.
5.2. Funding allocated to the Coordination Layer shall be held within a designated Coordination Layer multisig wallet (“Coordination Layer Multisig”).
5.3. Coordination Layer funds may be used for:
- contributor support,
- ecosystem initiatives,
- operational expenses,
- grants,
- governance tooling,
- experimentation,
- communications,
- coordination initiatives,
- and other DAO-facing operational responsibilities within scope.
5.4. Coordination Layer funds shall not be used for purposes outside the scope defined in these rules.
6.1. The Coordination Layer Multisig shall initially consist of the two Coordination Layer Members.
6.2. Additional signers may be added through governance proposal or amendment to these rules.
6.3. All transfers executed from the Coordination Layer Multisig shall be subject to a mandatory seven (7) day timelock.
6.4. All proposed outgoings must:
- be documented publicly,
- include sufficient operational rationale,
- disclose any relevant conflicts of interest,
- and remain publicly visible throughout the timelock period.
7.1. A veto mechanism shall exist for the purpose of preventing clearly inappropriate, malicious, or contested outgoing transactions during the timelock period.
7.2. The exact operational implementation of the veto mechanism may be defined separately through governance-approved operational procedures.
7.3. The ENS Security Council may act as the emergency veto executor during the pilot period.
7.4. The Security Council shall not oversee routine operations or governance decisions of the Coordination Layer and shall only act in relation to emergency veto execution.
7.5. If a valid veto action is executed during the timelock window, the associated outgoing transaction shall not proceed.
8.1. The Coordination Layer must maintain a public GitHub repository documenting:
- outgoing transactions,
- operational initiatives,
- contributor funding,
- active initiatives,
- meeting summaries,
- and operational documentation.
8.2. The Coordination Layer must publish monthly transparency reports outlining:
- funding allocations,
- contributor engagement,
- initiatives undertaken,
- operational progress,
- ongoing responsibilities,
- and notable operational concerns or failures.
8.3. Monthly transparency reports must include a self-evaluation section outlining:
- initiatives started,
- initiatives completed,
- initiatives paused or abandoned,
- operational bottlenecks,
- governance coordination issues,
- and areas where meaningful progress has not been achieved.
8.4. Transparency reports must be published publicly on the ENS governance forum.
9.1. The Coordination Layer shall facilitate regular public coordination calls.
9.2. These calls should:
- provide accessible entry points into DAO coordination,
- facilitate discussion of DAO initiatives,
- coordinate contributors,
- and improve visibility into ongoing operational work.
9.3. Outcomes and actions resulting from coordination calls should be documented publicly where practical.
10.1. Coordination Layer Members must publish up-front conflict of interest disclosures.
10.2. Members must disclose transaction-specific conflicts where applicable.
10.3. Members should recuse themselves from operational decisions where a material conflict exists.
10.4. The Coordination Layer may propose additional Conflict of Interest standards or operational procedures for ENS DAO governance consideration.
11.1. These rules may be amended through Social Proposal.
11.2. Any amendment proposal should clearly document:
- proposed changes,
- rationale,
- operational implications,
- and affected sections.
12.1. The Coordination Layer may be dissolved through Social Proposal.
12.2. Upon dissolution:
- all unspent funds must be returned to the ENS DAO treasury,
- active initiatives should be documented publicly,
- and a final operational report must be published.
12.3. Dissolution of the Coordination Layer does not automatically reinstate the previous Working Group structure unless separately approved through governance proposal.