CFP DFIP

From DeFiChain-Wiki
Revision as of 18:55, 21 September 2022 by SaschaGLM (talk | contribs) (Komplett neu)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

DFIPs and CFPs

DFIP = DeFiChain Improvement Proposal - CFP = Community Fund Proposal

DFIPs and CFPs are a large part of DeFiChain. Aside from normal development activity from the developers, there is also activity from the community, which should happen either way, as the point of decentralization is that the community takes part of the development, not a centralized team deciding on the development.

Both DFIPs and CFPs are supposed to be discussed on Reddit to get an overview about the community's sentiment concerning that idea. After that the requester can put the CFP/DFIP on github. Usually once a month the masternodes vote on the CFP/DFIPs and confirm or reject them.

DFIPs

DFIPs are made to improve DeFiChain itself in general with improvements to features/new features or rules implemented by the developers.

An example of a DFIP would be using futures contracts to solve the premium of tokenized stocks on DeFiChain (read more about DFIP-2203-A), or allowing tokenized Ethereum to be used in a vault (read more about DFIP-2203-B).

To avoid not-serious DFIPs there is a fee of 50 DFI to be paid as soon as a DFIP is put online.

CFPs

CFPs are community proposals that community members create. Community proposals are used to get funding from DeFiChain's Community Fund, which is created by masternodes' block rewards. Community members can request funding for a DeFiChain project with which they want to add value to the project. Many community projects that are found in DeFiChain are partly funded by our community fund.

To avoid not-serious DFIPs there is a fee of 1% of the requested amount of DFI to be paid as soon as a CFP is put online.

Discussions about CFPs

Currently there are discussions within the community how to proceed with for-profit-CFPs and if they should be funded as the community would take the risk and the requester gets the upside.