diff --git a/basics/governance/Community.md b/basics/governance/Community.md new file mode 100644 index 000000000..54f0f680d --- /dev/null +++ b/basics/governance/Community.md @@ -0,0 +1,118 @@ +# Community + +### Community Overview + +The Filecoin Community exists to govern the network, propose changes and improvements, and ensure that the values that underly the network are upheld. The Community’s goal is to make the Filecoin network efficient, robust, and usable. In order to ensure that the Community is aligned about the best way to move the mission of Filecoin forward, the Community needs to be aligned around the mission of the network and the values that the participants hold. + +There are key differences between mission and values. The mission of Filecoin is the high-level purpose and principals of the project. The values are the motivations and assumptions that help align the community around the mission. The Code of Conduct exists to ensure that we are all operating in a safe and friendly environment as we work toward the mission. + +### Mission + +The Mission of Filecoin is to create a decentralized, efficient, and robust foundation for humanity’s information. This can be broken down further: + +- Decentralized + - The network is not dependent on any one party, e.g., not dependent on a company, foundation, or other organization to continue operating. + - No centralized parties can control, stop, or censor the network, its operation, or its participants. + - Users and providers are not controlled or governed by powerful intermediaries (unlike markets like Uber or Airbnb). + - Activity is trustable (web3) through the public verifiability of operations and rational incentives. + - Refers to the decentralization movement of 2015+, including IPFS, Bitcoin, Ethereum, and more. + - Third parties cannot prevent willing participants from exchanging data and/or payments for it. + - Filecoin uses cryptography, end-to-end encryption at rest, and incentives to secure information and network operation. +- Efficient + - Make digital storage (spacetime) a proper commodity with real markets + - Decouple digital storage from cloud computing moat feature sets -- turn storage market into a real market where any provider can sell their storage. + - Enable humanity to create an efficient digital storage market, with small margins and as close as we can get to physical limitations. + - Ensure efficient usage of digital storage resources -- reduce digital space waste (unused storage supply while prices are high enough to warrant using it). + - Drive more and more efficient usage of storage media. + - Enable fast (sub-second) buying and selling of spacetime. + - Enable programs to buy and sell spacetime (without having to be humans or have an associated bank account) -- i.e., a cryptocurrency wallet and code should be enough to buy storage. + - Clients can trust Filecoin will serve data quickly and efficiently back to them. + - Filecoin will not waste user resources (storage, bandwidth, computation, time) unnecessarily. +- Robust + - Filecoin has five 9s of uptime or more. + - Clients can trust Filecoin to keep their data safe. + - Clients can trust Filecoin to serve their data in a variety of extreme circumstances (in the distant future). + - Clients can trust Filecoin to replicate storage and to self-repair lost replicas over time. + - Clients can use Filecoin to store critical application data and trust it to work whenever they need that data back. + - The network is robust to attack by all sorts of powerful parties, including state-level actors. + - The network is robust to changing market dynamics and powerful counter incentives -- meaning, it is rational to continue operating the network. + - The network is robust to network censorship attacks (given there exist willing storage providers). + - The network is robust to specific file censorship attacks (given there exist willing storage providers). + - The network is robust to catastrophic attacks (i.e., nuclear war, long-running internet partitions, etc.). + +### Code of Conduct + +The best way to make the vision of Filecoin become a reality is through a friendly, safe, and accepting community. Harassment, intimidation, and other behaviors that negatively impact the Filecoin Community will not be tolerated. + +All members of the community are expect to abide by the Code of Conduct at all time in all Filecoin community venues, online and in person, and in one-on-one communications about Filecoin. The Code of Conduct covers the usage of all Filecoin public infrasctructure, Filecoin websites, Filecoin related events, and services offered by or on behalf of Filecoin. We expect people to follow this Code of Conduct in Filecoin Open Source project communities, public GitHub repositories, IRC channels, social media, mailing lists, and public events. + +- Friendly Harassment-Free Space + + - We are committed to providing a friendly, safe and welcoming environment for all, regardless of gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics. + - We ask that you please respect that people have differences of opinion regarding technical choices, and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a single right answer. A difference of technology preferences is not a license to be rude. + - Any spamming, trolling, flaming, baiting, or other attention-stealing behavior is not welcome, and will not be tolerated. + - Harassing other users is never tolerated, whether via public or private media. + - Avoid using offensive or harassing nicknames, or other identifiers that might detract from a friendly, safe, and welcoming environment for all. + - Harassment includes, but is not limited to: harmful or prejudicial verbal or written comments related to gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics; inappropriate use of nudity, sexual images, and/or sexually explicit language in public spaces; threats of physical or non- physical harm; deliberate intimidation, stalking or following; harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact; and unwelcome sexual attention. + - Media shared through public infrastructure run by the Filecoin team must not contain illegal or infringing content. You should only publish content via Filecoin public infrastructure if you have the right to do so. This includes complying with all software license agreements or other intellectual property restrictions. You will be solely responsible for any violation of laws or others’ intellectual property rights. + +- Avoid Marketing or Soliciting + + - You are welcome to post endorsements of tools, products or services that you personally find useful, but please refrain from blatant advertising, marketing or any kind of spam. Selling commercial services or fundraising is not allowed. + +- Reporting Violations of this Code of Conduct + + - If you believe someone is harassing you or has otherwise violated this Code of Conduct, please contact us at [abuse@filecoin.io](mailto:abuse@filecoin.io) to send us an abuse report. If this is the initial report of a problem, please include as much detail as possible. It is easiest for us to address issues when we have more context. + +- Copyright Violations + + - We respect the intellectual property of others and ask that you do too. If you believe any content or other materials available through public Filecoin infrastructure violates a copyright held by you and you would like to submit a notice pursuant to the Digital Millennium Copyright Act or other similar international law, you can submit a notice to our agent for service of notice to: [abuse@filecoin.io](mailto:abuse@filecoin.io) + Please make sure your notice meets the Digital Millennium Copyright Act requirements. + +- Consequences + + - All content published to public Filecoin infrastructure is hosted at the sole discretion of the Filecoin team. + -Unacceptable behavior from any community member will not be tolerated. + - Anyone asked to stop unacceptable behavior is expected to comply immediately. + -If a community member engages in unacceptable behavior, the Filecoin team may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event or service). + +- Addressing Grievances + + - Please contact [abuse@filecoin.io](mailto:abuse@filecoin.io) if you need to report a problem or address a grievance related to an abuse report. + - If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should contact [abuse@filecoin.io](mailto:abuse@filecoin.io). We will do our best to ensure that your grievance is handled appropriately. + - In general, we will choose the course of action that we judge as being most in the interest of fostering a safe and friendly community. + +- Contact Info + + - Please contact [abuse@filecoin.io](mailto:abuse@filecoin.io) if you need to report a problem or address a grievance related to an abuse report. + - You are also encouraged to contact us if you are curious about something that might be "on the line" between appropriate and inappropriate content. We are happy to provide guidance to help you be a successful part of our community. + +- Changes + + - This is a living document and may be updated from time to time. Please refer to the git history for this document to view the changes. + +- Credit and License + + - This Code of Conduct is based on the [npm Code of Conduct](https://www.npmjs.com/policies/conduct). + + - This document may be reused under a [Creative Commons Attribution-ShareAlike License](http://creativecommons.org/licenses/by-sa/4.0/). + + +### Values + +The current guiding values of the Filecoin Community are under construction. + +### How to Participate + +- Become a Storage Provider +- Become a Client +- Work with an Ecosystem Partner +- Become a Tokenholder +- Work as a Developer +- Join the Guild +- Participate in Community Calls +- Vote On-Chain +- Join the Slack +- Attend an Event +- Host an Orbit Event +- Author a FIP diff --git a/basics/governance/Overview.md b/basics/governance/Overview.md new file mode 100644 index 000000000..25cf7ea0c --- /dev/null +++ b/basics/governance/Overview.md @@ -0,0 +1,50 @@ +### What is Filecoin? + +Filecoin is a **blockchain**-based **decentralized storage network** designed to store humanity’s most important information. But what does this actually mean in the real world? + +Current cloud storage networks offer relatively limited services and are not always widely available. For the most part, these services are owned by just a few major providers who get to dictate the prices, areas of coverage, and who gets to use their service. Filecoin proposes a new storage model with economic incentives, with local storage around the globe that is owned and operated by the users of the network itself. This **hyper-local** and **peer-to-peer** model means more efficient access to data, freedom from **centralized storage** providers, and the ability to take part in the **governance** of the network in order to guide the direction of Filecoin. + +### **Who is part of the Filecoin Network?** +The Filecoin network is made up of several key players: +-**Storage Providers (SPs)** +-**Clients** +**-Ecosystem Partners** +**-Tokenholders** +**-Developers** +**-Filecoin Foundation** +**-Founding Engineers/Core Devs** + +These groups and individuals are all part of the Filecoin **Community,** and help shape the future of the network. + +### How does the Filecoin network function? + +Filecoin aims to democratize the way data is stored and shared, lower costs for storage, and provide economic incentives for those who participate in the network. + +What’s in it for **Storage Providers**? They get the opportunity to make storage accessible and usable for the storage of important data. Storage providers make it possible to create a transparent and equitable storage market. There is also a monetary incentive for Storage Providers in the form of FIL, the network’s native **cryptocurrency**. There are two main sources of revenue for SPs: providing storage and retrieval services, and by securing the Filecoin network. + +### What’s in it for **Clients**? +They can rest easy knowing their data is securely stored, free from corporate control, resistant to censorship, and available across the globe. The prices to store data on the Filecoin network are competitive compared to traditional cloud storage, and network is highly flexible and reliable as it is verified regularly with both **proof-of-spacetime** and **proof-of-replication**. + +### What’s in it for the **Community**? +The Filecoin Community guides the direction of the network, participating in the governance and overseeing the day-to-day operations of the network itself. Much of the governing of Filecoin is done through **Filecoin Improvement Proposals** (FIPs). Community members can submit FIPs to propose new features, changes to processes, or changes to the environment. They can also vote on FIPs, document their opinions, and build consensus within the community. Community members are also active in the Filecoin Slack, where they can discuss the current state and future of the Filecoin Network, meet like-minded individuals and organizations working to democratize data storage, and connect with projects happening across the network. Filecoin Foundation also hosts a variety of virtual and in-person events that the community can participate in across the globe, which offer opportunities for connection, learning, and building the future of data storage. + +### How is Filecoin governed? + +Governance is a blanket term that means, simply, the process of overseeing the control and direction of something. The importance of governance is that it helps define who has power and accountability, who gets to make decisions, and how the process of decision making happens. + +Filecoin operates on a decentralized model, which means that the people participating in the governance process have the opportunity to impact the network and set the direction it takes. Participation in a decentralized governance system means that individual people, organizations, and projects partners from around the world can all come to the table together to have their voices heard and find consensus about what is best for the network and how to help it achieve its mission. It is a very real model of ownership, personal investment, and responsibility that allows the community to work together in a clear and process-driven way. + +Filecoin is governed through the FIP process, which lets anyone in the community author a recommendation for changes or improvements to the network. Currently, for a FIP to pass, soft consensus is required from the community. You can learn more about the FIP process [here]. + +The Community Guild also plays a critical role in the governance process, and is especially important for high-risk and complex FIPs. The Guild is made up of one representative from each of the following groups: +-Storage Providers +-Clients +-Ecosystem Parterns +-Tokenholders +-Developers +-Filecoin Foundation +-Founding Engineers/Core Devs + +Each representative has one vote that is meant to represent the interests of the community they represent in the Guild. This serves to provide institutional representation, an expert consensus body, and a veto check on community voting. This is a critical governing body for complicated FIPs where consensus might be difficult or various parts of the community might be split on the best route forward. + +The Filecoin community is highly active, involved in the process, and dedicated to the mission of the network. diff --git a/basics/governance/the-fips-process.md b/basics/governance/the-fips-process.md index 5427e965b..e8c683b37 100644 --- a/basics/governance/the-fips-process.md +++ b/basics/governance/the-fips-process.md @@ -4,4 +4,256 @@ description: >- --- # The FIPs process +# Filecoin Improvement Proposals (FIPs) +Filecoin Improvement Proposals (FIPs) can be authored by anyone in the community, and are the main mechanism for governing the Filecoin Network. A FIP provides the technical specifications of a feature, documents the rationale for the proposal, and documents both consensus and dissenting opinions. In this way, FIPs provide a historical record of the decisions made by the community for Filecoin’s features, technical input, and design decisions. FIPs are also a way to track the progress of implementation and who has authored or suggested improvements. + +A FIP is an important piece of the governance process within Filecoin for several key reasons: + +-It gives community members a chance to guide the network by making recommendations which may then be implemented +-It creates an important forum for community engagement where people can come together to discuss proposed ideas and work together in collaboration to explore solutions +-It creates an open record of all ideas proposed, the conversation around those ideas, and why they were or were not implemented +-It provides a clear process for making changes to the network and clearly defines the roles that people within the community can play in terms of shaping the proposals, making edits or recommendations, and moving the FIP through the stages from creation to implementation + +FIPs should be contain a single idea or proposal, and be focused on how this proposal will improve the network. The more concise and focused the FIP, the more likely it is to succeed and be implemented. + +There are five categories of FIPs, listed in order of increasing complexity and risk to the network: + +**Network Standards (FRCs)**—These FIPs do not require consensus, and are proposals to document network best practices and key recommendations +**Technical FIPs**—These FIPs require consensus and are for changes to the core protocol stack +**Cryptoeconomic FIPs**—These FIPs are to propose changes that will affect the economic policy of the network, or for changes that are likely to have a substantial impact on existing token dynamics and network incentives +**Community FIPs**—These FIPs introduce structural or programmatic changes to the Filecoin Community, including changes to its governance process +**Security FIPs**—These FIPs are for emergency technical changes to the core protocol in event of attack, capture, outage, or other immediate threats to the network + +## FIP Roles, Stages, and Paths to Acceptance + +Every FIP requires the participation of the community. As a FIP moves through the path to acceptance, it will go through several key statuses that require the community to interact in different ways. These statuses tell us where the FIP is on the path to acceptance and create an important record of community involvement and the historical considerations for the network. As a community member, it is critical to participate in the FIP process—this is the way to have your voice heard, to shape the network, and to usher in important changes that represent the needs of Filecoin at any given point in time. + +### FIP Roles + +There are five key roles involved in the FIP process: + +- The FIP author or champion + + This is the person who writes the FIP and proposes it to the community, to guide the discussions through the appropriate forums, and to build community consensus around the idea + +- The FIP editors + + This is the person who reads the FIP draft, and confirms that it makes technical sense, checks the language, and makes any needed recommendations for changes + +- The Filecoin Core Developers + + These are the people who help write the code for the Filecoin network, and will ultimately code the changes for accepted FIPs + +- The Filecoin Community + + These are the members of the community who will offer feedback, and who the FIP champion will try to build consensus with + +- The Community Guild + + The Community Guild is a governing institution that is made up of representatives from each of the following community groups: + + - Storage Providers + - Clients + - Tokenholders + - Developers + - Filecoin Foundation + - Core Devs + - Protocol Labs + + The Guild plays a critical role in the FIP approval process, and they are especially critical for high-risk and complex FIPs. + + The goal of the Guild is to provide clear, transparent, and expert guidance through the FIP approval process. As FIPs grow in risk and complexity, it is critical that the level of certainty in the FIP itself grows in equal measure. This is where the Guild becomes a vital piece of the governing body of the community—because the Guild is comprised of representatives from the above groups, they are able to provide expertise, technical understanding, and a important checks and balances in the system. The Guild decentralizes the “expert function” away from just Core Devs. + + The Guild has the ability to veto community votes on especially complex or risky FIPs, and requires hard consensus in order to move forward. + + +Before you begin writing a FIP, check in with the community. You want to ensure that you idea is new, has adequate support, can be applied to the whole community, and has not been previously researched and rejected. The best ways to check in with the community are the I[ssues section of the Github Repository](https://github.com/filecoin-project/FIPs/issues), the [Filecoin Discourse Forum](https://discuss.filecoin.io/), and the [Filecoin community chat](https://docs.filecoin.io/basics/project-and-community/chat-and-discussion-forums). + +### FIP Statuses + +All proposed FIPs go through the same process, and have similar stages that the FIP champion is responsible for seeing through. FIPs are created as Pull Requests in GitHub, and the FIP editors will process the Pull Requests through the following statuses: + +- Work in Progress (WIP) + + After the champion has asked the Filecoin community whether or not an idea has any chance of support, they can write a draft FIP as a pull request. + + If the WIP looks good, a FIP editor will assign the FIP a number and merge your pull request. + + If the WIP is unfocused, too broad, a duplication of effort, technically unsound, does not have give clear motivation, does not address issues with backward compatibility, or is not in line with the Filecoin improvement principals, the WIP will be denied at this stage. The FIP author can that edit the WIP and resubmit, depending on the reason the WIP was denied. + + For Community, Cryptoeconomic, and Technical Core FIPs, this is the stage where a **Community Temperature Check** must be done. The Temperature Check is a simple tool that is used to gauge early-stage community support for FIP drafts. These checks are non-binding, anonymous, and are meant only to help indicate community prioritization of FIPs at the WIP stage. + +- Draft + + After the WIP is merged, you can keep submitting follow-up pull requests with additional changes until you believe that the FIP is ready to move onto the next stage. A FIP remains in Draft status until it is implemented, at which point it is considered for promotion to the next status (this is not the same for Core FIPs). + + Once the FIP champion and FIP editors believe the FIP is ready, the FIP editor will assign Last Call status and set a review date (usually 14 days later). + + If the FIP editors believe that changes still need to be made to the draft, Last Call status will be denied. The goal is for FIPs to only enter Last Call status once, so it is important for them to be polished and technically sound at this stage. + +- Last Call + + During Last Call, the FIP is listed prominently on the Filecoin website. After the Last Call period ends, there are three different directions a FIP can go: + + -Reversion to Draft: If a FIP reaches Last Call but the community believes that it needs changes or is not technically sound or viable, the FIP will revert to Draft status. + + -Accepted (Core FIPs only): A successful Last Call without changes will become Accepted. + + -Final (Not Core FIPs): A successful Last Call with needed changes will become Final. + +- Accepted (Core FIPs only) + + Accepted FIPs move into the hands of the the Filecoin implementation developers. They decide whether or not encode it into their clients as part of a consensus upgrade, and this process is outside of the FIP process. + + For a Standard Track Core FIP to be considered Final, it must be implemented in at least two viable Filecoin clients (currently, Lotus, Venus, and Forest). A Pull Request to update the spec of the text of the spec and describe the protocol changes must be submitted to the [Filecoin Specification repository](https://github.com/filecoin-project/specs) before the FIP can proceed to Final status. When the implementation is complete and has been adopted by the community, the status will be changed to Final. + +- Final + + A FIP in Final status represents the current state of Filecoin. A Final FIP should only be updated to correct errors. + +- Other statuses + + Deferred: Core FIPs that have been put off for a future consensus upgrade + + Rejected: A FIP that is fundamentally broken or unworkable, or a Core FIP that was rejected by the Core Devs and will not be implemented + + Active: This is similar to Final status, but it denotes a FIP that maybe be updated without changing its FIP number + + Superseded: A FIP that was previously Final, but is no longer considered state-of-the-art because a newer FIP has taken its place and updated it; the newer FIP will be in Final status, and will reference the Superseded FIP + + +### What needs to be in a FIP? + +For a FIP to be successful, it should contain the following parts. It also needs to be written in [markdown](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) format so that it will display properly. + +- Preamble + + Each FIP must begin with a standard metadata header section called RFC 822. This style of header gives us important information about what is in the body of the FIP, and it is critical for building tools to organize, manage, and record documents on the web. The preamble needs to include a FIP number, a short and descriptive title, and author details. + + You can find FIP templates [here[. + +- Simple Summary + + Each FIP should be explained in simple, clear language that is easy to understand. The summary is for a wide audience that includes non-technical and technically included people. If you struggle it explain it simply, consider chatting with the community to make sure you understand the subject deeply enough. + +- Abstract + + The abstract should be 200 words or less, and needs to describe the technical issue being addressed. + +- Motivation (Optional) + + Having a motivation for a proposed FIP is an important way of gaining community buy-in, and it is especially important for FIPs that propose changes to the Filecoin protocol. This section should clearly address why the existing protocol solutions in place are inadequate to address the problem, and how the FIP solves that problem. FIP submissions without clear and compelling motivations are very likely to be rejected. + +- Specification + + For any new feature or process, technical specifications are required. These should be detailed enough to allowing competing and interoperable implementations for any of the current Filecoin platforms. + +- Rationale + + The rationale gives the details of what motivated the design and why particular design decisions were made. The rationale is different than the motivation; where the motivation gives the reason for the FIP proposal, the rationale explains why the proposed FIP is designed the way it is and how that supports the motivation. It should also include alternate designs that were considered, related work (for example, how the feature will be supported in other languages) + +- Backwards Compatibility + + For any FIP that is not backwards compatible (meaning, older version will not work without special adaptions or modifications), a section must be included that explains what the incompatibilities are and and what their severity is. The FIP champion also needs to propose how to deal with these incompatibilities. FIPs that do not have a clear plan for handling backwards compatibility are likely to be rejected. + +- Test Cases + + If a FIP requires consensus, test cases must be included. All other FIPs can choose whether or not to include links to test cases. + +- Security Considerations + + All FIPs need to have a section that discusses the security implications and concerns of the proposed change. Consider including any information that might be important for security discussions, make note of any risks, and detail any security-relevant design decisions made. + + Other things to consider including are: + + -any important previous discussions + + -security concerns + + -implementation or client-specific guidance or pitfalls + + -an outline of threats and risks, and how they are being addressed in the FIP + + Any FIP that does not include a security section will be rejected. A FIP cannot make it to Final status without a Security Considerations discussion that is deemed sufficient by the FIP reviewers. + +- Implementations + + For a FIP to be moved to Final status, the actual code for the proposed changes needs to be written and committed—this is known as implementation. However, this step doesn’t need to be completed for the proposed FIP to be merged as a draft in Github and be considered Accepted. + +- Copyright Waiver + + All FIPs are required to be in the public domain, and Filecoin is an open source project. + + +### Pathways to FIP Acceptance + +Once your FIP is drafted, it is time to hit the road toward Acceptance. + +FIPs with different levels of complexity have different pathways for reaching consensus so that the community can align the scope of the FIP, the complexity of the change, and the need for due diligence and community participation in the FIP process. This also means that the community can set appropriate thresholds for the acceptance of different types of FIPs. + +The details of how each FIP can reach Acceptance is detailed below: + +- Community FIP + + **When the FIP is at the WIP stage**, it is time to do a Community Temperature Check. The Temperature Check is a simple tool that is used to gauge early-stage community support for FIP drafts. These checks are non-binding, anonymous, and are meant only to help indicate community prioritization of FIPs at the WIP stage. + + If there is early support from the community for a Community FIP, the FIP can move to Draft status and then Last Call. **When the FIP is in Last Call**, the FIP will move to a Community Vote **and** Community Guild Consensus. + + The Community Vote will happen via a voting tool for hard consensus and will be off-chain with the option to either accept or reject. + + The Community Guild will hold a session to discuss the FIP and vote. The Guild will vote in a private, recorded meeting that will be made available after the fact for transparency. + + If both the Community and the Guild vote to pass the FIP, it will be moved to Accepted status and be moved to the implementation stage. + + If the Community votes to pass the FIP but the Guild does not, + + If the Guild votes to pass the FIP but Community does not, + + If the FIP does not pass at this stage, then it will be rejected. + +- Network Standards (FRCs) + + **When a Network Standards FIP reaches the Last Call stage**, a presentation on the proposal will be made to the Core Devs. The Core Devs will audit the proposal and conduct a review. + + These FIPs require soft consensus to pass. If soft consensus is achieved, the FIP passes. If not, it is rejected. + +- Cryptoeconomic FIP + + Cryptoeconomic FIPs are some of the most complex FIPs in the Filecoin ecosystem because they come with the most risk and can usher in very complicated changes to our systems. + + **When the FIP is at the WIP stage**, it is time to do a Community Temperature Check. The Temperature Check is a simple tool that is used to gauge early-stage community support for FIP drafts. These checks are non-binding, anonymous, and are meant only to help indicate community prioritization of FIPs at the WIP stage. + + If there is early support from the community for a Community FIP, the FIP can move to Draft status and then Last Call. **When the FIP is in Last Call**, the FIP will move to a Community Vote **and** Community Guild Consensus. + + The Community Vote will happen via a voting tool for hard consensus and will be off-chain with the option to either accept or reject. + + The Community Guild will hold a session to discuss the FIP and vote. The Guild will vote in a private, recorded meeting that will be made available after the fact for transparency. + + If both the Community and the Guild vote to pass the FIP, it will be moved to Accepted status and be moved to the implementation stage. + + If the Community and the Guild are at odds on the vote, if the FIP becomes contentious, or if there is not clear consensus with either the Guild or the Community, the following outcome matrix will be used to determine whether or not the FIP is accepted. + + ![Screenshot 2023-10-03 at 8.56.10 PM.png](https://prod-files-secure.s3.us-west-2.amazonaws.com/c89addf5-1c49-42bf-acfc-70e44c06122c/a558bfd0-7762-4cf5-9b96-ef69cedf5091/Screenshot_2023-10-03_at_8.56.10_PM.png) + +- Technical Core FIP + + **When the FIP is at the WIP stage**, it is time to do a Community Temperature Check. The Temperature Check is a simple tool that is used to gauge early-stage community support for FIP drafts. These checks are non-binding, anonymous, and are meant only to help indicate community prioritization of FIPs at the WIP stage. + + If there is early support from the community for a Community FIP, the FIP can move to Draft status and then Last Call. + + **When the technical FIP reaches the Last Call stage**, a presentation on the proposal will be made to the Core Devs. The Core Devs will audit the proposal and conduct a review. + + These FIPs require soft consensus to pass. If the FIP does not achieve soft consensus from the community, it will move to a vote. If the FIP receives hard consensus from the community vote, the FIP is accepted and moved to Accepted status. + + If the FIP does not achieve hard consensus to pass, then the FIP is rejected. + +- Security FIP + + When a Security issue is identified, a Security FIP is opened. **At the Last Call stage**, the Core Devs make a recommendation, perform an audit, and review the FIP. + + After the Core Devs do their review, the FIP goes to the Community Guild. The Guild conducts their own review and audit of the security issue and proposed solutions. + + If the Guild reaches hard consensus to accept, then the FIP is accepted. + + If the Guild does not reach consensus to accept, then the FIP is rejected.