filecoin-project / notary-governance

113 stars 55 forks source link

v5 Notary Allocator Application:HG(hengan) #1066

Open HG-singapore opened 5 months ago

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

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 commented 5 months ago

Basic Information

1. Notary Allocator Pathway Name: HG

2. Organization: hengan

3. On Chain Address for Allocator: f15pidlm4yjhqx3lpttuuvkmm5oinhvvugpuk7uoq

4. Country of Operation: Singapore

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

6. Type of Allocator: Market-based

7. DataCap requested for allocator for 12 months of activity: 100P

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?: Fully implement monetization and have a reward mechanism to prevent abuse from occurring

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?: A large number of existing templates

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.: https://form.jotform.com/231862753015656 Similar to this, some issues outside of the template will also be added, such as Using personal information, company or organizational information to determine the ownership of data Dataset information: What tools are used? How to send it? How to distribute DataCap: SP quantity? How to allocate

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

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?: Utilize existing open-source tools such as CID checker tool

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?: Check if there are any special identifiers in the data, such as watermarks, special information, etc For public data, a proof of data disclosure is required, such as the company's public data, which requires confirmation of the company's business license, etc There are many channels for verifying enterprise users on the Internet, such as Google search, which can provide a large amount of specific company information

19. How will you ensure the data meets local & regional legal requirements?: I will go to understand the local legal situation, whether it is allowed, and consult professional legal institutions or relevant personnel to understand. This method may be faster

20. What types of data preparation will you support or require?: Support various publicly available datasets

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?: Both Lotus and Boost can retrieve corresponding data and then verify whether it matches the sample provided by the customer to prevent abuse. We will sample and inspect sectors at different stages

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?: 3 different cities

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?: According to the current template and rules, such as # 922, equal allocation will not be required

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?: This is something the client is considering, just meet my conditions

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?: Not supported, will ask SP to provide KYC information

DataCap Allocation Strategy

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

30. Allocation Tranche Schedule to clients:: Allocate according to existing rules, such as https://github.com/filecoin-project/filecoin-plus-large-datasets?tab=readme-ov-file#datacap-tranche-size-calculations But 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.: Official existing open-source 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: • client discoverability & applications  We will publish news on Salck, WeChat group,and Twitter etc . • due diligence & investigation For example, question 12 • bookkeeping Google Docs • on-chain message construction https://filplus.fil.org/#/ • client deal-making behavior datacapstats.io filecoin.tools/clients filplus.info filfox.info • tracking overall allocator health CID checker bot and datacapstats.io • dispute discussion & resolution such as https://filecoin.notion.site/T-T-Dispute-Tracker-d28b93677cb544b48e77b585856601cf • community updates & comms  Github、Email、Slack、Or wechat

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?: Yes, almost all official tools

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?: Public Google Spreadsheet

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.: Utilize all existing official tools to support new customers as long as data is legitimate and legitimate

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.: https://filecoin.notion.site/T-T-Dispute-Tracker-d28b93677cb544b48e77b585856601cf,We will also create a similar public form to disclose the dispute situation, and anyone can submit a dispute. We will handle the dispute within 48 hours. When there is a dispute, we will immediately stop issuing relevant data caps and check the specific situation. For illegal distribution of data caps, false data, illegal data, and any other intolerable errors, we will immediately remove the remaining data caps and publish them in the community, Afterwards, the application is prohibited, and other related disputes may be decided accordingly depending on the situation

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

40. How long will you allow the community to provide feedback before implementing changes?: two 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 technical responsible 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

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.: The customer needs to pay 1FIL for data review before the review, including KYC, KYB, data review, etc

After the data review is approved, a data pledge fee of 50FIL needs to be paid. If the data is found to be inconsistent with the initial declaration, it will be deducted

We can provide relevant technical services, with a fee of 10 FIL per session, such as packaging data, setting up HTTP download services, etc. More complex services require hourly fees

For the distribution of data caps, a fee of 0.1 fil/T will be charged, and this fund will be rewarded to high-quality SPs. Based on the amount of data stored by the SP, the initial ranking is based on the network situation of retrieval. Rich fil rewards will be distributed to the SP's account every quarter, and also to high-quality customers. The number of high-quality SPs under each LDN will be ranked, and the rewards will be calculated and distributed quarterly

44. Describe your organization's structure, such as the legal entity and other business & market ventures.: A blockchain technology team established in Singapore

45. Where will accounting for fees be maintained?: On chain or publicly available forms

Past Experience, Affiliations, Reputation

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

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.: We have been committed to the blockchain industry, including Bitcoin, Ethereum, Filecoin, and more

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?: Reviewed a large number of LDN application decisions