filecoin-project/notary-governance

v5 Notary Allocator Application: 1475

Opened this issue · 15 comments

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+"):1475
  2. Organization Name:1475
  3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): f17a4y7bgfvzl7m4dw3kbxnlfutpxfelfim6risnq
  4. Country of Operation (Where your organization is legally based): Greater China Region (GCR)
  5. Region of Operation (What region will you serve?): All Regions
  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): 180PiB

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.

Hi @1475Notary
Wanted to let you know this application has been received. Also verifying you have 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.

Basic Information

1. Notary Allocator Pathway Name:
E-Fil+

2. Organization:
1475

3. On Chain Address for Allocator:
f17a4y7bgfvzl7m4dw3kbxnlfutpxfelfim6risnq

4. Country of Operation:
GCR

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:
180PiB

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?:
1475 Group are willing to help enterprises or Individuals to participate in filecoin by providing them with DataCap to store and spread useful data. For the first time, we support and innovate a combination of manual and automated distribution processes to increase the transparency and efficiency of distribution and reduce the risk of prejudice and abuse.�We will design automated tracking tools to track the rate at which DataCap is allocated to clients to ensure that DataCap is allocated appropriately and fairly.�With our experience working as a Notary of V4, we have a better understanding of the needs of different types of clients, and we will take proper and comprehensive review of different applicants and develop an allocation plan exclusively for the convenience of our clients to come and participate, while keeping the preciseness of the Filecoin ecosystem.�We also have the ability to put data into car files, and we can prepare the data for the client and send it to the sp, reducing the difficulty of storage for the client.

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?:
Other (specified above), 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 general, the higher the DataCap thresholds are, the more restricted the client scrutiny would be.
For individual clients, online identity will be verified by both account age and account activity perspectives,
and this will serve to prove that they are valid users and not bots or sybils.
Third-party tools like twitteraudit may also be used to verify online identities.

For organizational clients, application organizations should be easy to verify through the appearance of their application.
The developing applications may require further stringent investigation;
this is to ensure that the application is valid and enclosed with meaningful content, rather than the shell of a malicious client.
Large public datasets hosted by organizational clients are easy to verify because the data should be unencrypted and accessible to anyone.
However, in the event that the organizational client has large private encrypted datasets(i.e., law firms), the Due Diligence procedure will be executed.

Below is the proposed procedure of Due Diligence. We need 3 types of information for review by myself or our compliance team depending on the volume of clients required Due Diligence:

  1. Entity Information
  • Formation documents - this includes certificates of registration/incorporation/information;
  • government-issued identification number for the entity
  1. Authorized Signatory Information
  • evidence of the authorized signatory’s authority to act on behalf of the application entity (evidence include written consent of the company board of directors, or a secretary’s certificate, a signed letter from the applicant’s CFO, or may be included in the company operation agreement);
  • close-up photo of the signatory’s face next to the visible passport or other government-issued photo-bearing ID
  1. Beneficial Owners - If there are any 25%+ shareholders, we need a document as a capitalization table, operating agreement, or similar to verify the ownership, and also the following information for each of them:
  • legal name;
  • date of birth;
  • street address (P.O. box number is not acceptable);
  • a government-issued identification number, which shall be either an SSN, ITIN, passport number and country of issuance, alien identification card number, or number and country of issuance of any other government-issued document evidencing nationality or residence;
  • copy of an unexpired passport or other government-issued document evidencing the individual's nationality or residence which bears a photograph of the individual.

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
There are two questionnaires to help me get to know our clients. The first one is about the basic information collection of new clients.
#Questions #1
Please describe answers as much specificity as you can.

  1. Can you introduce yourself? Where can I find you online? (GitHub, Twitter, Linkedin handle, Wechat, etc.)
  2. If you represent an organization, what is the name, nature, registration country, time since inception, and named officers of your organization?
  3. In which region(s) do you intend to use the DataCap?
  4. What is your use case for the DataCap being requested?
  5. Do you plan to specify advanced features when utilizing a DataCap in your storage deal? If so, please specify the feature.
  6. How many miners do you plan on allocating the DataCap? If you have a specific miner(s) you would like to allocate a DataCap, please specify.
  7. Do you agree on providing transparency of DataCap allocation decisions & execution details in public to prevent excessive/unfair self-dealing? ���We will use the second questionnaire to collect follow-up answers about previous allocations for returning clients.

#Questions #2
Since you have requested DataCap from me or other notaries before, we have some questions regarding your previous DataCap allocation.

  1. How much cumulative DataCap was allocated to you from me or other notaries?
  2. In which region(s) did you use the DataCap?
  3. What was your use case for the previous allocation?
  4. Did you specify any advanced features for the previous allocation?
  5. How many miners did you allocate the DataCap to? Please specify transaction links to the storage deals.
  6. In your previous allocation, did you violent any community principles like excessive/unfair self-dealing?
  7. Did you ask SP to provide the fast retrival to the network?
  8. Is there anything I could improve to serve you better in future allocations?

13. Will you use a 3rd-party Know your client (KYC) service?:
Yes, we will use reputable 3rd party system that ensures client eligibility, checks against known sanctions lists, and mitigates sybil risk, such as Qichacha, Tianyancha, Qixinbao and so on.

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 our pathway. We will post the process of applying to us to make it easier for applicants to participate; Also, we have a professional technical team for technical support to solve the problems that clients may face in the process. We would like to help all those who want to get involved in Filecoin and we will help them answer questions about their application and guide them through the process, in order to support the goal of growing the network of Filecoin.

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
The tool we are currently using has a program on the backend that calls the lotus API. It can check the client's activity of allocations every hour to see how they change. With this data, we can calculate the speed and distribution of DataCap.

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, Private Commercial/Enterprise, Private Non-Profit/Social Impact

