by 0x8dd060ad7f867ad890490fd87657c1b7e63c622f (Jungle)
DAO Committee Deprecation & Replacement
Summary
We propose to deprecate the DAO Committee and migrate its execution-only duties to a lean 3-of-5 operational multisig that reflects ecosystem representation. This change preserves the Council’s approve/oversee role and enforces fund-scoped execution. Net effect: the DAO’s operating model becomes clearer, safer, and faster.
Abstract
The DAO Committee historically acted as an operational and governance-enactment body: executing transactions, paying grants, and coordinating treasury operations. With the discontinuation of the grants program and the creation of the DAO Council, the Committee’s scope has significantly diminished.
This proposal introduces a transition strategy that retires the DAO Committee in its current form while reassigning execution responsibilities to a hybrid multisig structure composed of trusted representatives from existing entities within the Decentraland ecosystem. The proposed multisig will consist of trusted representatives from the DAO Council, the Security Advisory Board (SAB), the Decentraland Foundation, and 1 former DAO Committee member, forming a balanced and technically competent 3-of-5 multisig structure.
Motivation
The DAO Committee was once central to Decentraland’s operations: managing grants, paying contributors, executing transactions, and acting as a safeguard to ensure community-approved proposals were responsibly enacted. However, this role has fundamentally changed.
-
Reduced Scope: With no grants program and significantly fewer operational transactions, the workload and responsibility no longer justify the current structure or its $2.4k USD in MANA/month compensation per member (3 members → roughly 9k a month).
-
Legacy Role: The Committee historically coordinated treasury-related execution to enact community-approved decisions. Going forward, the Council sets mandates and provides oversight; execution remains with the operational multisig as defined in this proposal.
The DAO’s evolution now requires a leaner, more transparent mechanism. Transitioning to a council-driven multisig mitigates these risks while ensuring operational continuity.
The new multisig model offers clear benefits:
-
Representation: Aligns execution with representatives from major stakeholder entities across the project.
-
Accountability: Authority is distributed, reducing risks of over-concentration.
-
Continuity: Retains one former Committee member to ensure workflow continuity and a smooth handover.
-
Cost Alignment: Updates compensation to reflect the reduced scope and new responsibilities.
Specification
-
Deprecation of the DAO Committee
-
Disband the Committee as an operational and decision-making body.
-
Transition its functions to the newly appointed multisig structure, while retaining the existing operational multisigs on both Ethereum and Polygon to ensure continuity.
-
-
Multisig Configuration
-
Structure: The multisig will operate as 3-of-5, retaining the existing operational multisigs on Ethereum and Polygon for continuity.
-
Designation: Signers will be appointed at the DAO Council’s discretion, following standard security practices, and may be rotated or replaced by the Council to maintain security and liveness.
-
Members will be designated as follows:
-
2 current DAO Council members
-
1 appointed SAB member
-
1 appointed Foundation representative
-
1 former DAO Committee member
-
-
-
Responsibilities:
- Execute all on-chain transactions required to enact:
(a) passed governance proposals, and
(b) Council-approved mandates (treasury management strategies, operational budgets, etc) - No policy-making power. The operational multisig does not approve plans or re-interpret mandates.
- Execute all on-chain transactions required to enact:
-
Signer Replacement Procedure
- In the event of resignation or removal, the DAO Council will appoint replacements through an internal vote.
-
Compensation
-
Multisig signer responsibilities can be divided into two categories:
-
Passive tasks: Infrequent actions such as authorizing transfers replenishing the operating wallets. These are on-demand responsibilities and do not require continuous involvement. For these roles, compensation will be limited to reimbursing any transaction fees incurred.
-
Active tasks: Ongoing operational actions such as executing monthly compensations and handling smaller recurring payments or operations. These require consistent engagement. To ensure continuity, one signer will be designated as the “operator” of the operating wallet, with a defined compensation to reflect the more active nature of this role.
This structure balances fairness, ensures costs are covered, and recognizes the difference between occasional signers and those taking on day-to-day operational duties.
-
-
Impacts
-
Operational Agility: Faster execution DAO mandated proposals and treasury transactions, reducing unnecessary delays and bottlenecks.
-
Balanced Authority: Distributes trust into trusted members across the DAO Council, SAB, Foundation, and former Committee member, avoiding over-concentration.
-
Continuity: Retains one former DAO Committee member for institutional knowledge.
-
Cost Alignment: Adjusts compensation to reflect reduced responsibilities, ensuring sustainability.
Implementation Pathway
Until completion of the handover, the current DAO Committee remains the executor of transactions from the DAO Treasury, under Council mandates. Upon completion, the new operational multisig assumes that execution role as specified.
-
DAO Committee Offboarding
-
Revoke existing DAO Committee signer permissions and replace them with newly designated signers.
-
Revoke remaining Committee permissions once the handover is complete.
-
Discontinue DAO Committee compensation.
-
-
Multisig Configuration
-
Implement designated representatives into the new 3-of-5 multisig.
-
Update documentation and signer records.
-
-
Public Announcement
- Publish the new structure, disclose signer addresses, and responsibilities on the DAO governance forum and official channels.
- FOR
- AGAINST
- Invalid question/options