Initial Developer DAO Treasury Setup
One of the Core Teams objectives as defined in our Season 0 proposal was to deploy the DAO Treasury. This document provides details on how we’ve set this up.
Overview
Our Treasury has been deployed as a “multisig” contract wallet via gnosis safe with a 6/3 threshold. That means, out of the 6 signers listed below, 3 will need to sign any transaction for funds to leave the treasury.
Initial signers of the treasury multisig:
- Nader Dabit - @dabit3
- Will Kempsterrrr - @kempsterrrr
- marc - @wolovim
- Will Blackburn - @willhblackburn
- with-heart - @grow_love
- Erik_Knobl - @Erik_Knobl
This initial set of signers will serve for Season 0 and Season 1. This will provide stability and allow time during Season 0 for our community to stand up Governance processes and our new ERC-20 Governance token to be launched. Once these are in place, token holders will then vote to either keep or replace the existing signers.
We also maintain a legacy EOA wallet for specific use cases listed below. The same signers have access to both wallets.
Treasury address - 0x7128f5ff32eD07Ce12E6a9deBE32BB40F9884b3C
EAO wallet address - 0xdd00Cc906B93419814443Bb913949d503B3DF3c4
Management of funds
The Treasury stores the vast majority of DAO assets.
This includes but is not limited to any vested allocations of our ERC-20 Governance token once launched, revenue from on-chain activities and tokens received in partnership arrangements.
The only current exception to this is management for our ENS domain (devdao.eth) and a small amount of “working capital” provided by the core team which is stored in the EOA wallet. The reason for this is to provide easy management for mirror and snapshot, as well as voting as an ENS delegate.
Whilst there are no current plans to actively manage Treasury assets, we expect to open up discussions about this as the Treasury grows.
Governance of the Treasury
Decentralised and transparent Governance of the Treasury is key to ensuring trust in our community.
To that end, whilst each individual transaction does not require a vote, budgets must be pre-approved by DAO members via a snapshot vote. A record of transactions that ties them back to an approved budget will be made publicly available and can be verified on-chain via etherscan.
Governance and management of the Treasury will become more decentralized over time as our governance process and tooling matures. For now this set-up provides the ability to move forward whilst ensuring oversight from the community.