-
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:IPFS Metaverse Community #434
Comments
Hi @ipfscn based on this Notary election cycle's final scoring, you/your organization has qualified to be a Fil+ Notary! You will be receiving your final scored rubric soon, along with the total allocation of Datacap based on rubric scoring. In order to confirm your participation as a Notary in the Fil+ ecosystem, please respond to the following:
|
@Kevin-FF-USA Thank you for the notice, we are very excited,Here are our answers. In order to confirm your participation as a Notary in the Fil+ ecosystem, please respond to the following:
• 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.
• 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.
• 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.
• Community Governance Participation: It is expected that you will participate in the program 4-6 hours a week. Along with data allocation, participation in Github issues and Slack conversations, Notaries are to 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, with discussions and input.
4.Please affirm that you will abide by the allocation / client due diligence plan you laid out above.
5.(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.
• If you do not have a ledger already, we recommend ordering directly from the Manufacturer for the Nano S or Nano X (link: https://shop.ledger.com/pages/ledger-nano-x) %E2%80%A8)
|
Please fill out this form to move forwards with the ratification process: https://airtable.com/shrs55Lzbm1wJTIRw |
@galen-mcandrew |
@galen-mcandrew、 @Kevin-FF-USA |
Hello @ipfscn! Some final verification: We have your updated address on file as: f1j4n74chme7whbz3yls4a7ixqewb6dijypqg2a3a And we will be communicating with Nic-IPFS Metaverse Community on Slack. If there are any other handles you wish to have included in communications, please comment them below. |
Notary Ledger VerifiedMessage sent to Filecoin Network
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceademfdj5qya2v3ss5hnmky75qsgfvtr3k2tlbknef56l26vjd7w6 |
HI @ipfscn |
@galen-mcandrew、 @Kevin-FF-USA |
Thanks for your request!
|
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/bafy2bzaceayv46fpe4ojvhpbcs5jmdehtqq4w7i5roia6j3ynr56dfyp5vwji |
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/bafy2bzacebkn5rwvy45yqqnd57fu7kbnv6iuufke74zzuommlpc5yppyikztu |
Notary Ledger VerifiedMessage sent to Filecoin Network
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedsldtmd5xlqsi7znahpklbal3zb7daflhzju2ehrehqdiywkw5ic |
Notary Ledger VerifiedMessage sent to Filecoin Network
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaxujh6xywntfqml4r6nid2ywp23xm7il5xyak2eeq346ujatsbwo |
Notary Application
To apply to be a Fil+ Notary, please review the Notary Overview here and then fill out the following form.
Core Information
Please respond to the questions below in pargraph 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 that can substantiate your contributions.
Organizational 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.)
Individual Reputation
Please share links to at least 2 of your (personal) social media profiles (or accounts that you are able to use) and the approximate size of your audience (i.e., followers, subscribers) for each one.
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. This includes the target amount per client and 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 the clients that are applying for DataCap? What questions will you ask to ensure your trust is placed well and that clients can properly handle the DataCap you intend to allocate to them?
What processes will you employ when granting additional DataCap to a client that has previously been verified? This includes confirming that the client is not improperly using the DataCap they were previously granted, i.e., making deals with a single SP entity.
Bookkeeping Plan
Do you plan on conducting all your allocation decisions in public (e.g. Github repo), private (e.g. over email, Telegram, etc), or both?
Where do you plan on keeping a publicly accessible record of all your allocation decisions?
Service Level Agreement
Engagement in Program
How much time per week, on average, are you willing to dedicate to participating in the Fil+ program? This includes making DataCap allocations (direct and/or Large Datasets), comments on discussion/issues, attendance in governance calls, messages in Slack, etc.
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?
The text was updated successfully, but these errors were encountered: