The purpose of this repository is to manage the governance and evolution of specific Mechanisms and Operations of the program as insantiated in this FIP and illustrated in the following diagram.
Within this repository, you will find:
- Increased specification, governance, and evolution for Mechanisms and Operations layers.
- Information on Root Key Holders, available actions, roles and responsibility.
- Information on how to become a Notary, selection rubric, recommended guidelines, active Notaries.
- Information on how to file a Dispute, and the steps for how disputes are resolved.
If you are looking to request DataCap or to find a list of active Notaries please go to the Filecoin Plus Registry.
- Principles
- Decentralization and Diversity
- Tranparency and Accountability
- Community Governance
- Low-Cost Dispute Resolution
- Limited Trust Earned over Time
- Terms of Service
- A Useful Storage Network
- Roles & Responsibilities
- Root Key Holders
- Notaries
- Clients
- Interaction Diagram
The process for filing a Dispute / Audit request is as follows:
- An issue must be filed detailing the following information:
- Who is the Dispute / Audit request against?
The submission must include the on-chain addresses of the parties involved and the name of the Notary involved (if applicable).
- Why is the request being filed?
A concise description detailing the issue at hand. Notably some specific harm must be detailed (either a violation of the overarching principles, a violation of a Notary's own attested allocation plan, a violation of the agreed upon operating guidelines, or some other act of impropriety.
- What is the substantiating evidence?
Links to the relevant transaction ids or other substantiating evidence.
-
Once an issue has been filed, the community will review the submission to affirm the legitimacy of the claim. Issues that are not properly substantiated may require additional information or be closed.
-
If an issue is filed and has substantial evidence, a Notary will have 5 days to provide a response in the same issue.
-
Based on the evidence and the response, the community can adjudicate on the severity of the issue at hand at the next governance call - or pending an imminent need an emergency governance call may take place. If there is a flagrant violation of the Principles, operating guidelines, or other foundational items - a Notary may be subject to removal. If the violation is of a smaller scale, the Notary may simply be given a warning (and this repo may receive a PR to provide clarity for other Notaries). Auxillary information (including evidence that the Notary acted in good faith) should be considered as well.
Within this repository are the governing documents, selection criteria, and processes for Notaries and Root Key Holders. Areas for discussion or improvement, should be filed as issues. Please use the Modification template (for proposed improvements) or create a blank issue for topics for discussion!
After community discussion, pull requests are encouraged where open discussion can happen asynchronously via the community - please be sure to link the relevant issues to the changes in your PR. Similar to a FIP, any proposed changes must be done within the constraints of improving the Mechanisms and Operations to better meet the overarching Principles.
Please note our community governance calls will take place every other Tuesday - alternating every meeting between 3pm UTC and 11pm UTC. Please see the community calendar for the accurate dates, follow the repo (where agenda issues will be filed), or join our Slack channel!
- Community Calendar
- Zoom link, Passcode: 554538
- Please join our Slack channel, #fil-plus, if you have questions.
- 2021-05-11: Meeting recording
- 2021-04-27: Meeting recording
- 2021-04-13: Meeting recording
- 2021-03-30: Meeting recording
- 2021-03-16: Meeting recording
- 2021-03-02: Meeting recording
- 2021-02-16: Meeting recording
Meetings can also be found with the following Miners for longer term storage
| Meeting Date | Payload CID | Miner | Deal CID |
|---|---|---|---|
| 2020-02-16 | bafykbzacecqd3namsecd6takdpfcvlecs4u5q4v3vdaor7655hfxjdvm2ui4m | f023971 | bafyreicxnigp25uarpnq2qir7vxpyc4rtznhinb34tzl4hzzg3xtk62cya |
| 2020-02-16 | bafykbzacecqd3namsecd6takdpfcvlecs4u5q4v3vdaor7655hfxjdvm2ui4m | f022142 | bafyreifddfguvyaakx3c6c2xcw7mur27iqswdysi2yfeayzacr4tcednne |
| 2020-02-16 | bafykbzacecqd3namsecd6takdpfcvlecs4u5q4v3vdaor7655hfxjdvm2ui4m | f019551 | bafyreig6bl3btlmykthademdht3lt7mb4ee5x2catdubd3zfmnbotzv4ya |
| 2020-02-16 | bafykbzacecqd3namsecd6takdpfcvlecs4u5q4v3vdaor7655hfxjdvm2ui4m | f010617 | bafyreibmqamxqvoygdadutipndz76whnzmqnu2hmpoirc5jn5mejhxlzru |
| 2020-02-16 | bafykbzacecqd3namsecd6takdpfcvlecs4u5q4v3vdaor7655hfxjdvm2ui4m | f01247 | bafyreihuhonuijahda6g37it3lkhvmna66nrzmwphm7nx3kpsxnrcqgecy |
| 2020-02-16 | bafykbzacecqd3namsecd6takdpfcvlecs4u5q4v3vdaor7655hfxjdvm2ui4m | f023467 | bafyreibna5cjwktmntazlpxiezijwrybihhgumuah5uveoqpjxkwz2bleu |
Notes from prior meetings can be found here: https://docs.google.com/document/d/1gLMtS7OcII0KDaoVNCuP9ymOXpofVvsiK1CssfUbFFk/edit?usp=sharing