Move treasury logic to a separate contract to allow DAO upgrades (soft fork support) #47
Description
Is your feature request related to a problem
Right now, the treasury (DAO funds) is tightly coupled with the main DAO contract. This architecture makes it hard or even impossible to upgrade the DAO logic (e.g. voting mechanism, execution engine) without redeploying the entire contract — which would require a hard fork, migration of all assets, and loss of on-chain history.
Describe the solution you'd like
Refactor the DAO architecture to separate concerns:
- Deploy a dedicated
Treasurycontract, responsible solely for holding and transferring funds. - The main
DAOcontract becomes the controller and can be upgraded without affecting the treasury balance. - The treasury should verify that fund-transfer requests are authorized by Skipper
This allows:
- Soft forks and modular governance upgrades
- Better auditability and simpler reasoning
- Safer long-term fund storage
Describe alternatives you've considered
No response
Additional context
No response