Skip to content
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:ZCFIL #1009

Closed
zcfil opened this issue Dec 20, 2023 · 8 comments
Closed

v5 Notary Allocator Application:ZCFIL #1009

zcfil opened this issue Dec 20, 2023 · 8 comments

Comments

@zcfil
Copy link

zcfil commented Dec 20, 2023

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 :ZCFIL+
  2. Organization Name:ZC LABS
  3. On-chain address for Allocator: f1j5awdc2swdbrxlnn2y6txwjtiymrvuox4rexoii
  4. Country of Operation (Where your organization is legally based): China
  5. Region of Operation (What region will you serve?): Asia minus GCR,Greater China,Japan
  6. Type of Allocator, diligence process: 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):200PiB

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.

@zcfil zcfil changed the title v5 Notary Allocator Application:zcfil+ v5 Notary Allocator Application:ZCFIL Dec 20, 2023
@Kevin-FF-USA Kevin-FF-USA self-assigned this Dec 20, 2023
@Kevin-FF-USA
Copy link
Collaborator

Hi @zcfil

Wanted to let you know this application has been received. Also verifying you have completed and submitted the Airtable form with your detailed Allocator plan - the public answers will be posted in a thread below soon. If you have any questions - please let me know.

@zcfil
Copy link
Author

zcfil commented Dec 21, 2023

Hi @Kevin-FF-USA
Thank you for your response, no questions for now, thank you.

@zcfil
Copy link
Author

zcfil commented Jan 9, 2024

@Kevin-FF-USA Seems like my form info isn't posting, is there a problem?

@ghost
Copy link

ghost commented Jan 13, 2024

Basic Information

1. Notary Allocator Pathway Name:
ZCFIL+

2. Organization:
ZC LABS

3. On Chain Address for Allocator:
f1j5awdc2swdbrxlnn2y6txwjtiymrvuox4rexoii

4. Country of Operation:
China

5. Region(s) of operation:
Japan, Greater China, Asia minus GCR

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?:
Adopting pledge fil to ensure the legality, compliance, and validity of data

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, Enterprise Data 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 order to ensure the authenticity of customer information, we will verify customer information through the following contents, and assign special personnel to continuously follow up and verify after allocating DataCap
1.Browse the official website of the customer company to view the company's history, news, ecology and products.
2.Check the customer's third-party media updates, such as Twitter and Slack's social media accounts. We will observe the activity of the account and Github usage period.
3.Query the enterprise information website of the customer's country/region
4.We will require our customers to provide business license, establishment documents, public registration information and relevant certificates.
5.Our customers will be asked to provide government issued ID card or passport information.
6.We will ask our customers to provide stored sample data for review to confirm whether the data is open, stored content is legal, valid and insensitive.
7.Do not violate the laws, anti laws and regulations of the country and region where you are located and the regulations of the Filecion community,Customers with serious violations will be blacklisted by us.

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
https://form.jotform.com/230953098450156
Here are some examples of our review criteria.
Let me briefly explain our review rules. For new LDN applications, first of all, we will check the applicant's company qualifications, such as company information, official website, and scale, and verify their identity by checking the official domain email with the business license attached.
Secondly, we will check whether their data samples have value and copyright relationships.
Thirdly, we will review the detailed information of the SP provided, such as geographical distribution.
Fourthly, we will evaluate how to allocate data. Assuming there are no issues based on historical information, we are likely to support the first round of applications.

13. Will you use a 3rd-party Know your client (KYC) service?:
Data located in China can be queried using various enterprise query software, including enterprise information, website, contact information, etc
Located in other countries and regions, you can directly search for the name of the organization on Google to see if it matches the application

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

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
Every day

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?:
Business license verification, whether there are watermarks in the data samples, whether these data exist on the official website, third-party KYB services

19. How will you ensure the data meets local & regional legal requirements?:
After reviewing the sample data, investigate whether local laws can store the current sample data and whether it meets the current regional requirements

20. What types of data preparation will you support or require?:
Supports any type of data preparation and supports data sharding

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
After granting datacap, the customer will retrieve the successfully encapsulated data in real time for comparison with the sample after effective encapsulation

Data Distribution

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

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

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

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?:
I will not require proportional allocation, as long as a single SP does not store more than 30% of the total LDN quota. I may request the client to provide a preliminary SP allocation plan, which will be viewed using robot data

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

27. How will clients meet SP distribution requirements?:
I need to contact the relevant SP myself for data sealing, and I will provide several channels for customers such as Slack, BDE, etc

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
As long as it's not a VPN with geographical differences, I think it's okay

DataCap Allocation Strategy

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