18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?:
Yes. For public dataset, we will ask clients to provide source information, including the name of the dataset, which website the dataset is located at, and the team to which the data is belonging to.�For private dataset, we will ask the client to show data sample and provide the proof of their store. After we confirm that the data is reasonable and legitimate, we will grant DataCap for the client.�For enterprise data, we will use 3rd party KYB (https://www.yushanshuju.com/index.html ; https://www.x315.cn/overseasreport) to verify the client's corporate identity and ask the client to show data sample and provide the proof of their store. After we confirm that the data is reasonable and legitimate, we grant DataCap for the client.

19. How will you ensure the data meets local & regional legal requirements?:
We review the law of the client's location or the place where the data belongs. And compare the data samples provided by the client to ensure that the data meets the law of the local region. Clients are required to use secure storage and transfer methods to ensure data security. We have a professional legal team that will provide us with the latest legal requirements related to data protection in each region in a timely manner to ensure the legality of each step.

20. What types of data preparation will you support or require?:
We have a technical team to support data packing services for our clients. We use our program to cut, pack, and compress the data provided by the client into a 28-32 GiB zip file. These files are then converted to car files by a program using code libraries such as go-car; We also support working with DP, DP will pack the qualified files and send them to client, and then the client will send the package to SP for sealing.

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
We will ask the client to provide data samples to manually check the authenticity of the samples initially.�We also have automated tools that we provide to our customers. After the client installs this tool, the program performs a random sampling of the data provided by the client. It also automatically checks the data's format, compares it with the data sample type for evaluation, and ensures the consistency of the data.�To prevent sector-size abuse, we support DP to help clients with their applications. We will ask DP to provide clients with a packing service that requires package to be 28-32GiB to prevent sector-size abuse.�If they need us to provide data packing services, we will retrieve the relevant files and check the actual size by using GraphSync, Http and other retrieval methods. Then we determine if a sector-size abuse exists.

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?:
We will require data to be stored in at least 3-4 geographic regions, and expects clients to store copies in at least five physical locations. We welcome clients to distribute their data anywhere in the world. But we also comply with laws and regulations and advise our clients to exclude storage in areas that may be disputed or subject to international sanctions.

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?:
We require a detailed distribution plan from the client. Before client's first round allocation, we will ask clients to fill out the form we provide. The form will contain the percentage of clients allocated to different SPs and the KYB information of the SPs. We will ask our clients to follow the distribution plan they provide.

26. What tooling will you use to verify client deal-making distribution?:
Yes, we will use existing open-sourced tools AC Bot, CID Checker, and DataCapstats.io to check the distribution of our clients' transactions. We will check clients distribution from time to time after their first allocation. Then we will do automatically check and report on client deal-making distribution prior to subsequent allocations.

27. How will clients meet SP distribution requirements?:
We support using our own program to help clients with allocation.�Our platform supports manual and automated allocating DataCap to SPs. During the process, our platform will distribute evenly based on the client's history to ensure compliance and efficiency of allocation. This helps the client to reduce the risk of uneven distribution, and makes it easier for both the client to distribute and the SP to receive the data.

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
We are willing to support clients who work with SPs that use VPN. We understand that VPN are tools for SPs in some areas that can help them improve privacy and security. We will do KYB checks on each SP using VPN to confirm the reasons for SPs using VPN and their compliance, to ensure data security as well as distribution compliance.

DataCap Allocation Strategy

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

30. Allocation Tranche Schedule to clients::
• First: Clients receive lesser of 5% of total DataCap requested or 50% of weekly allocation rate
• Second: After used at least 80% of the first round, clients can receive lesser of 10% of total DataCap requested or 100% of weekly allocation rate
• Third: After used at least 80% of the second round, clients can receive lesser of 20% of total DataCap request or 200% of weekly allocation rate
• Fourth: After used at least 80% of the third round, clients can receive lesser of 40% of total DataCap requested or 400% of weekly allocation rate
• Max per client overall:  No more than 5 PiB

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.:
When a client makes a request for additional DataCap, we will confirm the amount of demand from the client first. And use the open-source tool --- SA Robot to get a report on the client's DataCap usage to check the client's usage of the previous DataCap.�When the client is using 80% of the DataCap, and upon our confirmation that the client's behavior complies with filecoin's rules, we will continue to grant DataCap to our clients. The amount of DataCap is consistent with previous allocation.

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 GitHub
• due diligence & investigation https://www.yushanshuju.com/index.html ; https://www.x315.cn/overseasreport
• bookkeeping  GitHub, Own website(pangodbook.com), TecentSheet
• on-chain message construction Ledger; https://filplus.fil.org/#/
• client deal-making behavior AC Bot, CID Checker, DataCapstats.io
• tracking overall allocator health DataCapstats.io, Filfox
• dispute discussion & resolution Slack, GitHub, Email
• community updates & comms * Slack, GitHub, Email�Address all the tools & software platforms in your process.

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
Yes. We'll use open-source tools, such as AC Bot, CID Checker, Filecoin Plus These open source tools can help follow customers' DataCap usage in real time. Also, GitHub will be used for booking. Tencent sheet will be used for collaboration in our group.

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
We will maintain our distribution and client information in both public and private ways. We will show our allocation policy and records for DataCap openly on GitHub. All records are automatically updated real-time as they are allocated by us. Enable anyone of the community to monitor and point out potentially problems. Identity information provided by the client, along with allocation information that we are required to keep confidential, will be stored in a private database built by our company. When the Fil+ team asks for reviews, we will support them by email (Email: tina-1475@outlook.com) We will provide the necessary information to support it.

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
a. We will communicate with the client on a monthly basis and the client should provide an update on their progress
b. Tracking DataCap allocation and client usage with CID Checker, AC Bot and DataCapstats.io
We welcome new clients, but new clients are also required to follow Fil+'s rules and participate in line with the laws and regulations of their country of location.

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
We aim to deal with disputes in a positive and speedy way.�When a dispute occurs, we will respond within 72 hours. To resolve a dispute, we will first find out the details of the dispute and identify the related parties, nature and conditions of the dispute. As we keep detailed records of every deal, we have a full view of our capability to handle disputes. The data we record can support our explanation of any dispute.�For disputes involving the client themselves, we will respond within 72 hours and a reasonable explanation will be provided by GitHub/slack to the challenger.�We will respond to disputes involving our allocator process within 48 hours and will provide a reasonable explanation to the challenger via Email (tina-1475@outlook.com).

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
When we have an update to to tooling, pathway guidelines, parameters, and process alterations, we will make it public via GitHub, website, slack, which will include the specific part of the update, and the function that will be implemented after the update. Before a specific update is put in place, we will also contact the Filplus-govteam via email to confirm that the update can be passed. After the update is done, we will also inform the clients who have applied to us via slack or email in a timely way.

40. How long will you allow the community to provide feedback before implementing changes?:
We allow one month for the community to provide feedback before changes are implemented. It will give community enough time to voice their opinions. We will also post pending updates on our website, GitHub, and slack, and engage in interactive discussions with the community to ensure changes are possible. Community can also communicate with us via email (pangodgroup@outlook.com) for feedback.�We will balance the opinions from community members with our goal of participating in filecoin, and aim to make improvements that are more beneficial to the filecoin ecosystem.

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 will protect the on-chain notary address by multisig to ensure the security and standardization of signing. Our process of multisig takes place within our company's senior management team, via internal OA approval --- The operations team submits the allocator request and the management team approves the request, copying it to the company's audit team. After internal approval, the management team selects two members for two multisig to grant the DataCap.

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?:
While the Filecoin Foundation and PL will continue to make investments into developing the program and open-sourcing tools, we are also striving to expand and encourage high levels of service and professionalism through these new Notary Allocator pathways. These pathways require increasingly complex tooling and auditing platforms, and we understand that Notaries (and the teams and organizations responsible) are making investments into building effective systems. It is reasonable for teams building services in this marketplace to include monetization structures. Our primary guiding principles in this regard are transparency and equity. We require these monetization pathways to be clear, consistent, and auditable. �We have plans to deploy smart contracts to track DataCap allocation, and ensure compliance and fairness of distribution. The relevant code for smart contracts will be stored and made available on our GitHub repository page. We aim for transparent community participation. We will keep a set amount of money for contract development costs and have a dedicated finance team to manage the accounts for this.

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
If the clients do not have the DP's ability to prepare the data themselves. If they need us to help them with data preparation services, they need to pay us a data fee of 10USDT/TiB. If clients need us to help send the hard drive to SPs, we will charge them for the courier fee. Also, we'll ask for a labour fee of 80USDT/day. Our fees are set to cover the cost of the services we provide, the cost of labour and to ensure that we can maintain a high quality and sustainable service.

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
I'm Tina, marketing manager of 1475 Group. Team of 1475 is from Shanghai, China. 1475 including high-performance terminal storage equipment selling, stable and secure computer room network system, efficient storage algorithm empowerment, etc. The core members of team 1475 worked for Baidu, Accenture, Google, UnionPay, and other internet giants, who are all well-known as big data experts and AI algorithm experts in the industry, as well as hardware experts from Intel with 20 years of experience in the industry. In June 2020, the 1475 team was formally recognized as a high-tech enterprise by Shanghai Government. It has applied for 28 patents and software copyrights, with multiple certificates such as IDC value-added telecommunications business license and ISP value-added telecommunications business license. Obtained investment from HashKey Capital, Fenbushi Capital, and Yimo Capital. Now we have a multi-channel development. We contacted the Dfinity official and established the ICP foundation to build Web 3.0.

45. Where will accounting for fees be maintained?:
We will invite a professional audit team in our company to account for the costs. We will put all records on our website and regularly publish the audits.�The process is: Our professional audit team will review the transaction details, flow of funds on a quarterly basis and form an audit opinion, generate a report and finally publish it on our website. Provide a clear audit path for Fil+ governance and stakeholders, and give transparency and ease of audit for all monetisation processes.

Past Experience, Affiliations, Reputation

46. If you've received DataCap allocation privileges before, please link to prior notary applications.:
Used to be a notary and on boarding data successfully. Please refer to : #770 ;#423; #172; #29

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
We are trying to find more innovation opportunities to embrace the future world, including, of course, connectivity with the web3 world. We know Filecoin and IPFS via IPFSUnion in January 2021- one of the biggest Lotus operator in China. At the beginning, I started to participate in Filecoin as an mining investor.

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
We have worked with 100+ clients . Market data shows that public demand for distributed storage continues to grow, with new client applications expected to increase by 10% annually. And path usage is expected to grow by 20% annually, based on a combination of demand from existing and new clients. Our estimates of client growth are based on a mix of our existing client base and market analyses. We keep in touch with our existing clients through face-to-face meetings and emails, and we regularly do online and offline activities, as well as on-site visits, to bring in new clients. Based on our experience in participating in blockchain, combined with data from market research we have conducted, we believe we can accurately anticipate and meet the needs of our clients.

Datacap Request for Allocator

Address

f2arpo76vxmneuor5qunbpybm24k7efomlev3rk5i

Datacap Allocated

5PiB

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacedd24jvccxzkrvwf4hx2bdgtot3hoonzk6xtxmdsur4n2xfrqyoce

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

Datacap Request for Allocator

Address

f2arpo76vxmneuor5qunbpybm24k7efomlev3rk5i

Datacap Allocated

2.55PiB

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacebgkkkawp33e7kgrqmsb7onjkj7gbusxxgtctqwkuu2q7cryasgwa

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

DataCap Request for Allocator

Address

f2arpo76vxmneuor5qunbpybm24k7efomlev3rk5i

Datacap Allocated

5PiB

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacea2s2ppdmghw2z7a42hlrpva267hbdggmjoi2ekkzowivtu5g7jc6

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

Datacap Request for Allocator

Address

f2arpo76vxmneuor5qunbpybm24k7efomlev3rk5i

Datacap Allocated

5PiB

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacebdi4633qed5lcurkmlp35eogj7afqu4tclhxkp37cn5v2mkw4fje

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

bafy2bzacecdvo7c3gob5ysnzx7hz3r5r3yj2o7uletga7g6vdjjmul33kphme

Datacap Request for Allocator

Address

f2arpo76vxmneuor5qunbpybm24k7efomlev3rk5i

Datacap Allocated

2.5PiB

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacebbf5or7filluszjxd5uxx7rclu5kt25og324wvxko7g5by6uppbk

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