This repository for the Fil+ Notaries has been sunset. The updated repositority for ALLOCATORS has been created and is now maintained at Github Goverance Repo
To view other updated reference links for the Fil+ program, please see
- For information on the open and pending DataCap deals, please see FIDL's Allocator.tech
- For information on support issues or a listing of all current Allocators, please see Allocator Registry
- For getting in touch, please reach out in SLACK
- Bi-weekly recorded Fil+ governance meetings on Youtube
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
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
Last updated: 2023-05-05
The person opening the dispute is referred to as ‘Claimant’ and the stakeholder against which the dispute is opened is referred to as ‘Responder'
Overview of the Dispute resolution process:
- Claimant submits form in the T&T Dispute Tracker.
- Responder is notified by the T&T WG Lead and allowed to submit additional details in the T&T WG slack or present at the T&T WG Call.
- T&T WG reviews all relevant data.
- Repercussions announced and enacted.
The process for filing a Dispute request is as follows:
An issue must be filed on the T&T Dispute Trackerusing the form
Although the WG prefers and strongly encourage full transparency, we understand some situations may require more discretion, so disputes can be submitted as 'anonymous'.
Once a dispute is filed, the T&T WG Lead will discuss it in the WG calls. The average time for a dispute to be resolved is two weeks based on the principles of optimistic governance but some disputes may take longer depending on the complexity and response times of the claimant and responder. The status will be trackable and updated at all times in the public dispute tracker.
Claimants are encouraged to cross-post the dispute in the T&T WG channel to bring the community’s attention to the dispute.
The claimant is requested to complete all fields including a description of the issue at hand. Notably, some specific abuse must be detailed, such as:
- 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
Supporting the dispute with substantiating evidence is highly encouraged, such as links to the relevant transaction ids on-chain, screenshots, or other evidence.
Claimants are discouraged from making personal attacks against any stakeholder when submitting details in the T&T dispute tracker and follow the Fil+ Code of Conduct.
Based on the evidence, the response to a dispute, and discussions of the situation in the T&T WG calls, some possible repercussions and outcomes may include but are not limited to:
- Removal from the program
- Losing rights as a notary
- Revoking of allocated DataCap
- Being asked to step away from the Fil+ community
- A warning coupled with restrictions
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 - there are (2) calls each day to accomodate time zones. 8am PT // 1400 UTC AND 1800PT // 0000am UTC. Please see the community calendar for the accurate dates/times relative to your local timezone, follow the repo (where agenda issues will be filed), or join our Slack channel!
- Community Calendar
- Zoom link, Passcode: Notary
- Please join our Slack channel, #fil-plus, if you have questions.
- ALL: Meeting recording
- ALL: Presentation Files