30. Allocation Tranche Schedule to clients::

  • First allocation: lesser of 5% of total DataCap requested or 50% of weekly allocation rate
  • Second allocation: lesser of 10% of total DataCap requested or 100% of weekly allocation rate
  • Third allocation: lesser of 20% of total DataCap request or 200% of weekly allocation rate
  • Fourth allocation: lesser of 40% of total DataCap requested or 400% of weekly allocation rate

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.:
Try to use these open-source tools for processing as much as possible

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 Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
Yes, almost all repositories such as Google spreadsheets, filplus checker app bots, large datacap requests bots, and GitHub, https://filecoin.tools/

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
Our allocation strategy and audit process will be disclosed in Github to ensure our fairness. A communication group will be set up on the social software similar to telegrams to publish announcements, help customers solve various problems, or discuss the future development of filpuls with each other

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
After the customer obtains DataCap, we will have a specially assigned person to continuously follow up the customer's transaction information. If any violation is found, we will remind him first. If he does not listen to the advice, it will be deemed as a serious violation. The customers who seriously violate the rules will be blacklisted to reject future applications,I don't think there's any problem with the new customer. As long as my rules are met, I will retrieve the successfully packaged data and compare it with the sample in real time after they have been effectively packaged

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
For dispute situations, the response time should not exceed 48 hours, as we work on this every day. If there is a dispute over the retrieved data, there are several situations. The first is that the data does not match the content of the application. I will ask the customer to explain this. If there is no objection from both parties, the dispute will be terminated. Otherwise, the remaining datacap will be removed, and LDN will be closed. If the data content does not meet the specifications, the remaining datacap will be immediately removed, LDN cannot be reapplied for even if it is closed. The dispute resolution process will be made public. Of course, I will try my best to minimize disputes over data retrieval. For example, as I mentioned earlier, I will retrieve the successfully encapsulated data in real time after it is effectively encapsulated and compare it with the sample

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
For this issue, I will organize a channel or group chat in the early stage to gather customers together, so that they can see the updated information as soon as I publish it. Of course, I will also leave a message under each LDN application, so that everyone should be able to see it

40. How long will you allow the community to provide feedback before implementing changes?:
Within 48 hours

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 a hardware wallet, such as a LEDGER, to protect my notarized address. Only the person designated by our team can obtain the opening password and signature rights for this hardware wallet

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?:
I don't have this idea at the moment. If necessary, our team will consider it

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
To prevent abuse, I will establish the following rules
Firstly, before I issue the datacap, I need to provide a deposit of 100 fil to deduct any subsequent fees and ensure that your data is consistent with the applied data, as well as any possible cheating situations such as data distribution. If any discrepancies are found, they will be deducted in full
The second review fee for the applied application is 2fil, including KYC, KYB review, data sample review, etc
Thirdly, regarding data retrieval, for a good network, if the download speed exceeds 10m/s, no retrieval fee will be charged. Otherwise, a timeout fee of 2fil will be charged
The fourth option is to provide remote assistance in data preparation, with a separate fee of 10 fil per session, which will not be deducted from the security deposit
The fifth option is to provide remote assistance for order sending, with a separate fee of 10 fil per order, which will not be deducted from the deposit
Sixth, other remote technology fees can be provided, such as HTTP download and deployment, FTP deployment, etc., with a minimum fee of 10 fil per time, and tiered fees depending on the technical difficulty

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
Shenzhen Zhongchuang System Technology Co., Ltd. Legal representative: Bu Li

45. Where will accounting for fees be maintained?:
I will develop my own accounting system or other tools, as well as chat records for social apps

Past Experience, Affiliations, Reputation

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

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
This is the browser we use internally:http://www.filtrace.cc/ ZC LABS PTE.LTD was established in 2020 and has an office in China. ZC LABS is committed to becoming an enterprise that provides distributed storage infrastructure construction and distributed storage service support. At present, we mainly engage in two business lines: 1. Construction of Filecoin distributed storage. At present, we have provided storage services for SPs in Guangzhou, Shenzhen, Dongguan, and Hong Kong, China. In the future, we will establish nodes around the world and provide storage services to customers. 2. Distributed storage related software services, providing online storage platforms for enterprises and hospitals

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
During my one year as a community notary, I have actively participated in notary governance and reviewed a large number of LDN applications and their usage, as well as the total DC quota of 100P that will be consumed in almost a month. Therefore, I estimate that the 200P applied by our team for one year is sufficient, and there are many social channels in China that can encourage customers to join

@galen-mcandrew
Copy link
Collaborator

Datacap Request for Allocator

Address

f24siazyti3akorqyvi33rvlq3i73j23rwohdamuy

Datacap Allocated

5PiB

@filplus-bot
Copy link
Collaborator

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacebzglshnvn7mvqcqvmxtecqzdtxctvr3g6lvvcf2s7fobaq3xoeks

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

@galen-mcandrew
Copy link
Collaborator

Datacap Request for Allocator

Address

f24siazyti3akorqyvi33rvlq3i73j23rwohdamuy

Datacap Allocated

5PiB

@filplus-bot
Copy link
Collaborator

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacec7b7nbsyehnoeiys4v2rrarr75cjitgagjlmepljuiuwnhb3efw2

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants