[Allocator Application] <Haven DP>< Client Vetted Pathway> PR #181

[martapiekarska]

Allocator Application

Application Number

recKOsnO9KqybMOAq

Organization Name

Haven DP

Organization On-chain Identity

f1mhd5x2d3gybsplhi2apqluxk6ircldusszf4miy

Allocator Pathway Name

Client Vetted Pathway

Github PR Number

181

Region of Operation

Africa,Asia minus GCR,Europe,Greater China Region,North America,South America,Oceania

GitHub ID

@haven-allocator

On-chain address

I will provide an address on a later date

Type of Allocator

Similar to existing allocator pathways

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

Manual - Novel pathway

Allocator Description

• Leverage Haven's current business model that is incentivized by gaining the support of our FIL initial pledge investors (who are interested in investing with a focus in the long term development of the Filecoin Network). They want to see projects onboarding datasets from vetted client bringing “value to the network” and ultimately partnering with vetted SP entities (third party KYB, known node locations disclosed upfront) that are storing copies to meet client needs.
• Enable Filecoin Network economic growth by ensuring upfront that multiple entities are vetted and involved in each data onboarding project and that data is distributed geographically in 2+ geographically dispersed locations.
• Require that data diligence processes are in place to be able to validate all information about the source data and preparation upfront and perform proper checks on data distribution throughout onboarding. 
• Upfront source data checks would include:
  • Because the client data is private in this pathway, we will focus on a complete vetting of the client via KYC/KYB third party check and questionnaire about the business and dataset
• Upfront Data Preparation validation would include:
  • Partnering with experienced Filecoin data preparer(s) who will be compensated for their time and effort in allocator projects and who can provide:
    • Clear documentation on how the data is prepared / transformed between the source data set and the data stored in Filecoin
    • Deals / Pieces stored to Filecoin should be full - there should not be significant 'slack' or 'padding' in stored data
    • Individual semantic items of the data should be able to be individually referenced / accessed.
    • When a piece is downloaded from the stored dataset, there must be a way to identify what part of the original dataset that piece represents and confirm that it is indeed valid data from the dataset. (this could be e.g. provided via a log file indicating the mapping of offsets / files into stored deals)
• Data Distribution checks would be conducted after each allocation to ensure entities are storing copies of the dataset as described upfront

Contributions to EcosystemOnboard >10PiBs of Data,Host or sponsor community events such as meetups, hackathons, conferences, FilDev summits etc,Build better data onboarding pathway

Monetization and Fee structure

Client fees,SP fees,Block rewards, pools,Other. Currently, our business processes involve splitting all storage deal block rewards proportionally between FIL Initial Pledge Investors and Storage Providers. Haven takes a portion of the block rewards as a fee for their work in investor/SP diligence and FIL allocation services. This fee will remain in place for SPs using pledge funding.

Additionally, as part of this allocator, fees toward services will need to be accounted for including:

• Coordination of quality dataset preparation (Data Preparer)
• Coordination of SPs and distribution of DataCap per client guidelines
• Confirmation to the adherence of data distribution requirements
• Administration of the allocator (diligence, allocation mgmt)

These fees could take the form of an adjusted proportional split of the deal block rewards for all parties mentioned above and/or could involve payment by Clients and/or Storage Providers for these additional services.

Target Clients

Commercial/Enterprise

Client Diligence Check

3rd party Know your business (KYB) service,3rd party Know your customer (KYC) service,NDA with additional verification,Manual verification

Description of client diligence

The “client” in our vetted client allocator pathway is an actual vetted client that wants to store copies of a quality, valuable dataset on Filecoin.  The client may be guided by a data preparer or storage provider and all parties will be vetted upfront, prior to project start, via a third party KYC/KYB/AML service and also a Filecoin wallet check service.  Any entity is eligible to join the allocator project as an investor, data preparer or storage provider as long as they meet and pass any client ana allocator pathway criteria and agree with the project structure and fees.

Type of data

Private encrypted with on-chain deal pricing

Description of Data Diligence

Because the data is private, we will focus on a complete vetting of the client via KYC/KYB third party check and questionnaire about dataset The data preparer will be required to provide:

