-
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
v5 Notary Allocator Application: CoinSummer Labs #1060
Comments
Hi @maxvint Thanks for submitting to become an Allocator! Wanted to confirm that this initial application was received. Once you complete and submit your complete Airtable form, the application will have the responses posted to this Github and be ready for scoring. As a reminder - the completed application deadline is 20Jan. |
I have submitted the include Airtable (form). |
Basic Information1. Notary Allocator Pathway Name: 2. Organization: 3. On Chain Address for Allocator: 4. Country of Operation: 5. Region(s) of operation: 6. Type of Allocator: 7. DataCap requested for allocator for 12 months of activity: 8. Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing?: Key aspects include:
9. As a member in the Filecoin Community, I acknowledge that I must adhere to the Community Code of Conduct, as well other End User License Agreements for accessing various tools and services, such as GitHub and Slack.: Client Diligence10. Who are your target clients?: 11. Describe in as much detail as possible how you will perform due diligence on clients. If you are proposing an automated pathway, what diligence mechanism will you use to determine client eligibility?: Detailed Criteria:
12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
After approval, keep an eye on datacap usage:
13. Will you use a 3rd-party Know your client (KYC) service?: Service Functionality:
Integration and Data Handling:
In essence, the integration of third-party KYC services significantly bolsters our due diligence mechanism, providing a more thorough and streamlined client risk assessment and ongoing monitoring process. 14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral): 15. How do you plan to track the rate at which DataCap is being distributed to your clients?: Data Diligence16. As an operating entity in the Filecoin Community, you are required to follow all local & regional regulations relating to any data, digital and otherwise. This may include PII and data deletion requirements, as well as the storing, transmit: 17. What type(s) of data would be applicable for your pathway?: 18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?:
Third party KYB services:
19. How will you ensure the data meets local & regional legal requirements?: 20. What types of data preparation will you support or require?: 21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
Data Distribution22. How many replicas will you require to meet programmatic requirements for distribution?: 23. What geographic or regional distribution will you require?: 24. How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?: 25. Do you require equal percentage distribution for your clients to their chosen SPs? Will you require preliminary SP distribution plans from the client before allocating any DataCap?: 26. What tooling will you use to verify client deal-making distribution?: 27. How will clients meet SP distribution requirements?:
28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?: DataCap Allocation Strategy29. Will you use standardized DataCap allocations to clients?: 30. Allocation Tranche Schedule to clients::
31. Will you use programmatic or software based allocations?: 32. What tooling will you use to construct messages and send allocations to clients?: 33. Describe the process for granting additional DataCap to previously verified clients.: 34. Describe in as much detail as possible the tools used for: • client discoverability & applications • due diligence & investigation • bookkeeping • on-chain message construction • client deal-making behavior • tracking overall allocator health • disput:
Tools and Bookkeeping35. Will you use open-source tooling from the Fil+ team?:
36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?: Risk Mitigation, Auditing, Compliance37. Describe your proposed compliance check mechanisms for your own clients.:
38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
Through this structured approach, we aim to resolve disputes efficiently and fairly, ensuring the integrity and health of the network. 39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.: 40. How long will you allow the community to provide feedback before implementing changes?: The process of community interaction, moderation, and feedback balancing will proceed as follows:
This systematic approach aims to strike a balance between decentralized participation and operational efficiency, ensuring that community members have a meaningful role in key decision-making processes. 41. Regarding security, how will you structure and secure the on-chain notary address? If you will utilize a multisig, how will it be structured? Who will have administrative & signatory rights?: 42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?: Monetization43. Outline your monetization models for the services you provide as a notary allocator pathway.:
All service fees and pledge requirements will be clearly communicated to clients before the commencement of services. Regularly assess and adjust the fee structure to ensure competitiveness and service quality. 44. Describe your organization's structure, such as the legal entity and other business & market ventures.: 45. Where will accounting for fees be maintained?: Past Experience, Affiliations, Reputation46. If you've received DataCap allocation privileges before, please link to prior notary applications.: 47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.: 48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?: |
Datacap Request for AllocatorAddress
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/bafy2bzacedybuh6uteb2w6mz2eckjx2jzjyecf7psgta3bib4sl5tj5hchrse |
v5 Notary Allocator Application
To apply to be an allocator, organizations will submit one application for each proposed pathway to DataCap. If you will be designing multiple specific pathways, you will need to submit multiple applications.
Please complete the following steps:
1. Fill out the information below and create a new GitHub Issue
2. Access allocator application (download to save answers)
Click link below to access a Google doc version of the allocator application that can be used to save your answers if you are not prepared to fully submit the application in Step 3. https://docs.google.com/document/d/1-Ze8bo7ZlIJe8qX0YSFNPTka4CMprqoNB1D6V7WJJjo/copy
3. Submit allocation application
Clink link below to access full allocator questionnaire and officially submit your answers:
https://airtable.com/appvyE0VHcgpAkt4Z/shrQxaAIsD693e1ns
Note: Sections of your responses WILL BE posted back into the GitHub issue tracking your application.
The final section (Additional Disclosures) will NOT be posted to GitHub, and will be maintained by the Filecoin Foundation.
Application information for notaries not accepted and ratified in this round will be deleted.
The text was updated successfully, but these errors were encountered: