Test app 1025

[NateWebb03]

No description provided.

[NateWebb03]

Notary Allocator Pathway Name:

Enterprise data - HK CyberPort pathway

Organization:

ND LABS

Allocator's On-chain addresss:

F1s5sho3yqbxjuk4pavpo2sc5gpka2cnm3egjcaga

Country of Operation:

Singapore

Region(s) of operation:

North America,Asia minus GCR

Type of allocator:
What is your overall diligence process? Automated (programmatic), Market-based, or Manual (human-in-the-loop at some phase). Initial allocations to these pathways will be capped.

Manual

Amount of DataCap Requested for allocator for 12 months:

150PiB

Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing?

Enterprise data - HK CyberPort pathway is primarily an application channel for incubating, accelerating, and investing in web3.0 startups. As Cyberport aims to assist entrepreneurs in establishing themselves in Hong Kong and expanding globally, the goal is to advance further in web3.0. The advisory team comprises industry leaders. The global web 3.0 acceleration program has been initiated with a fund of USD 1 million. This program will provide financial support to selected projects, offering benefits such as mentorship, investment incubation, technical support, marketing promotion, industry connections, and policy and legal consultation. The channel will serve as the DataCap application pathway for these selected enterprises. What makes this channel unique is that these enterprises are carefully screened by Cyberport, ensuring that they have the potential to rapidly grow into unicorns in the web3 domain, with higher-quality data.

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.
Additionally, I will adhere to all local & regional laws & regulations that may relate to my role as a business partner, organization, notary, or other operating entity. *
You can read the Filecoin Code of Conduct here: https://github.com/filecoin-project/community/blob/master/CODE_OF_CONDUCT.md

Acknowledgment: Acknowledge

Cient Diligence Section:

This section pertains to client diligence processes.

Who are your target clients?

Other (specified above)

Describe in as much detail as possible how you will perform due diligence on clients.

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.

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

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.

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

Anyone can apply, but the DC allocation from our channel is only provided to enterprises collaborating with Enterprise data - HK CyberPort pathway.

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

This section will cover the types of data that you expect to notarize.

As a reminder: The Filecoin Plus program defines quality data is all content that meets local regulatory requirements AND
• the data owner wants to see on the network, including private/encrypted data
• or is open and retrievable
• or demonstrates proof of concept or utility of the network, such as efforts to improve onboarding

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, transmitting, or accessing of data.

Acknowledgement: Acknowledge

What type(s) of data would be applicable for your pathway?

Other (specified elsewhere)

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. Within the enterprise system of cyberport, we have detailed information about these enterprises. Only by having complete information about the enterprise can it be within the scope of cooperation with web3 labs. Additionally, we use a random sampling method with user data for business matching.

How will you ensure the data meets local & regional legal requirements?

All the enterprises collaborating with Cyberport will comply with local legal requirements in Hong Kong.

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.

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

This section covers deal-making and data distribution.

As a reminder, the Filecoin Plus program currently defines distributed onboarding as multiple physical locations AND multiple storage provider entities to serve client requirements.

Recommended Minimum: 3 locations, 4 to 5 storage providers, 5 copies

How many replicas will you require to meet programmatic requirements for distribution?

5+

What geographic or regional distribution will you require?

There need to be distributions in at least 4 regions.

How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?

5+

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.

What tooling will you use to verify client deal-making distribution?

Tools such as datacapstats.io and CID checker bot

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.

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

In this section, you will explain your client DataCap allocation strategy.

Keep in mind the program principle over Limited Trust Over Time. Parties, such as clients, start with a limited amount of trust and power.
Additional trust and power need to be earned over time through good-faith execution of their responsibilities and transparency of their actions.

Will you use standardized DataCap allocations to clients?

No, client specific

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.

Will you use programmatic or software based allocations?

No, manually calculated & determined

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.

Describe the process for granting additional DataCap to previously verified clients.

We will try SA Bot.

Tooling & Bookkeeping

This program relies on many software tools in order to function. The Filecoin Foundation and PL have invested in many different elements of this end-to-end process, and will continue to make those tools open-sourced. Our goal is to increase adoption, and we will balance customization with efficiency.

This section will cover the various UX/UI tools for your pathway. You should think high-level (GitHub repo architecture) as well as tactical (specific bots and API endoints).

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
• dispute discussion & resolution
• community updates & comms

- 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.

Will you use open-source tooling from the Fil+ team?

Yes, through GitHub repositories, Google Spreadsheets, and bot tools.

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

This framework ensures the responsible allocation of DataCap by conducting regular audits, enforcing strict compliance checks, and requiring allocators to maintain transparency and engage with the community. This approach safeguards the ecosystem, deters misuse, and upholds the commitment to a fair and accountable storage marketplace.

In addition to setting their own rules, each notary allocator will be responsible for managing compliance within their own pathway. You will need to audit your own clients, manage interventions (such as removing DataCap from clients and keeping records), and respond to disputes.

Describe your proposed compliance check mechanisms for your own clients.

Based on the proposal at filecoin-project/notary-governance#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.

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.

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.

How long will you allow the community to provide feedback before implementing changes?

One week.

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.

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

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.

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

Enterprise data - HK CyberPort pathway will primarily categorize customer value as follows:

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

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.

Where will accounting for fees be maintained?

Cyberport and ND will jointly establish a small foundation, and the fee accounting will be managed by this small foundation.

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

filecoin-project/notary-governance#697

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.

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.