• Clear documentation on how the data is prepared / transformed between the source data set and the data stored in Filecoin
• Individual semantic items of the data that are able to be individually referenced / accessed.
• When a piece is downloaded from the stored dataset, there must be a way to identify what part of the original dataset that piece represents and confirm that it is indeed valid data from the dataset. (this could be e.g. provided via a log file indicating the mapping of offsets / files into stored deals)

Data Preparation

Other existing ecosystem tooling,RIBS,Singularity,Go-CAR,IPFS Kubo,Client-provided

Replicas required, verified by CID checker

1+

Distribution required

Equal distribution of deals across regions

Number of Storage Providers required

1+

Retrieval Requirements

Private data not retrievable.

Allocation Tranche Schedule TypeManual or other allocation schedule.

Allocations will be given as a percentage of the total amount requested. Initial allocations will be 10-15% of total requested, up to 1PiB max. Subsequent allocations will be proportional up to 4 allocations. Example: 10%, 20%, 30%, 40%

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

Yes, all available tools

GitHub Bookkeeping Repo Link

https://github.com/haven-allocator/vetted-client-dataset

Success metrics

Number of clients,Number of paid deals,Amount of data onboarded, daily & aggregate,Speed of allocations (TTD)

Timeline to begin allocating to clients

1 week from RKH approval

Funnel: Expected DataCap usage over 12 months

75-100PiB

Risk mitigation strategies

All parties involved an a data onboarding project on our allocator will agree to terms of the onboarding plan upfront. Haven requires signed contracts for all parties. This includes the Data Preparer that will complete the documentation and preparation of CIDs. Also, the SPs agreeing to a plan for depositing their portion of FIL toward the pledge, storing cold copies, hot copies, and ensuring geographical distribution and distribution plan. All SP entities involved go through KYC/KYB upfront and disclose location of nodes and agree to terms of storage plan. Any party not meeting contract requirements or found abusing their role will risk delaying or losing their FIL block reward payout per contract.

Dispute Resolutions

A dispute within the context of DataCap allocation refers to any contention or disagreement arising between parties involved in the storage and retrieval of data on the Filecoin network. This could involve discrepancies over DataCap distribution, disagreements on data compliance with stated parameters, or conflicts over the execution of storage deals. Disputes may be internal, involving yourself and your client, or external, where you will need to defend your decisions against another active notary or the Fil+ Governance Team. For disputes between our allocator and client, hereby termed appeal(s), we will source the appeals using our own Open Data Allocator Appeals Form (https://docs.google.com/forms/d/e/1FAIpQLSd4QvDDByzhTSmIKuLdNEoSapszTG8tPdSVPkYtvubq4hbOdg/viewform) for all our clients where they can submit an appeal and someone on the team will address it with a 5 day SLA. We would like to respect the privacy of the client and do not plan to host a public resolution process. For disputes raised by community members/non-clients about our allocation approach and strategy, we will comply with the public dispute tracker that is being built by the Filecoin Foundation Governance Team and will commit to an SLA of 10 days.

Compliance Audit Check

After each allocation we will manually review the on-chain deal making activity of the applicant to confirm compliance relying on: Allocator Compliance and CID compliance reports to identify non-compliance of deal making and distribution. At any point if a party is caught providing fake or misleading information about themselves or their SP partners, we will close any open applications and add the GitHub user IDs and miner IDs involved and block them from future participation in the allocator.

Compliance Report content presented for audit

Success metric: Proof of Payments from clients,Success metric: onchain report of data onboarded,Success metric: onchain data report,Client Diligence: Client statements, client provided verification,Client Diligence: KYC/KYB report on clients,Data Compliance: Manual report,Compliance: CID report,Client/Data Compliance: external third-party audit .

Connections to Filecoin Ecosystem

Previous allocator,Event sponsor

Slack ID

@kz

[haven-allocator]

As an additional note about Haven Digital Partners current contributions in the Filecoin ecosystem, in the past five months Haven has delegated 3M FIL to seven different SP entities enabling projects to seal 75PiBs (QAP) of data

[Kevin-FF-USA]

Hi @haven-allocator,

One of the scoring mechanisms for pathways is their ability to onboard quality data to the network. Given your existing clients, suggesting a proposal to help establish your ability within the ecosystem to serve as an Allocator performing MANUAL diligence.

Proposal 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 @haven-allocator

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)?

[haven-allocator]

No questions at this time @Kevin-FF-USA - we will work to onboard through an active allocator for now and return to this after. Thank you.