-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notary Application : Filecoin Foundation #187
Comments
Updated formatting for readability |
Previous applications: |
Allocation track record from last round:
Client applications and usage of datacap: DataCap received by miner IDs:
|
Hi @tinkmk - thanks for submitting your application to be a Notary! The initially scored rubric can be found here: Please take a look at the notes (column I) and share any relevant additional details here in comments so we can update your score ideally within the next 2 days. Your initial unrounded score is: 3.2. |
@tinkmk, the final scores therefore for this election cycle are:
Link to rubric: We need a final confirmation on region before proceeding with finalizing scoring or election: EU/NA? |
Hi @dkkapur, The Filecoin Foundation would like to stay in the EU region, since this is the region where we have done our previous notary work we think that we think we would be more effective in this region than moving to NA, so we can use the expertise we've developed allocating data cap for EU clients in this next round. |
@tinkmk - based on this Notary election cycle's final scoring, you/your organization has qualified to be a Fil+ Notary! Per your application and the scored rubric, you will be receiving an allocation of 1 PiB. In order to confirm your participation as a Notary in the Fil+ ecosystem, please respond to the following:
|
@tinkmk - awaiting your response to the above before proceeding with next steps with the RKH. Thanks! |
Please confirm that the region of operation for client applications you will focus on is [Europe] Confirming Europe as region of operation Please confirm each of the following items below (you can do this by quoting each of the following bullets and adding a line under each section agreeing that you'll abide by these operational principles. Upfront Disclosures: Prior to being confirmed as a Notary, Notaries are expected to disclose all relevant addresses which they control, have a financial stake in, or are strongly connected to by other means. For the disclosure, the Notary should state the relevant addresses and the nature of the relationship Promoting Client Best Practices: Notaries agree to educate approved clients about the best practices for using their DataCap (e.g. how to request additional services from miners, storing data redundantly across many miners, etc). Some reference information can be found here. Commitment to efficiently serving the Network: Notaries agree to serve as fiduciaries of the Network, striving to work towards bringing useful data onto Filecoin and improving the experience for clients to do so. Notaries should generally be able to respond to Client applications and updates within 3 days, and should be comfortable communicating with Clients and Notaries if an application needs to be redirected. I agree to the above statement No Self Dealing: To prevent conflicts of interest, Notaries should not allocate DataCap to Clients over which they control the private keys, or to a Client who intends to specifically spend the allocated DataCap with an address affiliated with the Notary. When in doubt, Notaries should bias towards transparency (i.e. public disclosure) or to getting a different Notary to handle the individual request. I agree to the above statement Operating in Good Faith: Notaries hold a position of trust in the network, and as such it is expected that they operate keeping the Principles of this mechanism in mind. While each form of abuse cannot be exhaustively defined, Notaries are expected to bias towards caution and act in a way that promotes transparency. Notaries should expect to potentially receive requests or questions for allocation decisions (within reason) - and should make decisions with this in mind. I agree to the above statement Community Governance Participation: It is expected that Notaries make an effort to regularly attend the scheduled Governance calls. As these calls are a forum to shape this process, it is important to ensure Notaries are present to provide their context, learnings, and input. I agree to the above statement Please list any addresses you are affiliated with, and state the nature of the relationship. Please refer to the first bullet point in (2) for the definition of "affiliated", and bias towards transparency when in doubt. Please affirm that you will abide by the allocation / client due diligence plan you laid out above. Agreed (If ready) Please confirm the address that should receive DataCap. This is the address which you will use to sign messages on-chain to verify clients (through using a Ledger and the Fil+ Registry App). If you have an active (non-zero) DataCap grant from a previous election cycle, please provide a different address here. f1k6wwevxvp466ybil7y2scqlhtnrz5atjkkyvm4a In the case of the Filecoin Foundation - there is an existing allocation of ~8.5 TiB that was stated to not be allocated in the future. Can you confirm this will remain the case, and we can request the RKHs to remove that previous allocation? If not, you will only receive 1024 - 8.5 = 1015.5 TiB in this cycle. I can confirm this is the case |
Request ApprovedAddress
Datacap Allocated
|
The request has been signed by a new Root Key HolderMessage sent to Filecoin Network
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced4c3sfnj37n3nhaqzoqj45bjfh4mxtlaavivvqmjh5yyqykaprjg |
The request has been signed by a new Root Key HolderMessage sent to Filecoin Network
@dkkapur There was an error processing the message >bafy2bzacebfboa5pvtvmffdqytlwa4w7auyn5rgk5qefiwpf22bgwgoofxvzeYou can check the status of the message here: https://filfox.info/en/message/bafy2bzacebfboa5pvtvmffdqytlwa4w7auyn5rgk5qefiwpf22bgwgoofxvze |
This grant seems to have gone through correctly and should not be in Error status. Fixing this now! |
@tinkmk - can you please confirm the correct GitHub account we should be using to assign incoming client applications to the Filecoin Foundation? |
Hi @dkkapur -- I'll be managing the Filecoin Foundation datacap request process. My github account is https://github.com/dannyob Thanks! |
Notary Application
To apply as a notary, please fill out the following form.
Core Information
Please respond to the questions below in paragraph form, replacing the text saying "Please answer here". Include as much detail as you can in your answer!
Long Term Network Alignment
Time Commitment
Describe the nature and duration of your affiliation with the Filecoin project. Please include relevant Github handles, miner ids, significant projects or contributions (with links).
Stake Exposure
Please cite total token at stake (currently available, locked as collateral, vesting over time) and any substantiating evidence.
Industry Reputation
In-protocol Reputation
Please describe (in detail) your activity and tenure as a member of the Filecoin community. Please note (with links where possible) any contributions made to implementations of Filecoin, the spec, documentation, or to substantially help the Filecoin ecosystem grow.
In-protocol Security
Please describe your contributions to the security of Filecoin and the duration over which you've made contributions. Please also include any links or references who might be able to substantiate your contributions (e.g. if you've filed several bugs, please cite who you've communicated with on the Filecoin side).
External Reputation
Please describe the nature of your organization, including the country of registration, size of the organization, and time since inception.
Please share any relevant details to help substantiate information about your organization (website, named officers, links to social media profiles).
Diversity and Decentralization
Use Case Diversity
(Optional) Any additional information you'd like to share about the use case(s) you plan to support?
Allocation Plan
Concreteness of Allocation Plan
Allocation Strategy
How do you plan on allocating the DataCap requested above? Please describe your allocation strategy with as much specificity as you can.
Are there any internal processes you plan on implementing regarding the target, amount, or rate at which you'll allocate DataCap?
How do you plan on securing the DataCap to ensure your organization (and its delegated members) are the ones allocating the DataCap?
Client Due Diligence
How will you vet your Client to ensure they are spending that DataCap responsibly?
What questions will you ask to ensure the Client can properly handle the DataCap you intend to allocate to them?
What processes will you employ to confirm that a Client is not improperly over-allocating DataCap to a single entity?
Bookkeeping Plan
Do you plan on keeping records of your allocation decisions? If so, with what level of specificity do you intend to respond to any audit requests?
Do you plan on conduct your allocation decisions in public (e.g. Github repo), private (e.g. over email, Telegram, etc), or both?
Track Record
Past allocation
Have you previously received DataCap to allocate before? If so, please link to any previous applications.
Cumulatively, how much DataCap have you previously successfully allocated?
Have there been (or are there still) any disputes raised against you from your previous DataCap allocations?
The text was updated successfully, but these errors were encountered: