Forums and FIPs
Connect with the Filecoin community in discussion forums or on IRC. The Filecoin community is active and here to answer your questions in your channel of choice.
Last updated
Was this helpful?
Connect with the Filecoin community in discussion forums or on IRC. The Filecoin community is active and here to answer your questions in your channel of choice.
Last updated
Was this helpful?
For shorter-lived discussions, our community chat open to all on both Slack and Discord:
For long-lived discussions and for support, please use the instead of Slack. It’s easy for complex discussions to get lost in a sea of new messages on those chat platforms, and posting longer discussions and support requests on the forums helps future visitors, too.
Filecoin improvement proposals (FIPs) are design documents that propose changes and improvements to the Filecoin network, giving detailed specifications and their rational, and allowing the community to document their consensus or dissent. All technical FIPs that are accepted are later reflected in the .
There are three types of FIPs:
Technical FIPs (FTP): protocol changes, standards, API changes. They can include core (consensus-related changes, networking (network protocol improvements, interface (API/RPC or language-level updates), or can be informational (updates to general guidelines or documentation).
Organizational FIPs (FOP): changes to processes, tools, or governance.
Recovery FIPs (FRP): emergency fixes requiring state changes (e.g., major bugs).
Typically, the FIP lifecycle looks something like this:
[ WIP ] -> [ DRAFT ] -> [ LAST CALL ] -> [ ACCEPTED ] -> [ FINAL ]
WIP: A community member has an idea for a FIP, and begins discussing the idea publicly on the Filecoin Discord, in the , or in Github issues for the relevant repo.
DRAFT: If there is a chance the FIP could be adopted, the author submits a draft for the FIP as a pull request in the .
LAST CALL: This status allows the community to submit final changes to the draft.
ACCEPTED: Once the FIP is voted on and accepted, the core engineers will work to implement it.
FINAL: This status represents the current state-of-the-art, and it should only be updated to correct errors.
It is the authors' responsibility to request status updates for the FIP. A more robust explainer of the FIP process can be found in .