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:ZhongYiGuoLian #1074

Open
Patapon0702 opened this issue Jan 18, 2024 · 5 comments
Open

v5 Notary Allocator Application:ZhongYiGuoLian #1074

Patapon0702 opened this issue Jan 18, 2024 · 5 comments

Comments

@Patapon0702
Copy link

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

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.

@ghost
Copy link

ghost commented Jan 21, 2024

Basic Information

1. Notary Allocator Pathway Name:
Patapon

2. Organization:
ZhongYiGuoLian

3. On Chain Address for Allocator:
f1n7slqdxhxi3n3ljmfjzsbdhaemz53bcaslu5sii

4. Country of Operation:
China

5. Region(s) of operation:
Europe

6. Type of Allocator:
Manual

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

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?:
No

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?:
The purpose of allocating the DataCap is to make sure clients use these DataCap in the right way to store real and valid data. We firstly specify some rules to figure out the true identity of the applicant.
• Browse their official website to get a general understanding of the company or the individual.
• Query the company's registration information from government related websites to make sure the information he submitted is truth.
• Ask some questions to know about the applicant's position/organization/plan/use case etc.
• Then We will classify applicants based on their industry reputation and scale etc. All applicants will be divided into eight categories to determine the amount of datacap they will get.
The whole application process should be open and transparent. There are only several necessary internal processes Currently:
• Some brief communications via e-mail to make sure the e-mail address is authentic and valid.
• For some companies involved in confidentiality that can’t answer some details in public, we will have some communications in our private repository. In the event of a dispute, we will share the repository with officials immediately. The target and amount of our allocation can be found in the scoring guidelines.

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
https://docs.google.com/spreadsheets/d/1oM_Urz8TwwiijQt8EZDxaNYe2yJR56PDXQYnYQvCnPo/edit#gid=0

13. Will you use a 3rd-party Know your client (KYC) service?:
search.sunbiz.org

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 can apply to my pathway

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
I plan to track the rate once or twice a week trough 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?:
Private Non-Profit/Social Impact, Private Commercial/Enterprise, 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?:
To verify a client's data ownership, I would use a combination of methods, including requesting official documentation such as business registration certificates, tax identification numbers, and other relevant legal documents. I may also verify the client's data ownership through third-party sources such as public records and databases.
Using a third-party KYB service to verify enterprise clients can be a valuable additional layer of verification. This service can provide access to comprehensive databases and sources of information to confirm the legitimacy and ownership of the client's business. It can also help to identify any potential red flags or discrepancies in the client's data.
Ultimately, the decision to use a third-party KYB service to verify enterprise clients will depend on the specific requirements and risk assessment of the business. It can be a useful tool to enhance the due diligence process and ensure the accuracy and legitimacy of the client's data ownership.

19. How will you ensure the data meets local & regional legal requirements?:
Research local and regional legal requirements: Start by thoroughly researching the data protection and privacy laws in the specific local and regional areas in which the data will be stored and processed.

20. What types of data preparation will you support or require?:
The displayed data should be representative, able to illustrate certain characteristics and attributes of the entire data, such as data volume, data generation rate, etc.

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
I will use random sampling to ensure that the data is representative of the entire population. This will involve selecting a random sample from the dataset to analyze and verify

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?:
At least 7-8 locations and 3-4 separate geopolitical regions. No, I will not require certain geopolitical regions.

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?:
Yes, I will use a template to do recording.

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

27. How will clients meet SP distribution requirements?:
Yes. I will.

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
I will not support it. Clients should provide evidence that they are not using VPN.

DataCap Allocation Strategy

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

30. Allocation Tranche Schedule to clients::
We conduct our internal review process through 4 stages

  1. The primary reviewer will conduct a basic review of the application submitted by the client. The applicant's data storage must be open and valid data, and there are real storage requirements.
  2. According to the results of the basic review, the junior reviewers will submit the allocation process to the intermediate reviewers, and the intermediate reviewers will give a score based on the content of the evaluation model.
  3. According to the scoring results of the intermediate reviewers, the senior reviewers will further conduct a detailed investigation of the business ecology of the company, as well as verify the true information of the applicant and the company, and make a final decision and signature.
  4. After the decision of the senior reviewer is approved and signed, the DataCap will be assigned a certain amount to the client. If not passed, we will inform the client of the review result.

31. Will you use programmatic or software based allocations?:
No, manually calculated & determined

32. What tooling will you use to construct messages and send allocations to clients?:
I would like to use the existing notary registry tooling at https://filplus.fil.org/#/

33. Describe the process for granting additional DataCap to previously verified clients.:
Periodically review and audit DataCap usage (as metioned above, records are tracked and reviewed periodically to determine disqualification or demotion of nonconforming customers) Users can upgrade according to the actual situation to meet the requirements Communicate with customers regularly to understand relevant requirements and progress, and provide better service to customers Of course, try to avoid this situation in the initial review of the application and improve the initial application information supplement during the continuous record review process.

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:
Github,google doc,search.sunbiz.org,CID BOT

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
yes

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
all records will be public. Also, if we have detailed communication needs E-mail, we will save the screenshots..

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
This should include regular check-ins, tracking DataCap distribution metrics, understanding client demographics, time metrics, trust evaluations, and the use of tools such as CID Checker/Retrievability Bot.

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
response ASSP within 3 working days
All discussions must be transparent on GitHub, and language must not be discriminatory based on race or ethnicity. All speculations and inferences must be supported by evidence and no unreasonable speculations are allowed.

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
I will post on github about updates regularly

40. How long will you allow the community to provide feedback before implementing changes?:
Within 5 working days

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?:
Ne use a multi-signature wallet to operate, and we keep important information about otherpeople confidential. The main exercise rights are held by the core personnel of the company(no more than three people)

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?:
NO

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
Not willing to disclose

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
In 2017, a core technical team from distributed storage professional researchers, blockchain experts, senior IT engineers and hardware engineers was established, dedicated to distributed storage promotion, distributed storage device research and development, distributed storage application development. At present, we have deployed multiple distributed storage data centers around the world, with multiple 10-gigabit backbone networks. At the same time, we are providing decentralized cloud computing services based on the Web 3.0 infrastructure backboned by blockchain technology. In the future, distributed storage and data centers will be deployed.

45. Where will accounting for fees be maintained?:
China

Past Experience, Affiliations, Reputation

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

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
As an organization, we built quite an extensive relationship with the Filecoin community since 2019. We have sustained some contributions to the overall network. As a miner and researcher,we joined the testnet, space race, slingshot, mainnet. Our miner ids are f01901815 f01890287 f01736786

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
200 Pib

@galen-mcandrew
Copy link
Collaborator

Datacap Request for Allocator

Address

f22rkakf23oyzevmr75f663tcl76pezewbsk2oqvq

Datacap Allocated

5PiB

@filplus-bot
Copy link
Collaborator

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacecu5d3gbklnlaa3aldte3zilxa35r7jg5tfzfwcpisz2mlodwu5yo

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

@Kevin-FF-USA
Copy link
Collaborator

Hi @Patapon0702

Wanted to send a friendly check in.
As of this comment date, haven't seen any client applications or DataCap disbursements for the organization. Inactive organizations are in the process of being reviewed to see if still wanting to remain in program. If you would like this pathway to remain active as an Allocator, kindly asking that you reply to the proposal with your timeline for onboarding pathway or plan for action to clients.

1074 | ZhongYiGuoLian, Patapon | Manual | Bookkeeping | China | #1074 | f03019935

@Kevin-FF-USA
Copy link
Collaborator

Hi @Patapon0702
Tonight is the final night to provide a timeline for activity to this Allocator. If we don't hear from you in filecoin-project/Allocator-Governance#6 this Allocator pathway will be sunset and you will need to reapply in order to receive DataCap again.

If you wish to remain active, please respond to Issue 6 with a timeline /or/ roadmap.

Warmly,
-Kevin

https://docs.google.com/presentation/d/1yx-C1urFX7I_A1kmhJTXBy8R42770ZnST0WoQaZzTd0/edit?usp=drive_link
and https://docs.google.com/presentation/d/1pmrRvAyxP56ZjMpcItVbiuJcAvYNQ_YDyD3n6FtX5Co/edit?usp=drive_link

@Kevin-FF-USA Kevin-FF-USA reopened this Jun 27, 2024
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