filecoin-project / notary-governance

115 stars 58 forks source link

v5 Notary Allocator Application: DAHUA #1063

Open dahuajishu opened 10 months ago

dahuajishu commented 10 months ago

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+"):DAHUA
  2. Organization Name:DAHUA
  3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): f1x73gpwnreqnp3wtc77mxvi2mfki4effi37j4hhi
  4. Country of Operation (Where your organization is legally based): Greater China
  5. Region of Operation (What region will you serve?): everywhere
  6. Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase): Market-based and Manual
  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):200P

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.

dahuajishu commented 10 months ago

Forms submitted

Kevin-FF-USA commented 10 months ago

Hi @dahuajishu Thanks for submitting to become and Allocator! Wanted to confirm this application has been received along with your completed Airtable form.

ghost commented 10 months ago

Basic Information

1. Notary Allocator Pathway Name: DAHUA

2. Organization: DAHUA

3. On Chain Address for Allocator: f1x73gpwnreqnp3wtc77mxvi2mfki4effi37j4hhi

4. Country of Operation: Greater China

5. Region(s) of operation: Africa , Asia minus GCR, Greater China, Europe, Oceania, Japan, North America, South America, Other

6. Type of Allocator: Manual

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

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?: We conduct strict data review, and whether it is an individual or a company, as long as it does not violate relevant laws, your data can be stored in Filecoin. For details, please refer to the subsequent answers

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?: Individuals learning about Filecoin, 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?: Firstly, we conduct strict review of the data, including several aspects such as ownership, copyright, public disclosure, and compliance with the laws of most countries. For example, data that is not recognized by most countries, such as gambling, pornography, blood, etc., will be rejected by us Secondly, we will request a list of collaborating SPs to check if they comply with my rules And the existing template question and answer mechanism

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.: According to the existing LDN application template For example, question 11

13. Will you use a 3rd-party Know your client (KYC) service?: yes Personal data will require proper KYC of the account Enterprise data may require proof of business license or other methods

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 clients

15. How do you plan to track the rate at which DataCap is being distributed to your clients?: Every day, utilizing existing open-source tools

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 Dataset (Research/Non-Profit), Public Open Commercial/Enterprise

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 conduct strict data review, which includes several aspects: ownership of the data, whether it is publicly available, and whether it complies with the laws of most countries Ownership such as business license verification, whether there are other watermarks in the data sample, and whether these data exist on the official website, Enterprise KYB services can be searched on some national enterprise information query websites, or through Google search, Baidu in China, and so on

19. How will you ensure the data meets local & regional legal requirements?: Because this is distributed storage, there may be situations where the laws of one country allow it, while the laws of another country do not. Therefore, we will take data that is not allowed by most countries as a condition for rejection to prevent legal issues from arising

20. What types of data preparation will you support or require?: Support any type of data within the legal framework

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?: Retrieve data using existing Lotus tools and other open-source tools, compare after downloading data

Data Distribution

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

23. What geographic or regional distribution will you require?: At least in 3 different cities and 2 countries or 2 continents

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

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?: Handle according to existing rules, such as the rules of acbot

26. What tooling will you use to verify client deal-making distribution?: existing datacapstats.io tooling and the CID checker bot

27. How will clients meet SP distribution requirements?: Take distribution according to the existing mode. If you don't understand it, you can provide charged technical support

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?: In my work, I learned that many use VPN for security purposes, so I support

DataCap Allocation Strategy

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

30. Allocation Tranche Schedule to clients:: According to the existing standardization rules, but I set the overall upper limit to 10p

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?: Existing tools

33. Describe the process for granting additional DataCap to previously verified clients.: Handle with existing official tools

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: With the existing official tools, some relevant questions can be found in the previous answers. Let me briefly talk about it here • client discoverability & applications - spreadsheet tracking and meetings
• due diligence & investigation - publicly available information and meetings
• bookkeeping - spreadsheet
• on-chain message construction - current filplus.fil.org website
• client deal-making behavior - current CID checker bot
• tracking overall allocator health - current CID checker bot
• dispute discussion & resolution - GitHub notary governance repo
• community updates & comms - Slack and GitHub

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?: Yes, almost all official tools such as git hub, https://filecoin.tools/ , Google Spreadsheet, filplus checker app BOT, AC BOT, large datacap requests BOT, GitHub repository, etc

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?: Open Google spreadsheets, such as https://filecoin.notion.site/T-T-Dispute-Tracker-d28b93677cb544b48e77b585856601cf

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.: It will be reviewed every day and will use all existing official tools to support any type of data stored by new customers within the scope of the law

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.: such as https://filecoin.notion.site/T-T-Dispute-Tracker-d28b93677cb544b48e77b585856601cf Because we check the information every day, the response time will not exceed 48 hours. I stressed that we should only strictly review the data. If there is a problem with the data, we will immediately remove its datacap. Other disputes are unexpected for the time being

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.: Announce and remind in slack or GitHub

40. How long will you allow the community to provide feedback before implementing changes?: a week

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?: I will use LEDGER to protect my notarized address. Only the person in charge of technology 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?: N/A

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.: N/A

44. Describe your organization's structure, such as the legal entity and other business & market ventures.: https://www.dahuatech.com/ This is our official website, you can check it

45. Where will accounting for fees be maintained?: No monetary plan

Past Experience, Affiliations, Reputation

46. If you've received DataCap allocation privileges before, please link to prior notary applications.: N/A

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.: We already have a technology department responsible for blockchain, and filecoin also belongs to it. I hope to store our company's data in filecoin. My former colleagues have also applied for the corresponding LDN

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?: We checked a large number of LDN applications, the use of official quotas and the storage of our own data