This proposal defines the scope of dexie’s governance.
Overview
dexie can be divided into three main areas: operations, development, and the treasury/DBX economy. dexie is not an entirely autonomous protocol: While exchanging assets via offers is fully decentralized and peer-to-peer, the Core Team manages Splash! indexers, hosts the user interface, and handles development.
This proposal aims to limit the governance scope to the treasury/DBX economy. It ensures that dexie can iterate quickly without lengthy governance discussions on UI or operational details, while DBX stakeholders maintain control over financial aspects.
dexie’s treasury, which accumulates various assets from fees, is owned by DBX stakeholders, who decide how to utilize the capital. This could involve investing part of it to earn an additional return, distributing dividends, or executing DBX buybacks and token burns — all managed collectively through the governance process.
The Scope
dexie’s governance must strictly relate to decisions surrounding DBX tokenomics, distribution strategies, and the management and allocation of dexie’s treasury. Day-to-day operational decisions, including development, UI, and other non-financial aspects, will remain the responsibility of the Core Team.
Governance encompasses, but is not limited to:
- Changes to DBX tokenomics and distribution
- Treasury fund allocation and investment strategies
- Initiatives for liquidity incentives
- Partnerships and integrations with other DeFi projects (eg. project token swaps)
- Issuing grants or rewards for contributions
- Adjusting the monthly team DBX distribution
- Major contractual changes or agreements impacting the treasury or DBX
Changes to the scope
This proposal is not static and can be amended through the governance process itself. Any proposed changes must undergo the same discussion and voting process as other governance proposals.
Snapshot vs. On-Chain voting
While the initial bootstrap phase is exclusively based on snapshot voting, governance will eventually incorporate both snapshot and on-chain executions, depending on the context. Transparency is key; as long as everyone can verify vote results and subsequent actions, the project’s integrity is ensured. In the future, certain actions, such as accessing treasury funds, will always require an on-chain vote enforced by code.
Voting Process
Every DBX token holder is eligible to vote on this proposal once it moves to the voting stage. TibetSwap DBX LP token holders can vote based on the conversion rate at the time of creating the snapshot. The result will be determined by a majority vote.
Discussion and Feedback
This governance proposal is now up for discussion and will move to a snapshot vote after community feedback. Please review and provide your input to help shape the final version. More related proposals will follow.