# DIP-1 - Governance Scope **URL:** \ **Category:** Proposals (DIPs)\ **Created:** [June 18, 2024, 3:18pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18 "2024-06-18T15:18:30Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![dns](https://gov.dexie.space/user_avatar/gov.dexie.space/dns/32/9_2.png) [@dns](https://gov.dexie.space/u/dns)\ **Post date:** [June 18, 2024, 3:18pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/1 "2024-06-18T15:18:30Z")
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. ---
**Author:** ![darvd29](https://gov.dexie.space/user_avatar/gov.dexie.space/darvd29/32/13_2.png) [@darvd29](https://gov.dexie.space/u/darvd29)\ **Post date:** [June 18, 2024, 5:04pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/2 "2024-06-18T17:04:58Z")
I agree with the proposed scope of the governance. In the ever-changing world of crypto it is vital not to hinder the continuous development of new functionalities of the platform, while leaving a range of non-technical decisions to the community. ---
**Author:** ![SlowestTimelord](https://gov.dexie.space/user_avatar/gov.dexie.space/slowesttimelord/32/27_2.png) [@SlowestTimelord](https://gov.dexie.space/u/SlowestTimelord)\ **Post date:** [June 18, 2024, 11:52pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/3 "2024-06-18T23:52:29Z")
I also agree with the proposal for governance scope. Will there be a way for wXCH (warped XCH) holders to take part in the voting process? ---
**Author:** ![dns](https://gov.dexie.space/user_avatar/gov.dexie.space/dns/32/9_2.png) [@dns](https://gov.dexie.space/u/dns)\ **Post date:** [June 19, 2024, 7:05am UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/4 "2024-06-19T07:05:24Z")
> [@SlowestTimelord](#): > > Will there be a way for wXCH (warped XCH) holders to take part in the voting process? Do you mean wDBX? At the moment, no, but in theory, it’s possible to implement. The current supply of wDBX is about 8k. ---
**Author:** ![collector.xch](https://gov.dexie.space/letter_avatar_proxy/v4/letter/c/2bfe46/32.png) [@collector.xch](https://gov.dexie.space/u/collector.xch)\ **Post date:** [June 19, 2024, 7:05am UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/5 "2024-06-19T07:05:39Z")
I agree with the proposed scope of the governance. ---
**Author:** ![spark](https://gov.dexie.space/user_avatar/gov.dexie.space/spark/32/14_2.png) [@spark](https://gov.dexie.space/u/spark)\ **Post date:** [June 19, 2024, 1:07pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/6 "2024-06-19T13:07:43Z")
Good idea to limit the scope first, but still let it be extendable in the future (“Changes to the scope”) should dbx holders seek more participation. ---
**Author:** ![SlowestTimelord](https://gov.dexie.space/user_avatar/gov.dexie.space/slowesttimelord/32/27_2.png) [@SlowestTimelord](https://gov.dexie.space/u/SlowestTimelord)\ **Post date:** [June 20, 2024, 3:45am UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/7 "2024-06-20T03:45:46Z")
Yes I meant wDBX lol Related to the consideration for wDBX, what about expanding the scope of governance proposals to encompass changes to the voting process itself? For example: Are there controls in place to ensure the addresses holding the non-circulating supply of DBX are ineligible for voting? And should the warp.green held DBX also be ineligible for voting if wDBX voting support is implemented? I think these are questions that could be appropriate addressed by a governance proposal. ---
**Author:** ![karlkim](https://gov.dexie.space/user_avatar/gov.dexie.space/karlkim/32/26_2.png) [@karlkim](https://gov.dexie.space/u/karlkim)\ **Post date:** [June 20, 2024, 7:55am UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/8 "2024-06-20T07:55:09Z")
> [@SlowestTimelord](#): > > Related to the consideration for wDBX, what about expanding the scope of governance proposals to encompass changes to the voting process itself? I supported limiting the scope for now, but I see the potential for future expansion. I think the idea is related to DBX tokenomic as well? This could benefit a growing community of wDBX holders on other blockchains. ---
**Author:** ![Yak](https://gov.dexie.space/user_avatar/gov.dexie.space/yak/32/29_2.png) [@Yak](https://gov.dexie.space/u/Yak)\ **Post date:** [June 20, 2024, 8:11am UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/9 "2024-06-20T08:11:58Z")
I think the current code only allows votes from DBX with a standard P2 inner puzzle. That means that, even if TibetSwap and warp.green reserves are included in the snapshot, they cannot be used to vote. ---
**Author:** ![dns](https://gov.dexie.space/user_avatar/gov.dexie.space/dns/32/9_2.png) [@dns](https://gov.dexie.space/u/dns)\ **Post date:** [June 20, 2024, 10:21am UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/10 "2024-06-20T10:21:32Z")
> [@SlowestTimelord](#): > > Are there controls in place to ensure the addresses holding the non-circulating supply of DBX are ineligible for voting? And should the warp.green held DBX also be ineligible for voting if wDBX voting support is implemented? These are important points. Uncirculated supply is not allowed to vote. While this rule is not technically enforced, everyone would be able to notice an uncirculated address at the top of the ballot list. Addresses containing the uncirculated supply are filtered when creating the snapshot, so they not even show up as Outstanding. The addresses containing the uncirculated supply are listed at the bottom of [https://dexie.space/dbx](https://dexie.space/dbx). > [@Yak](#): > > That means that, even if TibetSwap and warp.green reserves are included in the snapshot, they cannot be used to vote. Correct, and to allow for voting with TibetSwap DBX LP tokens, we take a CAT snapshot of TibetSwap DBX LP holders, convert their balance to the corresponding DBX amount, and add them to the ballot list. They can then vote and appear as if they have DBX. This is not possible for the reserves because no one can sign from the address where the reserves are held. ---
**Author:** ![SlowestTimelord](https://gov.dexie.space/user_avatar/gov.dexie.space/slowesttimelord/32/27_2.png) [@SlowestTimelord](https://gov.dexie.space/u/SlowestTimelord)\ **Post date:** [June 22, 2024, 2:33pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/11 "2024-06-22T14:33:18Z")
> [@Yak](#): > > I think the current code only allows votes from DBX with a standard P2 inner puzzle. That means that, even if TibetSwap and warp.green reserves are included in the snapshot, they cannot be used to vote. > [@dns](#): > > Correct, and to allow for voting with TibetSwap DBX LP tokens, we take a CAT snapshot of TibetSwap DBX LP holders, convert their balance to the corresponding DBX amount, and add them to the ballot list. They can then vote and appear as if they have DBX. This is not possible for the reserves because no one can sign from the address where the reserves are held. Appreciate the clarifications! > [@karlkim](#): > > I supported limiting the scope for now, but I see the potential for future expansion. I think the idea is related to DBX tokenomic as well? This could benefit a growing community of wDBX holders on other blockchains. It’s definitely related to tokenomics, but I can envision future proposals around voting weights, caps, sybil/DID rules etc. I don’t feel strongly about including this in the scope either way given the governance scope itself is amendable through the governance process itself, and I don’t foresee such proposals happening in the short term. ---
**Author:** ![dns](https://gov.dexie.space/user_avatar/gov.dexie.space/dns/32/9_2.png) [@dns](https://gov.dexie.space/u/dns)\ **Post date:** [July 1, 2024, 9:02pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/12 "2024-07-01T21:02:28Z")
Thanks for the feedback! DIP-1 is now officially open for voting: [https://dexie.space/governance/4000eb96fe9a22e0b72c56b610a4cac6e427fd1f1819be4259c4bb79f19fb2a4](https://dexie.space/governance/4000eb96fe9a22e0b72c56b610a4cac6e427fd1f1819be4259c4bb79f19fb2a4) The vote will run for one week (until block 5615841). ---
**Author:** ![D.Yamen](https://gov.dexie.space/user_avatar/gov.dexie.space/d.yamen/32/41_2.png) [@D.Yamen](https://gov.dexie.space/u/D.Yamen)\ **Post date:** [July 10, 2024, 7:30pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/13 "2024-07-10T19:30:42Z")
Sorry for the stupid question, but I can’t find something on how to vote. How to do it? ---
**Author:** ![darvd29](https://gov.dexie.space/user_avatar/gov.dexie.space/darvd29/32/13_2.png) [@darvd29](https://gov.dexie.space/u/darvd29)\ **Post date:** [July 10, 2024, 7:32pm UTC](https://gov.dexie.space/t/dip-1-governance-scope/18/14 "2024-07-10T19:32:35Z")
Hi! No worries it’s not stupid. Voting for DIP-1 has already finished and the proposal was approved by dexie DAO. Stay tuned for future proposals!