[Allocator Application] <Coffee Cloud Company Limited>< CoffeeCloud Gen2 Allocation Pathway> PR #167

[martapiekarska]

Allocator Application

Application Number

recdMFRtHN1dUxxi0

Organization Name

Coffee Cloud Company Limited

Organization On-chain Identity

f14qmuid2b6ne4342m5dk56f4rcr7y5sz4sg5fiwy

Allocator Pathway Name

CoffeeCloud Gen2 Allocation Pathway

Github PR Number

167

Region of Operation

Asia minus GCR

GitHub ID

ccnick

On-chain address

I will provide an address on a later date

Type of Allocator

RFA

Filecoin Community Agreement

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, allocator, or other operating entity
Acknowledge

Type of Allocator and RFA List

RFA: Market-based - Client/SP Fees

Allocator Description

A web-based application will be established for clients to apply for DataCap for a market-determined price.

Contributions to EcosystemData Stewardship: Curate and provide high-quality datasets to be stored on the Filecoin network, enhancing the overall value and utility of the network.

Monetization and Fee structure

Client fees.

Target Clients

Commercial/Enterprise,Individuals

Client Diligence Check

Manual verification

Description of client diligence

First, copy of the official documentation, such as national identification document and/or company registration document, will be requested. Additional authorization documentations will also be requested for commercial and enterprise.
Second, video conference will then be arranged with the prospective clients to verify their personal identity.
Third, our Governance team will evaluate the trustworthiness of the potential clients, and may request notarized documentations, including but not limited to personal or attestation statements.

Type of data

Private encrypted with on-chain deal pricing,Public, open, and retrievable

Description of Data Diligence

Our Governance team will carry the initial content check with our vetted clients, per suggested in the "client diligence" section in stages.

First, an initial small amount of DataCap (e.g. 64 GiB) will be allocated to the vetted clients. After the initial DataCap is consumed by the clients, a full data review will be conduced to make sure the data are align with the scope of our Allocation Program and legal requirements. Proof of data ownership and/or authorization will be requested during this stage. Our clients will not be assigned more DataCap unless (a) their data are align with the objective (including scopes) of our Allocation Program, (b) data ownerships are attested and (c) the data are compliant with all legal requirements.

Second, if the clients passed the initial content check, additional DataCap will be gradually assigned to the clients in multiple rounds. Random, un-announced spot checks will be carried out every 15 working days. Approximately 25% of the newly uploaded data will be reviewed, while 10% of all existing data will also be reviewed.

Data Preparation

IPFS Kubo,Client-provided,Go-CAR

Replicas required, verified by CID checker

1+

Distribution required

Single region of SPs

Number of Storage Providers required

1+

Retrieval Requirements

Public data highly retrievable over Spark.

Allocation Tranche Schedule TypeManual or other allocation schedule.

100 Clients * 0.5 PiB = 50 PiB

Will you use FIDL tooling, such as allocator.tech and other bots?

Yes, all available tools

GitHub Bookkeeping Repo Link

https://github.com/coffeecloud-info/DataCap-Bookkeeping

Success metrics

Amount of data onboarded, daily & aggregate

Timeline to begin allocating to clients

2 months from RKH approval

Funnel: Expected DataCap usage over 12 months

5-50PiB

Risk mitigation strategies

Our Governance team will require official documentations from all of the clients, following the best practices of CA/Browser forum requirements and recommendations of Extended Validation Certificate issuance regarding validating the identities of individuals and organizations.

Dispute Resolutions

For disputes between our clients and other parties, we and/or our affiliates will initiate arbitrations to resolve the disputes. For disputes between us and our clients regarding the discrepancies of DataCap distribution, detailed audit traits will be provided to the notary or Fil+ Governance Team; for other disputes, our team will also first contact the clients in writing, clearly states the non-compliant issue(s) and suggest corrective action(s). If the disputes between the clients and us cannot be resolved, the conversations, internal audit logs and review logs will be provided to the notary or Fil+ Governance Team.

Compliance Audit Check

https://github.com/coffeecloud-info/DataCap-Bookkeeping

Compliance Report content presented for audit

Success metric: Proof of Payments from clients,Data Compliance: Manual report.

Connections to Filecoin Ecosystem

Previous notary,Storage provider

Slack ID

nixklai

[Kevin-FF-USA]

Thanks for applying to serve as an Allocator in the Filecoin Plus Program.
In looking at this application, the TYPE OF ALLOCATOR is currently set to REQUEST FOR ALLOCATOR (RFA). Can you please describe what type of Allocator pathway you wish to operate as a Manual with Market-based - Client/SP Fees.
Specifically - what makes this new pathway DIFFERENT from a Manual review?

For more details on the types of Allocators please check out this blog.
https://blog.allocator.tech/2024/04/allocator-tech-blog.html

[Kevin-FF-USA]

For MANUAL pathways, would like to make you aware that these types of applications are being processes as the network need becomes available. Currently there are ~50 pathways available for Manual reviews, so the priority for onboarding new Allocators is to pathways doing something novel to support the network.

[Kevin-FF-USA]

Hi @2ccnick,

Were you able to make it to any of the Governance Calls or watch the recordings? On the last call we went over the Allocator Applications and guidance on timelines and next steps.

Wanted to share some feedback about this application, because in reading this description, what is being described is a Manual pathway. No real mention of how this market would operate. Also, many of the detailed fields (Monetization for example) are either empty or lacking detail that would give a score high enough to onboard as a new Allocator. This information will play a key part in the scoring mechanisms for this pathway.

Recommending a few options.

1. Check out some of the other applications and the details of their program. Specifics are key - how will this pathway be measured for success and diligence. Right now, there is not much detail. Provide more concrete details. Here is an example of a recently onboarded Application .

2. If you have clients you can demonstrate this by brining them to network with an existing Allocator.
   Bring one of your clients into the ecosystem with an Existing Allocator Pathway. Establish that you have real clients and can maintain the diligence standards of this application. Demonstrate that to the community as the ability and value to onboarding this new Manual Pathway.

Steps

1. Work with any existing Allocator to create an application on behalf of your client. FIDL runs an enterprise Allocator if you were looking for a pathway with existing support in place to help with questions.

2. Once the data is onboarded, reply back to this application with the following
   1. Client ID
   2. Links to the DataCap Application
   3. Spark retrieval %
   4. Verification that the Data reached the targeted number of SP's
   5. What the data type was

Onboarding
Once the ability to onboard clients through the application process has been verified, this application will receive a KYC check and begin onboarding as an Allocator to onboard clients directly.

For questions or support

• There is a live Filecoin Plus Program call every two weeks. Calendar link is here. Or as always please tag us in issue for comment or update.

[Kevin-FF-USA]

Hi @ccnick

Wanted to send a friendly check in.
Did you have any questions about our recommendations for improving the details listed above for the viability of this pathway's application (or bringing a client through an existing pathway)?