# [FIP-1 Amendment Proposal]Purpose and Guidelines of FIP

- Space: [FreechatDAO](https://snapshot.box/s:freechatdao.eth.md)
- Author: 0xCe340Ed98522BBFC131ea0d2d29D2E2604992CcE
- State: Passed
- Voting type: Basic
- Start: 2023-03-16 15:47 UTC
- End: 2023-03-21 15:47 UTC
- Votes: 3
- Quorum: 500,000,001 voting power
- Discussion: https://s.freechat.world/NFBEg6nj
- Open in Snapshot: https://snapshot.box/#/s:freechatdao.eth/proposal/0x2c04a361c75aa3fbf2916f5e77b22d14c4c57de0c0ee96c069ad4c01c056473c

## Results

- For: 500,000,248.16 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

fip: 1 
Title: Purpose and Guidelines of FIP
Description: Guidelines for community governance mechanism and operation, including guidelines for community development teams and implementation mechanisms.
Status: Valid
Type: Mechanism 
Author: Jack Long （jacklong@freechat.world）， Mia 
Created Time: 2022-10-22 
Modified Time: 2023-03-05
Freechat Gitbook Fips:
https://fips.freechat.world/english/fip-1/fip-1

Purpose and Guidelines of FIP
What is FIP？
FIP stands for Freechat and FreechatDAO community improvement proposal. A FIP is a design document providing information to the community or describing a new feature for the Freechat and FreechatDAO community or its processes or environment. The FIP should provide a concise technical specification of the feature and a rationale for the feature. The FIP author is responsible for building consensus within the community, documenting dissenting, and updating the status of the FIP.
FIP Rationale
We intend FIPs to be the primary mechanisms for proposing new features, collecting technical input on an issue, and documenting design decisions that have gone into the Freechat and FreechatDAO community. Because FIPs are maintained as text files in a versioned repository, their revision history is the historical record of the function proposal.
For Freechat and FreechatDAO community implementers, FIPs are a convenient way to track the progress of their implementations. Ideally, each implementation maintainer would list the FIPs they have implemented. This will provide a convenient way for end users to know the status of a given implementation.
FIP Type
There are 3 types of FIP：
Function FIP
A Function FIP describes any change that affects most or all Freechat and FreechatDAO implementations, such as— the development of new features, changes in functionality, fee rate rules, changes in community governance, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using
Freechat and FresschatDAO. Standard function FIPs consist of five parts -an idea draft, an implementation document, a technical implementation, a feature living, and a feature withdrawn.
Function FIP Numbering Definition
For the convenience of distinguishing the type of each FIP, the FIP number is defined as follows：
Functional FIP Head Number：5
（For example51、5001、50001、500001, etc.）
Function FIP-Related Definitions
Idea Draft： Any draft idea should be discussed first, and the status of the draft can be changed at will. Form ideas into implementable documents, such as product prototypes, development documents, etc., and vote through community proposals. After passing, the proposals will be transformed into implementation documents.
Implementation Document： After the idea draft is approved through community voting, it will be organized into an implementable FIP document, and the community development team will conduct the technical implementation.
Valid: After the technical implementation is completed, the corresponding FIP status changes to Valid.
Invalid: The community decides to withdraw the proposed FIP, the community development team will remove the function and the status changes to Invalid
Mechanism FIP
A Mechanism FIP describes the process or proposed changes to the process (or events, business model, and governance scheme in the process) around Freechat and FreechatDAO community. Mechanism FIP applies to areas other than Freechat and FreechatDAO community itself. They may propose an implementation, but not to freechat and FreechatDAO’s codebase; they often require community consensus; any mechanism FIP is also considered a business decision FIP and a community governance FIP.
Mechanism FIP Numbering Definition
For the convenience of distinguishing the type of each FIP, the FIP number is defined as follows：
Mechanical FIP Head Number：1
（For example1、12、103、1004、10005、100006, etc.）
Mechanism FIP-Related Definitions:
Draft： Any draft should be discussed first, and the draft status can be changed at will. After the draft has passed, it will be collated into an implementable mechanism FIP document, which will be implemented by the community development team or the community.  Its status will be changed to Valid.
Valid: The status of the community-approved mechanism FIP is valid.
Invalid: The status of Mechanism FIP that needs to be abandoned is invalid.
FIP Information FIP:
Information FIP describes Freechat design issues and provides general guidelines or information to the FreechatDAO community but does not propose new features. Information FIP does not necessarily represent the consensus or recommendations, so users and implementers are free to ignore the information FIP or follow its advice.
Information FIP Numbering Definition
For the convenience of distinguishing the type of each FIP, the FIP number is defined as follows：
Informative FIP Head Number：9
（For example9、92、903、9004、90005、900006, etc.）
FIP Status
FIP statuses are divided as follows:
Function FIP status： Draft, Implementing, Valid, Invalid
Mechanism FIP status： Draft, Valid, Invalid
Information FIP status:    None
FIP Flow Chart
FIP Execution Flow Chart

What does a successful FIP contain？
Every FIP should contain the following parts:
Header Preamble
Contains FIP number, Title, Description, Status, Type, Author, link, Created time, and Modified time.
Time Format：（YYYY-MM-DD）
Author Format： Name（Email）
Description of motivation or ideas etc.
Motivation, ideas, creativity, and community governance are critical to Freechat and the FreechatDAO community protocol. It should clearly explain why the current protocol specification is inadequate to address user needs.
Implementation Details (e.g., product prototypes, development documentation, etc.）
Implementation details describe the design rationale and should be formed into readable product prototypes, development documents, etc. for easy reading and understanding. The Author should create a community proposal and form implementation documents for rapid development and execution.
Copyright Waiver
Copyright waiver - The FIP uses Ethereum's license agreement to make the declaration. All FIPs must be in the public domain. The copyright waiver Must link to the license file and use the following wording:
Copyright and related rights waived via CC0
FIP Templet
Templet Link：https://fips.freechat.world/jian-ti-zhong-wen/fip-template
Format of Submitting Proposal
Community Governance Link： FeechatDAO
In order to unify and facilitate the reading, the following format should be followed when initial proposals to the community:

fip: Number of FIP (defined according to the FIP numbering scheme)
Title: Title of FIP
Description: a short description of FIP
Type: type of FIP (function, mechanism, information）
Author: FIP creators and editors
Created time: YYYY-MM-DD
Modified time: YYYY-MM-DD
Community Governance Discussion Group Link
Chinese：https://s.freechat.world/6cEgqXUi
English：https://s.freechat.world/NFBEg6nj

Freechat Gitbook Fips:
https://fips.freechat.world/jian-ti-zhong-wen/fip-1/fip-1
Comments: This option links to the corresponding FIP in Github. e.g., FIP-1 corresponds to the GitHub address.
Proposal content: Copy the contents of the FIP. Please change the images in the proposal to the corresponding FIP image address if it contains pictures.
Copyright Waiver
Copyright and related rights waived via CC0

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

