v5 Notary Allocator Application: ND CLOUD

[NDLABS-Leo]

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+"):ND CLOUD
2. Organization Name:ND LABS
3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): F1ydfdqffpgx4uc5ar3j7xif5btadxodoojftshsa
4. Country of Operation (Where your organization is legally based): Singapore
5. Region of Operation (What region will you serve?): North America / Asia minus GCN
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):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.

[Kevin-FF-USA]

Hi @NDLABS-Leo
Wanted to let you know this application has been received along with the Airtable detailed answers - the public answers will be posted in a thread below soon. If you have any questions - please let me know.

[ghost]

Basic Information

1. Notary Allocator Pathway Name:
NDCloud

2. Organization:
ND LABS

3. On Chain Address for Allocator:
F1ydfdqffpgx4uc5ar3j7xif5btadxodoojftshsa

4. Country of Operation:
Singapore

5. Region(s) of operation:
Asia minus GCR, North America

6. Type of Allocator:
Manual

7. DataCap requested for allocator for 12 months of activity:
100 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?:
NDCloud is a new pathway. This proposed channel is designed to allow us to reach and enable web2 and web3 enterprise data owners whom we understand and can effectively engage to store data on the Filecoin network. NDCloud is a public cloud aggregation platform, and the clients we aggregate to the public cloud have real and substantial data storage needs. Therefore, the clients in this channel will be highly efficient, with low educational costs for data storage, and sustainable over the long term.

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?:
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?:
Section One: Review Based on Fil+ Current Rules

1. Initially, the client needs to submit their LDN application.
2. Conduct a voice or video meeting, and the client must undergo domain authentication through the enterprise email.
3. The client is required to provide a list of collaborative storage nodes, and their geographical dispersion is reviewed.
4. Request the client to provide data samples and conduct a sample review of the enterprise's data.
5. If the client meets the above criteria, initiate the first-round small-scale issuance process.
6. Review the client's encapsulation nodes and compare the matching degree of disclosed nodes, conducting retrievability tests.
7. If all the above criteria are met, proceed to the next round of quotas, conducting data download and comparative testing during the process.
8. Before each round of issuance, compliance with the disclosed standards is mandatory. A plan for allocating sp node quotas for the next round must be provided, and random comparisons of DC quotas must be conducted in each round for review.

Section Two: Review Based on Cyberport Rules

1. Conduct a comparative review with Cyberport's corporate database to verify the consistency of enterprise information.
2. Compare with Cyberport enterprise level and set the enterprise's equity level, which is graded from 1 to 5. The higher the level, the larger the equity distribution.

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
https://docs.google.com/document/d/1v1xgciUsTtAEEoxUb82t2e4el4KIOCH_JJU2XvGUakg/edit?usp=sharing

13. Will you use a 3rd-party Know your client (KYC) service?:
No external KYC system will be used. The internal enterprise review process of Cyberport will be utilized, combined with ND's review criteria, to conduct KYC authentication for the enterprise.

14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral):
NDCloud: Any web2/web3 enterprise-level client can apply. clients applying for storage through this channel can enjoy exclusive discounts from NDCloud's public cloud providers. (This is also one of the ways we bring diverse data clients to the FIL ecosystem.)

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
https://docs.google.com/spreadsheets/d/1BfAe7UaURb55NFNeltJAmkpTRXhphu_e68ctn2-Sm_Y/edit?usp=sharing

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?:
Other (specified elsewhere)

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 do not use third-party KYB to verify corporate clients. Enterprises that cooperate with NDCloud have data storage needs, and we have detailed information about these enterprises, including both their background and data content. In addition to the already cooperating enterprises, if there are clients who want to obtain quotas through our channel while accessing more favorable public cloud service providers, the public cloud service will also review the client's qualifications.

19. How will you ensure the data meets local & regional legal requirements?:
The enterprises collaborating with cloud service providers are certified through contracts.

20. What types of data preparation will you support or require?:
We support universal data types and provide clients with data processing tools to preprocess their data.

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
We will use MD5 value comparison to compare client data.

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?:
There need to be distributions in at least 4 regions.

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 will request clients to allocate no more than 20% to different SPs in each round, and we will document this through records. Additionally, data validation will be performed using the https://datacapstats.io/ website.

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

27. How will clients meet SP distribution requirements?:
Yes, we will use a programming approach to select data and distribute it from the client to the SP.

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
Support for sps to use VPN, but Cyberport and ND will conduct a prior review of the geographic location information provided by the customer before proceeding, and only with detailed information from the customer can it be allowed.

DataCap Allocation Strategy

29. Will you use standardized DataCap allocations to clients?:
No, client specific

30. Allocation Tranche Schedule to clients::

• First: The client will provide their weekly application volume, and for the initial allocation, we will allocate 50% of the weekly application volume.
• Second: After review, the client will be allocated 100% of the weekly application volume.
• Third:  After review, the client will be allocated 200% of the weekly application volume.
• Fourth:  After review, the client will be allocated 200% of the weekly application volume.
• Max per client overall: Upon successful review, the client will be allocated the weekly application volume minus the already allocated quota, with a maximum single application of 5P.

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?:
If the new allocator model supports the distribution of DC to clients through the https://filplus.fil.org/#/ tool, we will utilize that tool. Note: In the absence of tools similar to https://filplus.fil.org/#/, we will primarily use the Boost tool to construct messages and allocate dc to the clients.

33. Describe the process for granting additional DataCap to previously verified clients.:
We will try SA Bot.

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: Mainly recorded through GitHub.
• Due diligence & investigation: Processes are documented on GitHub.
• Bookkeeping: Recorded through online documents.
• On-chain message construction: Primarily utilizing the Boost tool.
• Client deal-making behavior: https://datacapstats.io/clientsbot
• Tracking overall allocator health: Utilizing bot tools.
• Dispute discussion & resolution: Tracked in the trust document on GitHub.
• Community updates & comms: Through GitHub and Slack.

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
Yes, through GitHub repositories, Google Spreadsheets, and bot tools.

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
We primarily keep records through GitHub, and additionally, we will provide emails as evidence. Moreover, we will document the information through online documents.

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
Based on the proposal at #986, we will conduct audits and tracking of downstream usage by clients using tools such as the CID checker and searchable bot.
For new clients, there will be a three-week grace period, during which new clients need to make the necessary adjustments. Failure to do so within this timeframe will result in the discontinuation of DC allocations.

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
Type 1: Disputes Limited to Within the Allocation Pathway

1. Response time is 1-2 days.

   • Disputes will be addressed within 1-2 days, during which both parties need to provide a chain of evidence.

2. Transparency determined based on the nature of the dispute.

   • Transparency will be determined by Cyberport, with the principle of maximizing transparency without compromising customer interests.

3. Accountability determined based on the dispute.

   • Accountability measures will be decided based on the outcome of the dispute:
     a. Temporarily suspend DC allocation, resume after client adjustments and proof.
     b. Temporarily suspend DC allocation, reclaim previously allocated but unused quotas.
     c. Mark client/SP; no future DC allocations.

Type 2: Disputes Involving External Parties Regarding Clients/SPs in the Pathway

1. Response time is 1-2 weeks.

   • Disputes will be addressed within 1-2 weeks, with both parties providing evidence during this period.

2. Transparency determined through dialogue based on the dispute.

   • Transparency will be decided through discussions between the disputing parties and Cyberport, with the principle of maximizing transparency without compromising customer interests.

3. Accountability determined based on the dispute.

   • Accountability measures will be decided based on the outcome of the dispute:
     a. Temporarily suspend DC allocation, resume after client adjustments and proof.
     b. Temporarily suspend DC allocation, reclaim previously allocated but unused quotas.
     c. Mark client/SP; no future DC allocations.

Type 3: Disputes Involving External Parties Regarding Pathway Applicants Themselves

1. Cyberport supports real-time response.

2. Transparency determined through dialogue based on the dispute.

   • High transparency is supported, with the principle of maximizing transparency without compromising Cyberport's interests.

