v5 Notary Allocator Application: Waterdrop Lab

[amiclan666]

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

1. Notary Allocator Pathway Name (This can be your name, or the name of your pathway/program. For example "E-Fil+"): Waterdrop Lab
2. Organization Name: SSDMINER CLOUD INTELLIGENT
3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): f157xffs5vqgzfvcdwhqo7bna2cqadhxchq52mvbi
4. Country of Operation (Where your organization is legally based): Hong Kong, China
5. Region of Operation (What region will you serve?): Greater China
6. Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase): Automated/programmatic
7. DataCap requested for allocator for 12 months of activity (This should be an estimate of overall expected activity. Estimate the total amount of DataCap you will be distributing to clients in 12 months, in TiB or PiB): 120PiB

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.

[Kevin-FF-USA]

@amiclan666
Wanted to let you know this application has been received. After you complete and submit the Airtable form with your detailed Allocator plan - the public answers will be posted in a thread below. If you have any questions - please let me know.

[ghost]

Basic Information

1. Notary Allocator Pathway Name:
Waterdrop Lab

2. Organization:
SSDMINER CLOUD INTELLIGENT

3. On Chain Address for Allocator:
f157xffs5vqgzfvcdwhqo7bna2cqadhxchq52mvbi

4. Country of Operation:
Hong Kong, China

5. Region(s) of operation:
Greater China, Other

6. Type of Allocator:
Automatic

7. DataCap requested for allocator for 12 months of activity:
120PiB

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?:
Our allocator receives open-ended data and welcomes all clients who adhere to the rules. All our data will be publicly available on the GitHub community for transparency.

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.:
Acknowledge

Client Diligence

10. Who are your target clients?:
Small-scale developers or data owners

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?:
When a customer applies for a credit limit, they are required to provide SP information, node distribution locations, details on tools used including boost/market conditions, storage methods, and the allocation status of copies. Register this information into the database, and compare it with the report and KYC results during the customer's first round of reporting. Check CID sharing status, retrieve health status, and so on.

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
1.Applicant's basic information and contact details.
2.Applicant's role in this process (Data Owner/Data Preparer/Storage Provider).
3.List the basic rules of FIL+ for the applicant to review and confirm adherence to these foundational rules.
4.Disclose information about the storage provider, including email contact, node location, storage sector methodology (bare metal or distributed storage), boost/market.
5.Data processing methods.

13. Will you use a 3rd-party Know your client (KYC) service?:
We will enter all applicant information into our database, with detailed specifics as outlined in the aforementioned 12 points.

14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral):
any client

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
We have customized a monitoring tool to track customer rates

Data Diligence

16. 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:
Acknowledge

17. What type(s) of data would be applicable for your pathway?:
Public Open Commercial/Enterprise, Public Open Dataset (Research/Non-Profit)

18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?:
KYB service

19. How will you ensure the data meets local & regional legal requirements?:
Based on the content of the data request, we will inquire about data ownership, whether it is of a public data type, and the authorized usage Due to the majority of our serviced clients being in the Greater China region, we ensure compliance with China's data protection regulations, such as the 'Personal Information Protection Law.' These regulations establish rules for handling personal information, including clear concepts of data ownership and protection of the rights of data subjects.

20. What types of data preparation will you support or require?:
Public Open Dataset (Research/Non-Profit)

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
The current robot report and sampled information on SP (Storage Provider) sector orders

Data Distribution

22. How many replicas will you require to meet programmatic requirements for distribution?:
5+

23. What geographic or regional distribution will you require?:
Encourage applications to be distributed across at least 2 continents and 3 different organizations.

24. How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?:
5+

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?:
For those required, disclosure of this information is necessary, and it should be provided in advance for entry into our database. A comparison will be conducted after the first round of reports is released.

26. What tooling will you use to verify client deal-making distribution?:
CID checker bot

27. How will clients meet SP distribution requirements?:
singularity

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
Not Supported

DataCap Allocation Strategy

29. Will you use standardized DataCap allocations to clients?:
Yes, standardized

30. Allocation Tranche Schedule to clients::
• First:  200T
• Second: 500T
• Third: 1P
• Fourth: 3.2P
• Max per client overall: 5P

31. Will you use programmatic or software based allocations?:
Yes, standardized and software based

32. What tooling will you use to construct messages and send allocations to clients?:
https://filplus.fil.org

33. Describe the process for granting additional DataCap to previously verified clients.:
Allocation (SA) bot

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:
• client discoverability & applications singularity/boost
• due diligence & investigation  kyc airtable
• bookkeeping Google
• on-chain message construction Ledger 
• client deal-making behavior  Retrieve robot reports
• tracking overall allocator health robot reports
• dispute discussion & resolution github
• community updates & comms * slack，github

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
Using Singularity for Data Distribution and Monitoring

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
We will make all records public on GitHub for community review

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
We will customize and develop corresponding monitoring programs to integrate with existing robot reports, triggering them periodically. There will be a relatively high tolerance for the first round of allocation issues. There is zero tolerance for the abuse of DC situations.

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
We will promptly monitor the community's controversies regarding LDN. We believe more in letting the data speak, and if there is no way to explain the issues that arise, the rules will be automatically triggered to close. Of course, there is zero tolerance for the misuse or padding of data.

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
Utilize a combination of communication channels such as email, dedicated collaboration platforms (e.g., Slack, Microsoft Teams), and an internal portal or website. Ensure the chosen channels are accessible to all relevant stakeholders.

40. How long will you allow the community to provide feedback before implementing changes?:
A quarter of a year

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?:
We use a hardware wallet to store this private key, and only the authorized person has the right to sign.

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?:
No plans at the moment.

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
No charges were made

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
No charges were made

45. Where will accounting for fees be maintained?:
No charges were made

Past Experience, Affiliations, Reputation

46. If you've received DataCap allocation privileges before, please link to prior notary applications.:
#432

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
These may include Storage Providers, existing client applications, developer service providers, and more.

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
existing clientsDawei Sun，china

[galen-mcandrew]

Datacap Request for Allocator

Address

f2ddjxnv4bvvl6br7nuuthgk6cx5ad53jnqefszka

Datacap Allocated

5PiB

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacecjvdshardqsl3x7nzckkn3pzby6eddad6dojkywdq6vca7uta5wc

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecjvdshardqsl3x7nzckkn3pzby6eddad6dojkywdq6vca7uta5wc