Partial list. Full dataset available on request.
The Mission of Filecoin is to create a decentralized, efficient, and robust foundation for humanity’s information.
Implementation teams (Protocol Labs, ChainSafe, IPFSForce, Soramitsu)
Mining businesses (many)
Ecosystem development businesses (Textile, Infinite Scroll, etc)
No restrictions to participation.
Within the Filecoin Economy, there are three distinct markets, and participants in the network exchange different goods or services. In the storage market, storage miners offer to rent out digital storage that will be verified by the Filecoin Network. Conversely, storage clients offer filecoin to have their data stored. This storage is priced based on the amount of storage space used and the duration of the contract in time. There is a retrieval market, where clients pay filecoin to retrieval miners to provide them with a copy of the data. Lastly, token exchanges could enable participants to trade to put filecoin in the hands of clients, miners, and other token holders.
FIP Editors: https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0001.md#fip-editors
Filecoin Core Devs: All implementation devs + members of core research Labs (cryptoecon, proofs, network research, etc)
Goals and Implementation
Adding capacity to the Filecoin network: block reward
Storing useful data on the Filecoin network: FIL+ multiplier on block reward
Creating applications on Filecoin to boost utility of the ecosystem: Hackathons, devgrants, accelerators, and ecosystem funds
Loaning Filecoin tokens to miners: APY on lent filecoin
https://github.com/filecoin-project/FIPs - the majority of proposed FIPs have been accepted, FIP authorship extends across 6+ different organizations
Devgrants from the Filecoin Foundation pay for many infra services, dev projects, etc. https://fil.org/grants/
FIPs are the official decision-making venue for protocol upgrade decisions and organizational process decisions that affect the entire community.
Anyone can ship a new FIP
FIPs must be valid/complete and get approval from the community and core devs to be accepted.
Core devs are responsible for implementing technical FIPs (across implementations) once accepted.
There is a polling tool, but there isn't an explicit judiciary process yet.
Anyone can propose a FIP, core devs have a check on community proposals for what gets implemented in official releases (they hold each other in check), miners decide which new implementation releases they accept (holding the core devs in check).
There is a polling system for miners/clients/ecosystem devs to signal their support (or rejection) for a FIP: https://filpoll.io/
In emergency situations, we don't wait the full timeline between posting/accepting/shipping a FIP across implementations.
No? FIPs can cover any aspect of technical or governance process.
Having multiple independent implementations requires more agreement and alignment between core devs on the problems to solve and how.
There are new organizational FIPs in the works to upgrade existing documentation/FIPs.