-
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: MathWallet #123
Comments
Previous applications: Allocation track record from last round:
Client applications and usage of datacap: DataCap received by miner IDs: |
Hi @rayshitou - 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: 1.8. |
Thank you, @dkkapur |
@rayshitou - thanks for sharing this. Based on this, the following adjustments were made:
The final scores therefore for this election cycle are:
Here is the link to the updated rubric: https://docs.google.com/spreadsheets/d/1baQQNZ_tNa18b6w4yxYMy3OFXP-SFNaVEOe_L3oapog/edit?usp=sharing |
@rayshitou - as shared in the last Governance call, 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: 100 TiB. In order to confirm your participation as a Notary in the Fil+ ecosystem, please respond to the following:
|
@dkkapur thank you very much!
|
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/bafy2bzaceaysvw74kl5j4u2ikvpbtianm7ltp3sic4dbwseh2zddnxu4x5tpg |
The request has been signed by a new Root Key HolderMessage sent to Filecoin Network
@dkkapur There was an error processing the message >bafy2bzacecdrzuawh4vvtjpzn6amhoom4rp6vdwq5nguwtafnvptw7l7iw4riYou can check the status of the message here: https://filfox.info/en/message/bafy2bzacecdrzuawh4vvtjpzn6amhoom4rp6vdwq5nguwtafnvptw7l7iw4ri |
This went through correctly |
Notary Application
Core Information
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).
Please share any relevant external information regarding your organization (e.g. news articles, social media profiles, etc.)
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 impelementing 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: