Evmos DAO addition

docs/articles/advanced/governance/Evmos-DAO/Evmos-DAO.md

@@ -0,0 +1,13 @@
+# **Evmos DAO & Community Governance**
+
+
+## **Evmos DAO**
+
+**Evmos DAO** is the community-led & organized decentralized organization dedicated to the Evmos Network, which aims to continue its part in building the Evmos ecosystem.
+
+The DAO operates under the Interim Constitution, passed by the Evmos community in Proposal #51.
+
+The **Evmos Governance Framework** is still a work in progress and will be rolled out modularly. Like the Interim Constitution, the Framework will likely change and evolve as the network matures and grows.
+
+
+Document created by the Evmos DAO, https://evmos.community

docs/articles/advanced/governance/Evmos-DAO/Governance-Overview.md

@@ -0,0 +1,17 @@
+# **Evmos Network Governance**
+
+Governance is the process of interaction and decision-making among the stakeholders of a given system or organization. It is also the way rules, norms and actions are structured, sustained, regulated and upheld.
+
+
+## **Truly Decentralized, Community Governed Network**
+
+The Evmos network, like other Cosmos-based chains, utilizes `on-chain governance` for all protocol level execution of proposals via the `gov` module included in the Cosmos SDK. This gives the community full control of the network, including complex parameter changes, distribution changes, treasury pool spending, and even upgrades to the network. Anyone who holds or stakes EVMOS can participate in these votes, regardless of the voter's validator choices. Immense power is given to the community to govern and dictate the future of the chain.
+
+
+## **Limitations and Shortcomings**
+
+While the governance module in Cosmos SDK is sufficient for on-chain governance, there are limitations and shortcomings of the module that make it difficult to conduct off-chain governance - a crucial component for a DAO to be able to operate efficiently. Furthermore, the Cosmos ecosystem is lacking the innovative DAO management toolings that EVM-based DAOs have at their disposal. We hope to bridge the growing gap in innovations and tools between Ethereum and Cosmos with the deployment of interoperable tools onto our EVM, opening up a new world of tools for IBC chains.
+
+
+
+Document created by the Evmos DAO, https://evmos.community

docs/articles/advanced/governance/Evmos-DAO/Governance-Voting.md

@@ -0,0 +1,52 @@
+# **Governance Voting**
+
+
+## **Voting Period**
+
+The voting period is currently a fixed 5-day period. During the voting period, participants may select a vote of either `Yes`, `No`, `Abstain`, or `NoWithVeto`. Voters may change their vote at any time before the voting period ends.
+
+
+## **Voting Options**
+
+
+
+1. **<code>Abstain</code></strong>: indicates that the voter is impartial to the outcome of the proposal.
+2. <strong><code>Yes</code></strong>: indicates approval of the proposal in its current form.
+3. <strong><code>No</code></strong>: indicates disapproval of the proposal in its current form.
+4. <strong><code>NoWithVeto</code></strong>: indicates stronger opposition to the proposal than simply voting <code>No</code>. If the number of <code>NoWithVeto</code> votes is greater than a third of total votes excluding <code>Abstain</code> votes, the proposal is rejected and the deposits are[ burned](https://evmos.community/governance/voting#burned-deposits).
+
+Voting <code>NoWithVeto</code> provides a mechanism for a minority group representing a <em>third</em> of the participating voting power to reject a proposal that would otherwise pass. This makes explicit an aspect of the consensus protocol: it works as long as only up to[ a third of nodes fail](https://docs.tendermint.com/v0.34/introduction/what-is-tendermint.html). In other words, greater than a third of validators are always in a position to cause a proposal to fail outside the formalized governance process and the network's norms, such as by censoring transactions. The purpose of internalizing this aspect of the consensus protocol into the governance process is to discourage validators from relying on collusion and censorship tactics to influence voting outcomes.
+
+
+## **What determines whether or not a governance proposal passes?**
+
+There are four criteria:
+
+
+
+1. A minimum deposit of 192 EVMOS is required for the proposal to enter the voting period
+    * anyone may contribute to this deposit
+    * the deposit must be reached within 3 days (this is the deposit period)
+2. A minimum of 33.4% of the network's voting power (quorum) is required to participate to make the proposal valid
+3. A simple majority (greater than 50%) of the participating voting power must back the `Yes` vote during the 5-day voting period
+4. Less than 33.4% of participating voting power votes `NoWithVeto`
+
+Currently, the criteria for submitting and passing/failing all proposal types is the same.
+
+
+### **How is voting tallied?**
+
+Voting power is determined by stake weight at the end of the 5-day voting period and is proportional to the number of total EVMOS participating in the vote. Only bonded EVMOS count towards the voting power for a governance proposal. Liquid EVMOS will not count toward a vote or quorum.
+
+Inactive validators can cast a vote, but their voting power (including the backing of their delegators) will not count toward the vote if they are not in the active set when the voting period ends. That means that if I delegate to a validator that is either jailed, tombstoned, or ranked lower than 150 in stake-backing at the time that the voting period ends, my stake-weight will not count in the vote.
+
+Though a simple majority `Yes` vote (ie. 50% of participating voting power) is required for a governance proposal vote to pass, a `NoWithVeto` vote of 33.4% of participating voting power or greater can override this outcome and cause the proposal to fail. This enables a minority group representing greater than 1/3 of voting power to fail a proposal that would otherwise pass.
+
+
+### **How is quorum determined?**
+
+Voting power, whether backing a vote of `Yes`, `Abstain`, `No`, or `NoWithVeto`, counts toward quorum. Quorum is required for the outcome of a governance proposal vote to be considered valid and for deposit contributors to recover their deposit amounts. If the proposal vote does not reach quorum (ie. less than 33.4% of the network's voting power is participating) within 5 days, any deposit amounts will be burned and the proposal outcome will not be considered to be valid.
+
+
+
+Document created by the Evmos DAO, https://evmos.community

docs/articles/advanced/governance/Evmos-DAO/Interim-Constitution-of-Evmos-DAO.md

@@ -0,0 +1,77 @@
+# **The Interim Constitution of Evmos DAO**
+
+
+## **Preamble: The Evmos Mission**
+
+We, the Evmos Community, formally declare our shared beliefs and mission to build and assist in growing the Evmos network. We strive to be the leading EVM network in the Cosmos Ecosystem, utilizing the Cosmos SDK modules, Tendermint's consensus engine, and the Inter Blockchain Protocol for a fully decentralized, censorship-resistant, interoperable chain. The Evmos network, our community, and our governance processes must strive to play a role in laying the foundation for a more equitable, hyper-connected, decentralized future.
+
+
+## **1. The Evmos Community**
+
+The Evmos Community (“community”) is a general all-encompassing term that comprises various groups that are participants in the Evmos network. The level and degree of participation may vary by group, but the common denominator of all members of the community should be the shared interest in the continued growth of the Evmos network.
+
+**1. Protocol Developers** - this group of developers focuses mainly on improving the Evmos network on the protocol level; this group includes core developers as well as individual contributors not considered as core team members.
+
+**2. Network Validators** - network validators are key members of the community responsible for securing the network through the Tendermint proof-of-stake consensus mechanism.
+
+**3. Network Delegators** - network delegators are the predominant group that assist in network consensus and security by delegating power to validators through the staking of tokens.
+
+**4. Workstream and Committee Members** - workstream and committee members are those that work to improve and grow the Evmos network on a non-protocol level.
+
+**5. Community Leaders** - workstreams and special projects, although not required, may have an appointed leader to steward and lead his or her group.
+
+**6. Application Developers and End Users** - application developers and end users are those that develop, deploy, utilize, interact, transact, and ultimately bring value to the Evmos ecosystem.
+
+While the aforementioned groups make up the majority of the community, the definition and composition of the community are not strictly limited to these groups.
+
+
+## **2. The Evmos Governance Framework**
+
+The Evmos Governance Framework (“framework”) is the foundational set of guidelines and processes developed for the community and network contributors to follow and flourish. The framework should be designed to recognize and incentivize contributors and curate a culture that creates long-term, positive-sum interactions between all community members and the Evmos ecosystem.
+
+The framework is to be proposed and adopted separately from the Constitution. The Constitution shall take priority over the Governance Framework and should be regarded as the supreme guiding document.
+
+
+## **3. Guiding Principles and Values**
+
+**1. Progressive Decentralization:** The Evmos network aims to be as decentralized as possible, in the context of network validation as well as governance and finances. While network resiliency and the decentralization of power is paramount, we recognize the need to proceed with strategic and scientific-based planning. The community must not haphazardly rush into decisions that may potentially destabilize the chain or provoke a strong negative community reaction. The community will take the stance of progressive decentralization as we research and analyze the social, legal, and/or financial ramifications our decisions may potentially have.
+
+**2. Neutrality and Non-Partisanship:** We believe in the principles of equality for all and must act in accordance with this core principle. All groups and community members have equal access to information, equal rights, and equal responsibilities, as defined by this Constitution. No one group or community member should be favored over any other members. No one group or community member should be disfavored over any other members. We define “favor” as an unfair benefit that is not a direct consequence of provable effort and actions done, in alignment with our mission and goals. We define “disfavor” as an unfair punishment or loss of opportunity that is not a direct consequence of provable actions done against Evmos’ mission and goals.
+
+**3. User-Centrism:** Evmos is specialized to provide a unique EVM experience in the Cosmos ecosystem. We must therefore continue to optimize for 1) user adoption and 2) the qualities that contribute to steady growth: network liquidity, improvement of user experience, data sovereignty, stable production of blocks, educational resources, strong governance, etc.
+
+**4. Agnosticism:** Evmos should maintain neutrality as a chain with roots in both the Ethereum and Cosmos ecosystems. While the governance of Evmos may be reliant from time to time on other networks or tools, the Evmos community should retain a stance of neutrality. Community members must leave tribalism at the door; we should refrain from engaging in political debates that are not directly relevant to improving the Evmos network.
+
+**5. Cross-Chain Diplomacy:** Evmos is a network with a long history in the decentralization movement, with inspirations, ideas, protocols, and allies in various networks. Our community will come from a wide range of blockchain communities. Cross-chain collaborations, outreach initiatives, diplomacy missions, and continued participation in events are highly encouraged — especially with chains from the EVM and IBC ecosystems.
+
+**6. Consensual Collaboration:** While the Cosmos SDK’s implementation of governance is relatively permissionless, this does not mean anyone is entitled to work or compensation. Proposals will be assessed by the community on their merits alone and eventually voted on. In addition, proposals must follow the Governance Framework of the Evmos network and adhere to the principles outlined in the Constitution.
+
+**7. Sovereignty to Work:** The purpose of the Governance Framework is not to micro-manage proposals or teams. Sovereignty will be given to those that are working in accordance with the original proposal passed by the community, and are not in violation of any governance processes or principles of the Constitution.
+
+
+## **4. Removal of Community Leaders**
+
+All community members appointed to a role of higher responsibility, including workstream members, may be removed via a formal vote on-chain. The Governance Framework shall outline the appointment, removal, and appeals process, along with a detailed dispute resolution guideline.
+
+
+## **5. Constitutional Rights**
+
+Constitutional rights protect the members of the community from any unjust or cruel treatment by another member or the DAO itself. The Governance workstream shall amend a Bill of Rights to the Constitution as soon as a general consensus can be confidently reached.
+
+
+## **6. Constitutional Amendments and Revisions**
+
+The community holds the power to propose an amendment to the Constitution by following the standard Evmos Proposal Lifecycle. The reasoning for the amendment must be justified and petitioned. If possible, there should be an attempt made to resolve the issue before a proposal for amendment is initiated.
+
+
+---
+
+**Validator/Community Code of Conduct and Constitutional Rights**
+
+We recognize that this Constitution is missing a few key topics — however, we also see the need to tread carefully in these sensitive and controversial topics. While it is inarguable that these are necessary components of the Constitution, there was clear signaling that we needed more time to allow for the natural growth of the community before we could formally ratify some sections with confidence. We pledge to continue our research and continue to engage with the community to find general consensus on the best step forward.
+
+While some topics will be amended into the Constitution when they are ready, most will likely be implemented through the Governance Framework.
+
+
+
+Document created by the Evmos DAO, https://evmos.community