💯Comprehension check
Review the following scenarios to test your comprehension of the different components of the MVC DAO protocol, such as the Security Council, MIPs, on-chain and off-chain actions. By exercising your understanding of these scenarios, you'll be better equipped to confidently navigate the process, governance tools, and governance proposals that support the MVCDAO.
Scenario 1: You have an idea that you'd like to propose to the MVCDAO
What's the first step you should take?
The first step is to submit the idea as an draft proposal on the public MVCDAO governance forum and discuss/debate it for 1 week before submitting an informal temperature check[draft proposal] using MVC DAO management tool.
This procedure is referred to as the Temperature Check phase and is technically optional, but it's strongly recommended as a due-diligence governance best practice. Although the process for submitting an MIP to the governance forum isn't explicitly outlined in the Constitution, the Constitution does specify that the DAO may approve and implement MIPs to change the rules governing the system. See 'How to submit a DAO proposal' for more detailed instructions on how to submit an MIP.
Scenario 2: A security emergency issue arises on MVC.
How can the DAO respond to the security emergency?
The Security Council is a committee of N-2 democratically elected members who are signers of a multi-sig wallet. This committee is afforded by the MVCDAO the power to perform emergency actions, as delegated to it by the MVCDAO, and is responsible for upholding the constitution of MVCDAO.
In this scenario, the Security Council should handle the emergency immediately by either implementing the required software upgrade or performing whatever other mitigating action is required in order to remedy the situation on behalf of the DAO and its members. This type of Security Council action is known as an emergency action and requires a 9-of-12 approval from the Security Council to execute.
The Security Council shouldn't use its power to perform emergency actions except in a true security emergency, such as a critical vulnerability that could significantly compromise the integrity, confidentiality, or availability of a chain governed by the MVC DAO. After performing an emergency action, the Security Council must issue a full transparency report to explain what was done and why the emergency action was justified. Notable details:
The MVCDAO is able to modify the Security Council's powers or to eliminate the Security Council entirely through the submission, approval and implementation of a Constitutional MIP. (75% voting right is required)
The MVCDAO is able to curtail or eliminate the Security Council's power to perform emergency actions via approval and implementation of a Constitutional MIP. (75% voting right is required)
The Security Council may also approve and implement routine software upgrades, routine maintenance and other parameter adjustments in a non-emergency setting (such actions are referred to as "non-emergency actions"), which require a 7-of-12 approval in order to take effect.
Equivalent "copies" of the Security Council multi-sig contracts (7-of-12 in the case of non-emergency actions, and 9-of-12, in the case of emergency actions) exist.
Scenario 3: You want to propose a change to the system parameters of MVC Chain.
What process should be followed to implement this change?
The process for proposing and implementing changes to system parameters is as follows:
Confirm the draft proposal checklist before submission of a draft proposal.
Submit the draft proposal as an MVC Improvement Proposal (MIP) on the public forum, which will be discussed and debated for 1 week (Temperature Check phase).
The MIP or draft proposal moves to a voting phase for 10 days, where token holders can vote on the proposal.
If the proposal passes the vote, security council will arrange to implement the changes.
Note that the Security Council may also approve and implement routine software upgrades, maintenance and other parameter adjustments in a non-emergency setting. This bypasses Phases 1 to 3 of the MIP process and goes directly through Phases 4 [Internal security Council Voting]. This is done to prevent routine upgrades and maintenance from being delayed or filibustered by the temperature check, voting, and delay phases of the MIP process.
Scenario 4: You want to propose a change to the Constitution of the MVCDAO
What process should be followed to implement this change?
The process for proposing and implementing changes to the Constitution is as described in the Constitution itself. It involves submitting the proposal as an MIP, and then going through the same voting and delay phases as any other proposal. The proposal must pass with a supermajority (75%) of votable tokens being voted in favor of the change. Changes to the Constitution must also be ratified by the Security Council with a 7-of-12 approval in order to take effect.
Scenario 5: You want to become a member of the Security Council
How can you become a member of the Security Council?
The Security Council has at least 5 members, The next election occurs 01 Apr 2024
Scenario 6: You want to upgrade the MVC chain
What process should be followed to execute this upgrade?
The process for upgrading the MVCDAO chain involves submitting a proposal as a MIP and going through the same voting and delay phases as any other proposal. The proposal must pass with a supermajority (75%) of votable tokens being voted in favor of the change. The upgrade must also be approved by the Security Council with a 7-of-12 approval in order to take effect. MVCDAO will then perform the upgrade by updating the contract implementation, and adjusting system parameters.
It's important to note that the upgrade should be thoroughly tested and reviewed by the community and experts in the field before being proposed and implemented. Any upgrade should also be compliant with the applicable laws, in particular sanctions-related regulations.
Scenario 7: The MVCDAO experiences a season of voter apathy.
Will this prevent work from being done on MVC
No, voter apathy won't prevent work from being done on the MVC chains. The Constitution allows for non-emergency actions to be taken, which don't require the approval of token holders. The Security Council has the power to perform emergency actions with a 9-of-12 approval, which can be used to address critical issues that cannot wait for voter approval. While voter participation is important for the proper functioning of the DAO, the Constitution has built-in mechanisms to ensure that work can continue to be done even in the event of low voter turnout.
Note that voter apathy could have an impact on the governance of the DAO, and certain decisions and actions might not be as representative of the community's collective will if voter turnout is low.
Scenario 8: You've $Space tokens, but you don't have time to actively participate in MVC DAO's governance.
What options do you have?
If you've $Space tokens but don't have time to actively participate in the MVC DAO's governance, you have a few options:
You can delegate your tokens' voting power to another member of the community who you trust to make decisions that align with your interests. See how to delegate your voting power for more information.
You can hold onto your $Space tokens and vote when you have the time, but please note that some important decisions may have already been made.
You can sell your $Space tokens to another member of the community who is more active.
While participating in governance is an important aspect of being a DAO member, it's not mandatory. As long as you hold $Space tokens, you can participate in the MVCDAO's governance protocol, but there aren't any consequences if you decide to not participate.
Scenario 9: A governance proposal passes that you voted against.
What options do you have?
If a governance proposal passes that you voted against, you have a few options:
You can accept the outcome and continue to participate in the DAO.
You can engage in further discussions and debates on the community forum to express your dissenting opinion and try to sway others to your point of view.
You can propose a new MIP that addresses the issues you have with the proposal that passed and try to get it passed through the voting process.
You can choose to disengage from the DAO altogether and sell your votable tokens before the proposal takes effect. This is facilitated by the time delay between the proposal passing and the proposal taking effect.
Scenario 10: Administrative / Executive proposal can't wait for 22days.
MVCLabs may approve to implement routine document upgrades, routine contributor replacement, routine media exposure and administrative work in advance. Action and costs with Administrative & Executive nature should be within executive budget on a monthly basis.
Conclusion
This comprehension check has been provided as an optional study aid that token holders and prospective delegates are encouraged to periodically review, share, and build upon. If you have any questions or concerns, visit the MVCDAO governance forum or Discord.
Last updated