# What Is the Connext Collective? {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at . {% endhint %} The Connext Collective is an ecosystem composed of autonomous entities and individuals aligned with the common goal of realizing the Connext vision. This documentation outlines the various components of the Connext Collective and the collaborative efforts driving the advancement of the Connext protocol. *** ## Components of the Connext Collective ### The Connext DAO The Connext DAO, comprised of NEXT token holders, governs critical aspects of Connext's smart contracts and is responsible for allocating resources from the DAO treasury to fund protocol development and growth. ### The Connext Foundation The Connext Foundation is a Cayman Islands foundation company that was established for the purpose of supporting the Connext ecosystem. The Connext Foundation is an independent entity with fiduciary responsibilities to support the Connext ecosystem through activities such as strategic stewardship and partnership initiatives. ### Core Contributors Core Contributors are organizations funded by the DAO to undertake research and development efforts, aimed at improving the Connext protocol. Core Contributors engage in an open Connext Improvement Proposal (CIP) process to solicit input from the community and propose upgrades. ### The Broader Connext Community The Connext ecosystem encompasses a diverse community comprising users and infrastructure operators, such as routers. This engaged community actively participates in the protocol's utilization, provides feedback, and aids in maintaining the protocol's robustness. # Connext Foundation {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at . {% endhint %} The Connext Foundation is a Cayman Islands foundation company dedicated to supporting the Connext ecosystem. ### What does the Connext Foundation do? The Connext Foundation, a shareholderless legal entity that is, by its constitutional documents, mission aligned with the Connext ecosystem, takes any actions that it feels will benefit the Connext ecosystem. These may include: * Entering into agreements with partners and third parties for the benefit of the Connext ecosystem. * Owning and administering intellectual property rights on behalf of the Connext ecosystem. * Administering grants of NEXT tokens to projects that will advance the Connext ecosystem. * Coordinating and funding research and development related to the Connext ecosystem. * Creating and administering the Connext Improvement Proposal (CIP) process - an open process (similar to the EIP process) by which Core Contributors and other community members can propose and discuss improvements to the Connext protocol. * Hosting and moderating a user interface for the DAO Governance Process. * Providing transparency and reporting to the DAO on the efficacy of Core Contributor work to provide accountability for NEXT resource allocation. * Communicating updates about the protocol and DAO to the broader Connext community. * Promoting decentralization of the Connext protocol. ### How does the Foundation Work? The Connext Foundation is made up of a board of directors, officers, consultants, and service providers. The initial directors of the foundation are Robert Drost, Glen Kennedy, and Arjun Bhuptani. The Connext Foundation is funded initially by an allocation of 10.8% of the supply of NEXT tokens as well as a grant from Proxima Labs (formerly known as Connext Labs), the original development company behind the Connext protocol.
# Core Contributors Core Contributors are organizations (for-profit companies, developer guilds, or sub-DAOs) that develop and grow the Connext protocol. Core Contributors may be funded by the Connext DAO and follow the Connext Improvement Proposal process to get public feedback on proposed protocol changes prior to developing them. *** ### Why Have Many Core Contributors? A key part of the Connext vision is for the Connext protocol to become a true, credibly neutral public good.\ \ The Connext ecosystem’s philosophy is that this outcome is best achieved by having a wide variety of contributors from many different backgrounds, spanning many different organizations.\ \ In order to minimize governance, the Connext DAO has initially been set up to fund contributors in NEXT tokens on an ongoing basis via vesting, with the capability for the DAO to adjust tokens vested quarterly or semi-annually based on efficacy and output of various Core Contributors. Core Contributors are then simultaneously: * **Collaborative** with each other to ensure the best outcome for the Connext protocol due to their shared collective ownership in the DAO through NEXT. * **Competitive** with each other (and with potential new Core Contributors) on ongoing grants of NEXT from the DAO, ensuring a high quality of execution over potentially many years of research & development. *** ### List of Core Contributors As of the time of writing, the following organizations are involved in some capacity as Core Contributors to the Connext ecosystem.
ContributorTypeFocus Ares(s)
Connext FoundationFoundationDAO & CIP administration, communications, grants.
Proxima LabsFor-profit
R&D Lab		R&D of core protocol, supplementary products, tooling, and developer onboarding/integrations.
WonderlandFor-profit
R&D Lab		R&D of core protocol, supplementary products, and tooling.
Community LeadersSub-DAOCommunity management, education, user support, and marketing.
P2PFor-profit CompanyRouter tooling development, router ecosystem administration.
CoinHippoFor-profit ContractorDevelopment of Connext explorer, bridge, and other user interfaces.
Veil CapitalFor-profit FundNEXT token distribution, economics, and institutional relationship management.
CreedDAOProtocol security research.
# Security Council {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on the Connext forum at {% endhint %} ### Roles and Responsibilities The Security Council plays a critical role in safeguarding the Connext protocol, its DAO members, and the wider community. Its responsibilities include: * Conducting critical maintenance, including software updates and configurations * Taking emergency actions in potentially time-sensitive situations The Security Council operates under the purview of the Connext DAO, which is responsible for holding membership elections. ### Election Process Elections for the Security Council are held annually, excluding an initial 6-month bootstrapping phase, during which the Connext Foundation will appoint the initial council. Before each election cycle, the Connext DAO will open a call for candidates, after which all eligible candidates will participate in the elections. In the [proposal ](https://snapshot.org/#/dao.connext.eth/proposal/0x1de93ea3698896c4af022b9c7ae21abfe20b27a4c15aadef4407f448953b5f87)from September 2024, changes to the election and structure of the Security Council were outlined such that: * New council is comprised of 8 regular members and a Lead, translating into a 7/9 multisig. * The term of each cohort is 12 months * All the Council members (9 out of 9) have a technical background that allows them to read code and detect possible vulnerabilities. * Monthly compensation is included for each Council member, which remunerates them for their work and the risk of taking on the responsibility that comes with being part of the Council. * Maximum members of the same organization were reduced from 3 to 2 #### Criteria for Membership To be considered for a position on the council, candidates must meet the following criteria: * Garner support from at least 0.4% of the voting supply prior to the election. * Maintain membership in the Connext DAO for at least 3 months prior to the election. * Have no more than 2 representatives from the same organization on the Council at a given time. * Publicly disclose any potential conflicts of interest prior to campaigning for membership. #### Emergency Removals In the case of repeated non-compliance of the expected duties, any Security Council may be revoked at any time outside of standard elections if a mayority of the existing council members agree on the removal. The Connext DAO can also remove council members through a two-thirds majority vote with a minimum participation of 6% of the token supply. ### Why have a Council? While Connext aims to move towards ungovernance in the future, the Connext protocol is not currently ready to operate without a degree of administrative oversight in emergency and non-emergency situations. Electing a council allows the DAO to ensure they have representation at this level while allowing council members to gain experience operating the protocol. # What is NEXT {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} NEXT is the governance and utility token of Connext. NEXT is deployed as an xERC20 (crosschain native) token on every chain Connext supports. ## How is NEXT used? At launch, NEXT is used to govern the Connext DAO, an organization responsible for allocating funding for the ongoing development of the protocol. True decentralization and permissionless operation of the Connext protocol are achieved by ossifying repeatable governance processes and enshrining them directly into the underlying protocol. This process is called **ungovernance**. In the future, NEXT can additionally be used to ungovern the network by making activities such as routing, chain support, and token listing permissionless via NEXT staking, subject to DAO approval. ## Mainnet Token Deployments
AddressTypeTypeAddress
Ethereum0xFE67A4450907459c3e1FFf623aA927dD4e28c67a0xFE67A4450907459c3e1FFf623aA927dD4e28c67aERC20ERC20
Arbitrum0x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E80x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E8xERC20
Optimism0x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E80x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E8xERC20
Polygon0x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E80x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E8xERC20
Gnosis0x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E80x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E8xERC20
BSC0x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E80x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E8xERC20
## Testnet Token Deployments
AddressTypeTypeAddress
Ethereum Goerli0x9F0ec1c7eA8f317Ef7D653C18d3717f87a37B7380xFE67A4450907459c3e1FFf623aA927dD4e28c67aERC20ERC20
Arbitrum Goerli0x9F0ec1c7eA8f317Ef7D653C18d3717f87a37B7380x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E8xERC20
Optimism Goerli0x9F0ec1c7eA8f317Ef7D653C18d3717f87a37B7380x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E8xERC20
Polygon Mumbai0x9F0ec1c7eA8f317Ef7D653C18d3717f87a37B7380x58b9cB810A68a7f3e1E4f8Cb45D1B9B3c79705E8xERC20
# Airdrop Details Key Details, Token Allocation, and Eligibility Criteria {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} ## Airdrop Overview The NEXT airdrop will be conducted through a first-of-its-kind airdrop mechanism, allowing eligible recipients to natively claim NEXT on the chain of their choice without the need to use a bridge or pay unnecessary gas fees. ### NEXT Details
Details
Total supply1,000,000,000
Token typexERC20
Token address0xFE67A4450907459c3e1FFf623aA927dD4e28c67a
Claimable chainsArbitrum, Optimism, Polygon, and Gnosis Chain
Snapshot dateAugust 1, 2023 at 00:00 UTC
Timestamp: 1690848000
Claiming beginsSeptember 05, 2023 at 13:00 UTC
Timestamp: 1693918800
Claiming endsMarch 05, 2024 at 13:00 UTC
Timestamp: 1714914000
*** ### Airdrop Eligibility Criteria {% tabs %} {% tab title="Users" %} {% hint style="info" %} After carefully reviewing feedback, we found that certain categories of transactions were not being counted towards the airdrop as we originally intended. \ To provide the best possible outcome, we adjusted the eligibility criteria on August 24, 2023. The total amount of NEXT that will be distributed during the airdrop was increased, ensuring that no pre-existing allocations are decreased. {% endhint %} A basic point system was used to determine the number of NEXT each recipient can claim. Our points criteria accounted for stableswap liquidity provision and bridge usage, with the most points awarded to users demonstrating consistent usage. In total, a maximum of 13 points were possible with both bridge and LP activity, and using partner projects or being a community advocate acted as a multiple on the accumulated points. ### User Qualifying Criteria Users earn 1pt for meeting the Mandatory Qualifiers and 1pt for each qualifier unless otherwise stated. #### Mandatory Qualifiers *Users must qualify for at least one of the following two criteria in order to qualify for the NEXT airdrop* 1. Transferred 5 or more times with an average value of at least $15 per transaction (calculated across all transactions) and a total volume exceeding $200. 2. Provided at least $1,500 in liquidity to the Connext network for a minimum of 1 day. *Vector usage will be included towards your points if* 1. Users interacted with NXTP (deployed November 2021) at least once via bridging or LPing. #### Stableswap LP Activity Qualifiers 1. Interacted with stableswap pools at least 25 times. 2. Interacted with stableswap pools at least 50 times. 3. Interacted with stableswap pools at least 100 times. 4. Provided at least $3,000 in liquidity (2 pts). 5. Provided at least $6,000 in liquidity (2 pts). 6. Provided at least $9,000 in liquidity (2 pts). 7. Provided at least $12,000 in liquidity (2 pts). 8. Provided liquidity for at least 30 days. 9. Provided liquidity for at least 60 days. #### Bridge Usage Qualifiers 1. 10 or more bridge transactions. 2. 25 or more bridge transactions. 3. 50 or more bridge transactions. 4. At least 3 unique months. 5. At least 6 unique months. 6. At least 9 unique months. 7. At least 12 unique months. 8. Transacted at least $1,000 on v2. 9. Transacted at least $2,500 on v2. 10. Transacted at least $5,000 on v2. 11. Transferred between 6 or more chains. 12. Transferred between 10 or more chains. #### Multipliers 1. Utilized a partner protocol (1.5x Multiplier) {% endtab %} {% tab title="Routers" %} A basic point system was used to determine the number of NEXT each router has earned. Our points criteria focused primarily on utility of provided capital, with longevity carve-outs to recognize the importance of capital being available on relatively low traffic chains. Additionally, multipliers were applied to router operators that were exceptionally helpful to the community (created dashboards, ran subgraph infrastructure, etc.) as well as those impacted by the nomad hack. ### Router Qualifying Criteria #### Router Activity Qualifiers 1. Had transactions in at least 7 unique months. 2. Had transactions in at least 12 unique months. 3. More than 50K transactions. 4. More than 200K transactions. 5. More than 350K transactions. 6. More than $5M in total router volume. 7. More than $40M in total router volume. 8. More than $80M in total router volume. 9. More than 100 days of transaction support. 10. More than 400 days of transaction support. 11. More than 700 days of transaction support. #### Multipliers 1. Impacted by nomad hack (1.5x multiplier). 2. Contributing router operators (3x multiplier). {% endtab %} {% tab title="Community Advocates" %} A basic point system was used to determine the number of NEXT each CA / CL earned. Our points criteria focused on quality and duration of contributions ### Community Advocate Qualifying Criteria #### Mandatory Qualifiers * Must be an active leader in the Connext community as recognized by the team. #### Community Advocate Activity Qualifiers * Number of months of support * Quality of contributions {% endtab %} {% endtabs %} *** ### Sybil Filtering To mitigate Sybil attacks, the following filters were applied to the data: * ***Removal of Known Malicious Actors.*** \ Addresses associated with previous Sybil attempts or known hackers were eliminated from the data. * ***Interaction Analysis.*** \ The interaction amount, frequency, and volume were analyzed across Ethereum, Polygon, and Binance Smart Chain (BNB). Addresses matching identified sybil-patterns (suspiciously high amounts of activity, identical transfer types, etc.) were eliminated from the airdrop. * ***Fund Flow Analysis.***\ Addresses that share a funding source may indicate Sybil accounts. * ***Address Clustering.***\ Transaction graphs were analyzed using clustering and community detection algorithms to identify sybils. *** # Tokenomics {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} ## NEXT Allocations The high-level allocations of NEXT are as follows:
Category% of total supplyNumber of NEXT
Community50.94%509,428,750
Early Backers22.43%224,338,119
Ecosystem & Strategic Backers11.24%112,352,000
Early Team & Advisors11.61%116,097,420
Proxima Labs3.78%37,783,010
The Community category can be further subdivided into:
Category% of total supplyNumber of NEXT
DAO29.44%294,350,509
Connext Foundation10.94%109,446,745
Airdrop10.56%105,631,496.18
{% hint style="info" %} After carefully reviewing feedback, we found that certain categories of transactions were not being counted towards the airdrop as we originally intended. To provide the best possible outcome, we adjusted the eligibility criteria on August 24, 2023. {% endhint %} ## Supply Schedule Allocations of NEXT to the following categories of recipients are subject to a lockup period. * Early Backers * Ecosystem & Strategic Backers * Early Team & Advisors * 50% of tokens allocated to Routers and Community Advocates as part of the Airdrop (2.15% of the total supply) The lockup period for Early Backers and Early Team & Advisors consists of a 15-month lockup followed by an 18-month **linear release**. In other words, 1/19 of the tokens will be released on December 6th, 2024, and the remaining tokens will unlock **linearly** in equal monthly 1/19 allotments until all tokens are fully unlocked (33 months after the NEXT Airdrop). {% hint style="warning" %} Edit: The lockup period and unlock schedule for Early Backers and Early Team & Advisors was amended as of September 3, 2024, as follows:\ \- The 1-year lockup period was extended to 15 months, with a new unlock date starting on December 6, 2024.\ \- The linear unlock period was extended from 12 to 18 months, with a new linear unlock rate of 1/19 per month, concluding on June 6, 2026. {% endhint %} # Constitution {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} ## Working Constitution of the Connext DAO *** The Connext DAO Constitution establishes the principles and values that guide the operations of the Connext DAO. It is intended to act as a framework for DAO participants to determine which actions should be considered to be a worthwhile allocation of resources and in the best interests of the broader Connext ecosystem (the “Connext Collective”). The Connext DAO Constitution is a working document aimed at aligning the mission of the Connext Collective and is expected to evolve through the input of the community according to the process defined in Article 5 below. ### Article 1: Purpose of the DAO The vision of Connext is to **empower builders to create applications that are universally accessible from any chain, using any token, all while maintaining the highest possible security.** The core purpose of the Connext DAO is to realize the Connext vision by effectively allocating resources to individuals and organizations (“Core Contributors”) that develop the Connext protocol and grow the adoption of the Connext network. ### Article 2: Rights and Responsibilities of the DAO The Connext DAO is comprised of NEXT holders who vote on proposals submitted by members of the broader Connext Collective. The DAO has the following capabilities: * Allocating assets from treasury to Core Contributors to support the development and growth of the protocol. * Allocating assets from treasury to fund operational expenses for the protocol until financial sustainability is achieved. * Evaluating the efficacy of resource allocation and optimizing it over time. The Connext DAO is additionally responsible for electing and removing members of the Security Council, an operational multisig that can take critical actions on behalf of Connext, such as vetoing DAO votes, performing routine upgrades, and pausing the protocol in the event of an emergency, until such time as the Security Council is no longer needed. ### Article 3: Ungovernance of the Connext Protocol Governance by NEXT holder vote is a critical first step in decentralizing the resource allocation and administration of the Connext protocol. True decentralization and permissionless operation of the Connext protocol are achieved by ossifying repeatable governance processes and enshrining them directly into the underlying protocol. This process is called ungovernance. A further goal of the Connext DAO is long-term self-limitation through ungovernance by reducing human-made decisions and automating processes such as resource allocation, fair utilization, and network administration directly within the core protocol based on appropriate on-chain metrics or incentive design. ### Article 4: Guiding Principles of the Connext DAO The Connext DAO should aim to embody the key principles that guide the Connext vision and Collective: * **A Positive Sum Mindset**: Connext is a public good that aims to push the entire web3 space forward. When evaluating proposals, the DAO should prioritize initiatives that optimize for value creation over-extraction and collaboration over unhealthy competition. * **Resiliency**: Connext is the foundational infrastructure for the future of the Internet. Trust minimization, decentralization, and security are the means by which the protocol can ensure that it continues to operate fairly and securely decades into the future. * **Data Orientation**: Connext is ultimately an experiment in decentralized coordination around a shared public good. Data is our most powerful tool to determine whether this experiment is succeeding and should be leveraged wherever possible by the DAO. * **Openness, Transparency & Integrity**: Connext is an open and accessible network that welcomes new ideas and perspectives, and operates with a high degree of transparency and integrity throughout its process. The DAO should work to uphold and embody these values wherever possible. ### Article 5: Amending this Constitution The working constitution will remain in effect until changed, with a mandatory review one year after the DAO launch. Any proposed amendments to the constitution require a two-thirds majority vote with a minimum of 6% token participation to be passed. *DISCLAIMER* *This Constitution is solely for the purposes of aligning the mission and priorities of DAO members to expand and improve the Connext protocol to empower builders to create applications that are universally accessible from any chain, using any token, while maintaining the highest possible security. This is not a legally binding agreement and is not intended to create a partnership or any legal entity or relationship amongst the members of the DAO. The DAO is made up of a diffuse, disparate and decentralized group of tokenholders that will have different priorities and goals. And while this Constitution aims to align on certain fundamental aspects regarding the use of the protocol, ultimately, the constraints on the actions of the members of the DAO are solely those that are imposed technologically (or as otherwise required by law).* *Additionally, this is not an offering or solicitation of an offer to become a member of the DAO, to purchase tokens or to otherwise engage in an enterprise. The Connext Foundation makes no representation or warranty, express or implied as to the completeness or accuracy of the information herein or elsewhere presented related to the Connext DAO or to the functionality or long-term direction of the DAO.* # Processes {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at . {% endhint %} The following series of documents outlines: * [Proposal and Voting Mechanisms](/dao-documents/processes/proposal-and-voting-mechanisms) * [Passing a Proposal](/dao-documents/processes/proposals-overview) * [Proposal Structure Guidelines](/dao-documents/processes/connext-governance-proposal-template) * [How-to Guides](/dao-documents/how-to-guides) * [Security Council Election Processes](/dao-documents/processes/security-council-election-process) # Proposal and Voting Mechanisms {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} This is a suggested process for developing and advancing Connext Improvement Proposals. It is a dynamic document intended to be owned, refined, and enforced by the Connext community. 1. [**Connext Forum**](https://forum.connext.network/)**:**\ Forum is used for governance-related discussions. Community members must register for an account before sharing or liking posts. 2. [**Snapshot**](https://dao.connext.network/)**:**\ Snapshot is a voting interface used for delegating votes and creating and voting on proposals. 3. **Crosschain Governance:**\ In line with the Connext DAO vision to empower builders to create applications that are universally accessible **from any chain, using any token,** Connext supports voting and delegation across multiple chains as well as cross-chain proposal execution. {% hint style="info" %} Note: In conjunction with the Zodiac team, Connext, and DeFi Wonderland have created a cross-chain widget that plugs into SAFEs to facilitate proposal execution. This tooling allows users to generate cross-chain payload directly from their SAFE. \ \ More information about the Zodiac Connext module is available [**here**](https://blog.connext.network/crosschain-governance-a-new-integration-connext-x-zodiac-gnosis-guild-5cf119a6cf2e). {% endhint %} # Proposals Overview {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} ## **Types of Proposals** There are three main types of governance proposals you can make: 1. **Executable Proposal:** \ This is a proposal for a series of smart contract operations to be executed by accounts the DAO controls. These can include transfers of tokens as well as arbitrary smart contract calls. Examples of this include allocating funding to a workstream multisig wallet or upgrading the Connext core contract. To maintain the security of the protocol, the proposed code must be audited by a high-quality third-party auditor and reviewed by the Security Council. Executable proposals have a quorum requirement of 15 million NEXT tokens and require a minimum approval of 50% to pass. 2. **Social Proposal:** \ This proposal seeks the consensus of the DAO members on a matter that cannot be implemented or enforced via on-chain mechanisms. Social proposals have a quorum requirement of 15 million NEXT tokens and require a minimum approval of 50% to pass. 3. **Constitutional Amendment:** \ This is a social proposal that asks the DAO to amend the constitution. The draft proposal should include the exact changes proposed to be made to the constitution. A quorum of 36 million is currently required, and a minimum approval of two-thirds to pass. *** ## **Phases of Proposal** ### **Phase 1: Request for Comments** *A governance forum post providing a description of a proposal.* #### To create a Request for Comment: * Ask a general, non-biased question to the community on the forum about a potential change. Forum posts should be labeled as follows: “Request for Comment - \[Your Title Here]“. * Reach out to your network to build support for the proposal. Discuss the proposal and solicit delegates to provide feedback on it. Be willing to respond to questions and comments. Share your viewpoint, but try to remain impartial. {% hint style="info" %} **Note**: The length of this phase is limited to 7 days. It’s in the proposal author’s interest to get as much feedback from the community as possible in this limited period of time. {% endhint %} {% hint style="info" %} **Temperature Check:** Temperature check was removed from the process based on [Formal Vote - Social CGP1 - Voting Duration](https://snapshot.org/#/dao.connext.eth/proposal/0x77125238d344e5e378387d048d6e3b2c2a45bf3d3d2b6c22b1b76c443e4e9301). {% endhint %} ### **Phase 2: Formal Vote** *A final governance forum post incorporating any feedback from the Request for Comments phase.*\ *The proposal in this phase should include the following sections:* [*Connext Governance Proposal Template*](/dao-documents/processes/connext-governance-proposal-template) #### To Create a Formal Vote: 1. Navigate to the relevant RFC and post a comment that the formal vote is live. Include the relevant title “Formal Vote \[Social/Constitutional/Executable \[Proposal Number]] — \[Your Title Here]” and link to any relevant Snapshot polls/discussion threads. Proposal numbers should be in a “CGP#” format. Topics that begin with “Formal Vote” that have not successfully passed Request for Comment stages should be removed by community moderators. 2. Ensure at least 600,000 NEXT is delegated to your address in order to submit a proposal or find a delegate who has enough delegated NEXT to meet the proposal threshold and propose on your behalf. * **Social Proposal or Constitutional Amendment:** \ Navigate to Snapshot and schedule the proposal for a snapshot vote. Votes are delayed by 2 days, and voting lasts for 7 days. If the snapshot vote passes, the proposal is passed, and you are done! * **Executable Proposal:**\ Generate the transaction using the Connext Zodiac module. If the transaction is not cross-chain, the SAFE transaction builder can be used to generate the executable data. Submit the proposal to a vote via Snapshot transaction builder. Votes are delayed by 2 days, voting lasts for 7 days, and “For,” “Abstain,” and “Against” are the voting options. If the proposal passes, anyone can request execution via Snapshot UI. Requesters must post a 5 WETH bond, and there is a 3-day delay. Once the delay elapses, anyone can execute the proposal via Snapshot, which will return the bond to the requester and execute on-chain transaction. {% hint style="info" %} **Note**: SAFE admins retain authority to delete proposals and submit their own multisig transactions, serving as a security council with veto power on community votes. \ More information about the Security Council is available [here](https://docs.connext.network/v/dao-documentation/collective/security-council). {% endhint %} {% hint style="info" %} **Note:** Voting Duration was changed to 7 days + delays, based on [Formal Vote - Social CGP1 - Voting Duration](https://snapshot.org/#/dao.connext.eth/proposal/0x77125238d344e5e378387d048d6e3b2c2a45bf3d3d2b6c22b1b76c443e4e9301). {% endhint %} # Security Council Election Process {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} Elections for the Security Council are held annually, excluding an initial 6-month bootstrapping phase, during which the Connext Foundation will appoint the initial council. Before each election cycle, the Connext DAO will open a one-month-long call for candidates, followed by the voting period. The top 8 candidates will then be inducted into the council for one term that will last for 12 months. Serving multiple terms will be possible, however, it will require candidates to submit a new application and be elected into the Security Council through a formal vote. Changes to these elections may be proposed by the DAO, but not in an ongoing election cycle. {% hint style="info" %} Note: Prior to the first election, the DAO can post an RFC to discuss whether the term duration should be 6 or 12 months. {% endhint %} *** ## Criteria for Membership Any DAO member may declare their candidacy for the Security Council. To be considered for a position on the council, candidates must meet the following criteria: * Posess a technical background and the ability to read code and detect possible vulnerabilities. * Garner support from at least 0.4% of the voting supply prior to the election. * Maintain membership in the Connext DAO for at least 3 months prior to the election. * Have no more than 2 representatives from the same organization on the Council at a given time. * Publicly disclose any potential conflicts of interest prior to campaigning for membership. *** ## Experience & Expectations of Candidates Elected Special Council members are expected to: * Provide emergency contact where they can be reached in case of emergency * Possess the mandatory skills necessary to act in this role, such as knowledge of best security practices, use of hardware wallet, ability to review and sign transactions, etc. *** ## Connext Security Council - Template & Introductions Interested individuals are encouraged to use the following template as part of their application to become a part of the Connext Security Council. **Instructions**: Copy this template, fill in your details and responses, and post it as a reply below. {% hint style="info" %} Please note that you must adhere to the template. Any responses that deviate from it will be deleted for easier consultation of the candidates. {% endhint %} **Candidate Biography & Introduction** **Name:** \[Name of individual or organization] **Twitter Link:** \[Please link your Twitter account or any other social media presence of yours] **Wallet Address or ENS:** \[Please insert your wallet address or ENS] **Introduction & Area of Expertise / Skillset:** * Please introduce yourself to the community by giving an overview of your relevant professional experience in more detail. Make sure to include the skills you have that match the requirements outlined [here](https://www.notion.so/Connext-DAO-Governance-Process-315c0c62c32a477ea554070682044dbe?pvs=21)] * Why do you think you are the right person to be a part of the Security Council? **Connext DAO Vision & Goals** \[Please share your vision for the Connext DAO and what the goals of the DAO should look like.] *** ## Current Security Council | Name | Affiliation | | --------------- | ----------------- | | Goncalo / Lead | Creed | | Layne | Proxima Labs | | James | Proxima Labs | | Rahul | / | | Greg | Chainsafe | | Veil | Veil | | Facu | / | | Stefan | Connext Community | | Vending Machine | Vending Machine | | | | # Connext Governance Proposal Template {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} This is a Connext Governance Proposal Template. Proposers are required to copy and include the following sections within Connext Governance Proposals: **“\[Social/Constitutional/Executable \[CGP#]] — \[Your Title Here]”** * **Abstract** - Abstract is a multi-sentence (short paragraph) summary. This should be a very short and human-readable version of the specification section. Someone should be able to read only the abstract to understand what the proposal does. * **Motivation** - A statement on why the community should implement the CGP. * **Rationale** - An explanation of how the CGP aligns with the community's mission and guiding principles[.](https://docs.connext.network/v/dao-documentation/dao-documents/constitution) Please reviews the [Constitution](/dao-documents/constitution) for vision and guiding principles. * **Key Terms** - Definitions of any terms within the proposal that are unique to the proposal, new to the community, and/or industry-specific. This section is optional, but recommended. * **Specifications** - The specification should describe the proposal in detail. The specification should be detailed enough to cover all the details of the proposal. * **Steps to Implement** - The steps to implement the CGP, including associated costs, manpower, and other resources for each step where applicable. CGPs that involve transactions with third parties (such as grants) will need to ensure that applicable legal documentation and procedures are also included. * **Timeline** - Relevant timing details, including but not limited to start date, milestones, and completion dates. * **Overall Cost** - The total cost to implement the CGP. The overall cost section should include a breakdown of the total cost of the CGP, including any associated costs for each step where applicable. Consider both fixed costs and recurring costs. # How-to Guides {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} Here, you will find a series of How-to Guides, including: * [How to conduct a temperature check using Snapshot Poll](/dao-documents/how-to-guides/conduct-a-temperature-check) * [How to vote](/dao-documents/how-to-guides/vote) # Conduct a Temperature Check {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} To conduct a temperature check using Snapshot Poll, simply: 1. Navigate to Snapshot to create a poll that will gauge the community's interest in your proposal. 2. Connect your wallet. 3. Open the Connext DAO Snapshot space if it isn't already open. 4. Create a poll that points to your forum post. The poll should run for 5 days and should be decided by a simple majority. 5. Navigate back to your forum post and share the link to your Snapshot poll with the community. # Vote {% hint style="warning" %} This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at {% endhint %} As a member of the Connext DAO, you can actively participate in the DAO's decision-making process by voting on governance proposals that other DAO members submit. As a NEXT token holder (or delegate), you can participate in these Snapshot polls and "temperature check" discussions: 1. Go to the Connext DAO governance forum. 2. Locate the proposal you'd like to vote on and read through the proposal and the discussion thread. 3. Provide feedback and participate in the discussion to help shape the proposal. 4. The forum submission for any given proposal will usually include a link to a Snapshot poll that allows you to vote on the proposal: * Navigate to **Snapshot**. * Connect your wallet. * Open the **Connext DAO Snapshot space** and locate the proposal you'd like to vote on (or click the Snapshot link in the forum submission). * Cast your vote by following the prompts within Snapshot's UI. Voting options are “For,” “Abstain,” and “Against.”