-
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:STCloud #1038
Comments
Hi @stcloudlisa |
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?: On the data front, we actively communicate with enterprises and persuade them to store their data in the Filecoin network. For example, with our assistance, ""gouhong"" participated in e-fil+ and ""China Auto Parts Network"" joined FIL+. We also help our partners download and store public datasets. Therefore, in the past two years, our DataCap has been diverse, abundant, and unique. At the algorithm level, we have developed our own data processing system that automatically deduplicates all data. We do not want to see any sharing of Content Identifiers (CIDs) as it would waste DataCap and harm the reputation of FIL+. Additionally, we have developed platforms for handling DataCap and submitting orders, enabling better end-to-end tracking of DataCap usage. At the implementation level, we have established the ST-DC project, which conducts auditing, tracking, and management for both new and existing customers. This is the application link : https://github.com/stcloudlisa/STDC/issues/new/choose. 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?: In our due diligence process, we primarily focus on the following aspects regarding customers:
We also gather and analyze publicly available information, such as corporate news reports, social media platforms like Twitter and LinkedIn, and analysis and ratings from professional organizations, to understand and assess the true situation of the enterprise. Furthermore, we employ various methods, including KYB (Know Your Business), to verify the authenticity of the information submitted by customers. This may involve using publicly accessible corporate information search systems, securities regulatory authorities, third-party business databases such as Twitteraudit, Dun & Bradstreet, Bloomberg, Hoover's, and more. 12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.: Company name Social media Company introduction Requested total amount of DataCap Expected size of individual datasets (per copy) Number of copies to be stored DataCap allocated per week On-chain address of initial allocation Data type of your company Amount of data your company has How do you prove ownership of the data Please provide data use cases Are you applying for FIL+ or E-FIL+ Is the data being stored on Filecoin for the first time Why do you want to store data on the Filecoin network Which regions do you want your data to be stored in How many backups How did you learn about us Do you have experience with data handling How will you handle your data Please introduce your technical team Do you need assistance from us If you already have a list of storage providers to work with, fill out their names and provider IDs below How will you negotiate the deals with the SPs When do you expect to start How long do you want to store the data What retrieval frequency do you desire Can your data be publicly retrieval Can you confirm that you will follow the Fil+ guideline 13. Will you use a 3rd-party Know your client (KYC) service?: Integrating KYC services into our workflow involves securely transmitting the necessary customer information to the service provider for verification. This may involve sharing customer files and data through secure channels or APIs provided by the KYC service. The service provider then performs the necessary checks and verification processes to validate the provided information and provides us with a comprehensive report or confirmation of the customer's identity. The main KYC tools used include LinkedIn, Twitter, Facebook, Namescan, Toggle, Uqudo, Qichacha (企查查), national information query systems, and more. The specific KYC service providers may vary depending on the regulatory requirements of the customer's jurisdiction. We prioritize partnering with reputable and reliable KYC service providers to ensure the security and privacy of customer data during the verification process. When conducting KYC, we primarily focus on the following aspects:
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?: We will use KYB services to verify our corporate customers. The key to verifying data ownership is as follows: Therefore, we emphasize verifying the identity of the applicant and the company's operational situation. In the following verification process, we will utilize KYB services: 1.Verify that the applicant is representing the company in the application: Confirm the legitimacy of the applicant representing the company by verifying their identity documents and authorization documents, such as admission notices, employment contracts, payslips, etc. This may require the use of third-party KYB services to verify the applicant's identity and employment status. 2.Verify that the applicant is representing the company in the application: To ensure that the applicant is indeed representing the company, you can request the applicant to send an email using the company's domain email address and attach the company's data license certificate stamped with the company's seal. By matching the email address with the one reserved on the company's official website, the identity and authorization of the applicant can be verified. 3.Verify the amount of data owned by the company: Validate the amount of data owned by the company. This step requires the company to provide relevant data storage records, backup strategies, data management documents, and screenshots of the total data storage on platforms such as AWS. By comparing the provided data volume with the requested capacity, it can be confirmed whether the company's data ownership aligns with the application. 4.Third-party KYB investigation: Conduct a KYB investigation through a third-party service provider to examine the company's operations, data management strategies, backup plans, and compliance with data ownership regulations. This can provide additional verification and background information to ensure the legality and credibility of the customer. 5.Contract signing: Signing a contract with the customer is a crucial step in ensuring data ownership and legality. The contract should clearly outline the customer's data volume, provisions regarding data ownership, and requirements for the public accessibility of data stored on Filecoin. Customers must adhere to the contractual provisions to ensure the integrity and compliance of the data. We will conduct ongoing audits and reviews to ensure their continuous compliance with data ownership and legality standards. This includes regular checks and verification of the data provided by the customer and monitoring the implementation of their data management and backup strategies. 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:: For the first time, 50% of the weekly quota is allocated; After checking and everything is reasonable and in compliance with the allocation rules, we will allocate the next round of quotas to the customer. 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?: The ST-DC application form will be stored on Github. Github's open and transparent approach not only keeps our allocator open, it also makes our activities and decisions easily accessible to community members and the Fil+ governance team. Some private information will be reflected in Slack communications, and important contract documents (ID cards, legal person information, contracts, data authorization statements) may also be retained via email. At the same time, based on any conclusions or major conclusions generated in private conversations, Decisions will be summarized and published on GitHub. If there is a dispute, we are willing to share documents from the private conversation with the governance team. Risk Mitigation, Auditing, Compliance37. Describe your proposed compliance check mechanisms for your own clients.: Tracking DataCap distribution metrics: We will closely monitor metrics related to DataCap distributions, such as the number of distributions, retrieval rate, and address location distribution. Understand customer demographics and timing metrics: We will query specific SP numbers and distribution through datacapstats.io. We will also track timing metrics related to DataCap requests, allocations and utilization to evaluate the efficiency and responsiveness of our processes. . Trust Rating: Customers must fill out an onboarding application and undergo an onboarding check. To receive a larger DataCap allocation, customers are required to provide data processing experience. Use of automated tools: Tools such as CID Checker and Retrievability Bot will be used to automatically monitor and verify the integrity and retrievability of stored data. New Customer Policy and Tolerance: New customers will be subject to stricter scrutiny than existing customers. We need to clearly know who they are, their purpose of obtaining DC, and the interest groups behind them. They will need to provide evidence of their ability to responsibly load data onto the Filecoin network. This may include proof of previous small-scale data coming online. In ST-DC allocator, the DC received by new customers in the first round should not exceed 250TiB. When allocating them to the second round, we need to comprehensively and detailedly check their first round allocation plan. We can accept that customers do not understand technology, and we are willing to provide them with technical assistance, but we cannot accept that they abuse DC and use lies to obtain DC. Therefore, if a dispute arises, we will immediately stop the issuance of DC. 38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.: Submit and track disputes on GitHub: All disputes are systematically tracked and logged on GitHub. This approach ensures transparency as the wider community can understand the details of the dispute and our response. Discuss the dispute on Slack or Zoom: If the dispute expands and the community begins to discuss the dispute on Slack and gets into a fierce fight, we will invite the governance team to join in, conduct a zoom meeting, and handle the dispute as soon as possible. Response time: We will respond to questions and handle disputes within 24 hours. 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?: We will adhere to the principle of community self-governance and respect the opinions of the community. We will publish change notifications on GitHub, Slack, and Twitter, allowing a minimum of 15 days for community feedback. For significant changes, we will provide more time for discussion, with a minimum of 60 days. Not all changes will be implemented. the larger the change, the more importance we place on the opinions of the community and the governance team. If there is significant opposition, we will not proceed with the change. 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.: To achieve this, we may implement relatively low fees that cover the operational costs of the ST-DC Allocator team. Based on our considerations, we may set the pricing at 0.8 FIL/T, which includes: In addition, we have developed discounts specifically for premium customers, with discounts stacking up to a maximum of 60%:
Consequently, the highest discount can reach up to 60%, with most discounts ranging from 30% to 50%. On average, the fee pricing could be approximately 0.45 FIL/T. 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/bafy2bzacedilzwhn7ghbz4xryfaw7tbajcgdyc3sw5xuuml4p64cxhxcxabra |
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: