Summary

This proposal recommends consolidating legacy multisig accounts into a simplified six-Safe structure, this is a follow-on proposal from TIP-52. The aim is to simplify the multisig structure and ensure each is aligned to a core financial function of Treasure DAO. The goal is to bring clarity, operational efficiency, and structure to how funds are allocated, managed, and reported. Multisigs will be deployed on Ethereum Mainnet and if/when Treasure goes multi-chain, these multisigs will also be deployed on these chains under the same address where appropriate.

Proposed Six-Safe Structure

Safe Name Purpose Treasury Core DAO reserves and long-term capital management Ecosystem Fund Ecosystem growth, strategic investments, and partner initiatives Contributor Contributor vesting compensation and grants Operations Routine expenses across DAO functions (infrastructure, tooling, Payroll etc.) Revenue Revenue flows generated from existing marketplace activity and future revenue activities Liquidation Fund Capital set aside for managing runway, covering downside scenarios, and backstopping protocol risks

Motivation

Over time, Treasure DAO created multiple function-specific multisigs to support operational decentralization. While effective early on, this structure has become overly complex and administratively burdensome. By consolidating into six clearly defined buckets, the DAO can:

• Simplify fund allocation and tracking
• Improve permission management and reporting
• Enhance accountability and strategic budgeting

Safes to be Consolidated

Existing Safe Destination Safe Treasury Treasury DA Staking Ecosystem Fund Liquidity Treasury Community Grants Treasury Smol Treasury Treasury Operations Operations Marketplace Revenue GBS Treasury Treasury Bridgeworld Treasury Magicswap Treasury Mage Treasury *It should be noted that some of these multi-sigs still have funds on arbitrum, wewill actively be bridging these assets back to mainnet in order to consolidate operations.

Safes Not Consolidated

Safe Name Rationale Ecosystem Fund Retained as a standalone Safe for funding strategic ecosystem initiatives Contributor Maintained for contributor vesting Liquidation Fund Newly created safe dedicated to liquidation of Treasure if the business becomes no longer viable

Change to Status Quo

Treasure DAO currently maintains 11 safes for organizational purposes. Over time, this structure has become unwieldy and inefficient. Each time a contributor departs, a significant amount of time is spent updating multisigs and internal documentation—time that could be better spent on development and operations. In many cases, multisigs were created for programs that are now inactive or effectively retired. For example, neither Community Grants nor DA Staking are currently relevant. This outdated structure makes it harder to present an accurate picture of the DAO’s available MAGIC or USDC reserves to the community. The onboarding process for new administrators has also become increasingly burdensome, requiring a deep understanding of legacy initiatives just to navigate the current treasury architecture. Ironically, while the original intent behind separating funds was to improve transparency and accountability, the result has been the opposite: the complex web of accounts has made it more difficult for the community to clearly understand the DAO’s financial state. We propose a simpler, more intuitive approach: business units or verticals will continue to be tracked and reported independently, but the DAO will retain just six core multisigs — Treasury, Ecosystem Fund, Contributor, Operations, Revenue, and Liquidation Fund.

• Treasury provides a clear view of core DAO reserves. Stablecoins in this account serve as the most accurate representation of the DAO’s operational runway, whereas MAGIC is too volatile for such projections.
• Ecosystem Fund holds MAGIC intended for DAO growth. With the sunset of game and chain publishing, unused funds from past programs like community grants and DA incentives will be returned here for future use.
• Contributor funds remain allocated to active vesting agreements and should not be repurposed for new initiatives.
• Operations serves as the DAO’s working capital account, typically holding three months’ worth of expected expenses. It enables smooth execution of payments across DAO functions without tapping directly into long-term reserves.
• Revenue should remain consolidated. Although DAO revenue streams (e.g., agent upgrades, marketplace royalties, compute costs) are diverse, managing them through a single account allows for efficient reporting and partner payouts, avoiding unnecessary complexity.
• Liquidation Fund In the event that treasure DAO is no longer a going concern, this will be used to wind down operations.

Implementation Plan

Categorization & Internal Audit

• Confirm balances, signer roles, and obligations across all source safes
• Finalize funding flow mappings per the table above

Transfer of Assets

• Move assets to their designated destination safes with transparent, verifiable transactions

Sunsetting Old Safes

• Signers will remain on these safes but will not be used to hold any funds — effectively deprecated multisigs
• Maintain view-only access for historical record-keeping

Reporting & Communications

• Publish a treasury architecture overview post-migration
• Detail each safe’s role, funding source, and reporting cadence

Benefits

• Streamlined fund architecture aligned with DAO’s future scale
• Greater transparency and ease of financial reporting
• Clear accountability by functional area
• Operational simplicity without sacrificing control

Next Steps

• Governance vote via Snapshot immediately
• Execution of transfers by relevant signers

Conclusion

This consolidation reflects a natural progression in Treasure DAO’s maturation — reducing complexity and aligning treasury infrastructure with strategic planning needs. It lays the foundation for an upgraded tokenomics model, improved accountability, and long-term sustainability across all DAO initiatives.

Author: Elliott (Regen Financial)