Kevin-FF-USA
commented
1 month ago Hi @Conor15,
Thanks for the note in SLACK. Wanted to add some of the conversation there - into this application for easier tracking. First off - thanks for appling to be an Allocator. How did you hear about Filecoin Plus?
Wanted to give you some early notes on sections which would benefit from additional information.
Allocator Type Market Based - Proof of Payment.
- Recommend you provide details of how the proof of payment will operate. Is the service already created or will you be building some new? Have you already tested or have a process created? What will it be?
- Recommend you check out other Applications of this type - ex: https://github.com/filecoin-project/notary-governance/issues/1073
Dispute Resolutions
- What does it mean to "Punish results on Github"? Ideally you spell out what steps you would take in the communication with an application.
- Recommend you look at a few examples from existing Allocators applications (https://github.com/filecoin-project/Allocator-Governance/discussions/58)
Description of Data Diligence
- These steps read like a MANUAL review. How will your Proof of Payment operate in this process?
Retrieval Requirements.
- Data onboarded should be open and public. The retreival method being used at Fil+ as a standard is SPARK. If you havent yet tested with SPARK, recommend you look at the Spark metrics: https://grafana.filstation.app/d/fea90509-20e8-4d49-b4ad-f0436da9c75d/spark-public-dashboard?orgId=1
- For new Allocators there will be the expectations that they are compatible with SPARK for retrieval verification.
Conor15
Allocator Application
Application Number
recL033b2WWTlhsv3
Organization Name
DataFly
Organization On-chain Identity
f1u6pukitc37mcot546mtf5bmxml3bezve3vwiqdq
Allocator Pathway Name
DFly Allocator Pathway
Github PR Number
97
Region of Operation
Asia minus GCR,Europe,Greater China Region,North America
GitHub ID
Conor15
On-chain address
I have a multisig I want to provide now
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 - Proof of payment
Allocator Description
Contributions to EcosystemBuild better data onboarding pathway,Onboard >10PiBs of Data,Data Stewardship: Curate and provide high-quality datasets to be stored on the Filecoin network, enhancing the overall value and utility of the network.,Host or sponsor community events such as meetups, hackathons, conferences, FilDev summits etc
Monetization and Fee structure
SP fees,Client fees,Block rewards, pools,Client staking.
Target Clients
Web3 developers,Nonprofit organizations,Commercial/Enterprise,Individuals,Open/Public
Client Diligence Check
3rd party Know your business (KYB) service,3rd party Know your customer (KYC) service,Automated deterministic,Client promise/attestation,Manual verification,On-chain deal pricing
Description of client diligence
First, we'll do KYC checks about client's identity, address, and source of funds. Next, we'll turn to do risk assessment which associated with the client based on various factors such as their business activities, geographic location, and political exposure. Then, we'll prepare some questions about Filecoin and data storage to clients. Once the above is verified, we will document and partially disclose it on github.
Type of data
Private encrypted with on-chain deal pricing,Public, open, and retrievable
Description of Data Diligence
First, we will ask clients to provide proof of data owner. Next, we will ask our clients to provide a part of data for us to download and check. All checks will be done both by program and by person. After above are verified, we will disclose on github.
Data Preparation
Client-provided,Singularity
Replicas required, verified by CID checker
4+
Distribution required
Single region of SPs
Number of Storage Providers required
4+
Retrieval Requirements
Public data highly retrievable over Spark.
Allocation Tranche Schedule TypeManual or other allocation schedule.
Allocation in proportion to the number of client requests.
Will you use FIDL tooling, such as allocator.tech and other bots?
Yes, all available tools
GitHub Bookkeeping Repo Link
https://github.com/Conor15/DFly-AllocatorPathway
Success metrics
Number of paid deals,Retrievability of data,Speed of allocations (TTD)
Timeline to begin allocating to clients
1 week from RKH approval
Funnel: Expected DataCap usage over 12 months
5-50PiB
Risk mitigation strategies
We do not allocate all the amounts required by the client at one time. Once a problem is encountered, we will immediately stop allocating datacap to clients. Once the problem was solved, it was back to business as usual.
Dispute Resolutions
We will communicate with clients in a timely manner. Then we publish the results on github.
Compliance Audit Check
We will use FIDL's tools to generate audit reports and provide results.
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: Financial Audits and Credit Check reports,Client Diligence: KYC/KYB report on clients,Data Compliance: Proof of provenance report,Data Compliance: Data Samples,Data Compliance: Manual report,Compliance: CID report.
Connections to Filecoin Ecosystem
Code contributor,Storage provider,Big data contributor
Slack ID
Conor