Abstract
This proposal aims to optimize the DAO’s financial management by scaling down operations, discontinuing outdated reward programs, and utilizing $CU to address financial obligations. These measures are intended to ensure the continued functioning of the DAO’s core operations.
Motivation
As the Laguna Games team steps down as the primary developer within the ecosystem, it has become imperative for the DAO to streamline its operations to ensure its long-term sustainability. This proposal offers the DAO a viable path forward, which the DA may accept or reject at its discretion.
Details
I. Termination of Outdated Programs
I propose the formal termination of the following programs:
With the core game offline and no live operations team, it will no longer be feasible to address incoming security reports. Therefore, we propose discontinuing the Security Bug Bounty Program.
Due to the absence of live operations and blockchain support, the production of new badges is no longer viable. Existing badges however, will retain their respective boosts.
Given the DAO’s limited revenue streams and the lack of a live operations team to execute this task, it is advisable to suspend this proposal until additional revenue sources are established.
The cessation of the core game may have implied the conclusion of this process, but this proposal formalizes that termination.
II. Changes in Settlement Methods
In light of the limited treasury, I recommend implementing a long-term safeguard:
-
$CU Settlement
Should the DAO lack ETH or stablecoins, all financial obligations will be settled using $CU by default. -
$CU to Cash Conversion
If the DAO must settle payments on a cash basis (e.g., subscription payments) in the absence of ETH or stablecoins, $CU will be converted to cash for such purposes.
III. Scaling Down to Critical Operations
Post-turnover, I believe the focus should be on maintaining critical operations, including:
- Staking Platform Maintenance
- Staking Reward Pool Maintenance
- Marketplace Maintenance
- Official Website Maintenance
- Queueing of Safe Operations (following a DAO request)
I believes it is in the DAO’s best interest for us to discontinue the following activities:
- Blockchain Engineering
- Live Operations (including closure of Zendesk)
- Customer Support (including closure of Zendesk)
- Community Management (including closure of team-owned Discord and Telegram and transition to a DAO-managed Discord)
- Governance (including closure of the team-owned forum and transition to a DAO-managed Discord)
- Social Media (transitioning Twitter to a legacy page and closure of other social media)
- Marketing
- Business Development
- Product Development
- Art Production
- Accounting (including cessation of treasury report releases)
Based on current financial obligations in ETH, cash, or stablecoins, the DAO’s estimated monthly financial responsibility is $28,604.
Service Providers | Coverage | Cost in (USD) | Frequency |
---|---|---|---|
Venticello | uniWU.me maintenance | $ 5,000.00 | Monthly until November |
Vault Team | Staking Contract Maintenance | $ 15,000.00 | Monthly |
Laguna Team | Multi-sig Operations, Staking Reward Pool, Marketplace, Website and Staking Website Maintenance | $ 7,000.00 | Monthly |
$ 27,000.00 |
While these costs are projections, the outlined work coverage is fixed. Moving forward, the DAO may engage any of these service providers to renegotiate fees directly.
Additionally, I present the following subscriptions for consideration. I believe these should not be renewed unless the DAO opts to maintain CU’s brand presence.
Subscriptions | Purpose | Cost | Frequency |
---|---|---|---|
Twitter Blue Check | $ 11.00 | Monthly | |
Gitbook | Whitepaper, Starter Guide, Charter | $ 300.00 | Monthly |
Discourse | Governance Forum | $ 100.00 | Monthly |
$ 411.00 |
Note: To ensure accuracy of information, all intellectual property and licensing-related efforts will be presented by the contributor separately.
Conclusion
I believe these changes are crucial for optimizing the DAO’s ability to meet its financial responsibilities going forward. As this is a proposal, the DAO is encouraged to vote on revisions, removals, or additions to any section of this document.