3. Accountability determined based on the dispute.

   • Accountability measures will be decided based on the outcome of the dispute:
     a. Temporarily suspend Cyberport channel, resume after channel adjustments and proof.
     b. Temporarily suspend Cyberport channel, reclaim previously allocated but unused quotas.

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
FIP, Parameter, and Process Changes When updates requiring announcements of tools, path guides, parameters, and process changes are needed, we will create a FIP in a designated module on GitHub. The FIP, outlining the changes, will be open for discussion by internal channel clients for one week. After FIP approval, a notification will be broadcasted across all channels on Slack. Clients will be given one week to adapt, and the updates will be implemented one week after the notification.

40. How long will you allow the community to provide feedback before implementing changes?:
One 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?:
Management through a Ledger hardware wallet.

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?:
Not implemented through a smart contract model temporarily. If needed during the execution, we will proceed with development.

Monetization

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

1. Data Valuable to the Network:
   For customers whose stored data holds value for the network's data storage, we will only charge technical service fees.

2. Data Not Inherently Valuable to the Forfil Network:
   For customers whose stored data doesn't have intrinsic value to the Forfil network but is based on customer demand:

   • Application Review Service: Free
   • Data Preparation: 1 FIL per terabyte
   • Data Settlement Distribution: 1 FIL per terabyte
   • Audit: Free

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
ND LABS has technical operation centers and nodes in Singapore, Hong Kong, the United States, and Dubai. Since Filecoin has launch of the mainnet in 2020, ND has begun to provide technical services to partners to help them complete the construction of storage services. At present, the accumulated storage power of ND exceeds 700P globally. The largest node has 84P storage power, and the node owns exceeds more than 1.4 million FIL. ND LABS is positioned as a decentralized storage service provider for WEB3.0. For a long time, ND not only focuses on building nodes for partners, but also explores how to provide better storage services for potential clients of web3. Since October 2021, ND has been deeply involved in the FilPlus project, vigorously promoting the Filplus project to partners who has effective data storage needs. We also providing them with a complete set of solutions and technical services for storing data in the FIL network. The Singapore and US nodes are the main storage nodes, which was provide real data storage for early clients.

45. Where will accounting for fees be maintained?:
ND CLOUD and ND will jointly establish a small foundation, and the fee accounting will be managed by this small foundation.

Past Experience, Affiliations, Reputation

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

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
Mainly as storage providers access. ND also the regional lead of Orbit community.

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
Currently, we mainly calculate based on the number of clients * estimated data storage volume. We already have cooperating clients, but the channel for onboarding is not yet in place.

[NDLABS-Leo]

Hi @NDLABS-Leo Wanted to let you know this application has been received along with the Airtable detailed answers - the public answers will be posted in a thread below soon. If you have any questions - please let me know.

Thanks @Kevin-FF-USA

[galen-mcandrew]

Datacap Request for Allocator

Address

f2xllrict42lc2toycwjqpzxt2eii346dudpey2ta

Datacap Allocated

5PiB

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacedlib6ptg6ctov4tx4wsxma62ffqmft3refhsd35m7dj55gouykpu

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

[Kevin-FF-USA]

Hi @NDLABS-Leo

On the next Fil+ Allocator meeting we will be going over each refill application. Wanted to ensure you were tracking the review discussion taking place in filecoin-project/Allocator-Governance#13.

If your schedule allows, recommend coming to the May 28th meeting to answer/discuss the issues raised in the recent distributions. This will allow you to faster address - or, the issue in Allocator Governance for ongoing written discussion.

Warmly,
-Kevin
https://calendar.google.com/calendar/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0%40group.calendar.google.com&ctz=America%2FLos_Angeles

[galen-mcandrew]

Datacap Request for Allocator

Address

f2xllrict42lc2toycwjqpzxt2eii346dudpey2ta

Datacap Allocated

2.5PiB

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacebkiav5sdjdkwndwgypmxlcypgypy3nwzcnk3gwxnnps3edlkauoa

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

[galen-mcandrew]

bafy2bzaceay7aiqmeagk6qwyzuy4orlmuh77zwew7ytbqjuj557qloomfg2em

[galen-mcandrew]

Datacap Request for Allocator

Address

f2xllrict42lc2toycwjqpzxt2eii346dudpey2ta

Datacap Allocated

5PiB

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacebxvlpi3v6y3e2xnwav4c3yxpgsut7zgmmapclgschlwxac6tfhgm

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