Open martapiekarska opened 2 months ago
Hi Timequant, I guess @galen-mcandrew must have missed your application - bad timing with ETH Brussels. Thank's for bringing it up on slack.
While it is not in my power to review the application, would you be able to provide details on how the client staking would work and how would you automate it? From the governance meetings, I heard Galen saying that novel applications will be prioritised/manual allocators will be deprioritised.
Hi @martapiekarska, thanks for your kindly review. Our allocator depends on the amount pledged by the client to determine the amount of datacap to be allocated to the client. Clients can submit their applications through our website, and when their applications are approved by us, we will allocate datacap to the clients. We get the client's datacap usage report through the cid checker bot. When the data in the report meets our allocator's requirements, we return their pledges to the client. This is how our allocator runs.
Allocator Application
Application Number
recLsLI5iAVbsHyez
Organization Name
TIMEQUANT
Organization On-chain Identity
f1t3hdbfsje37rtsu23d24jxmedgbka66oacjifzy
Allocator Pathway Name
Client Staking allocator
Github PR Number
81
Region of Operation
Asia minus GCR,Europe,Greater China Region,North America,Oceania,South America,Africa
GitHub ID
lilimengm
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: Automated - Client staking
Allocator Description
Contributions to EcosystemOnboard >10PiBs of Data,Build better data onboarding pathway,Data 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 staking.
Target Clients
Web3 developers,Nonprofit organizations,Commercial/Enterprise
Client Diligence Check
3rd party Know your business (KYB) service,3rd party Know your customer (KYC) service,Client promise/attestation,Manual verification,On-chain deal pricing
Description of client diligence
First, we require clients to provide personal information such as name, email address or other ways. We will verify their provided information through email or these ways. Also we will use 3rd party KYB/KYC service to do verification. It can make us conduct background checks on the client to verify their employment or business registration information. We will establish trust by providing secure payment options. Ensure that clients' transactions are secure and private. All records will be strored in github as a bookkeeping.
Type of data
Private encrypted with on-chain deal pricing,Public, open, and retrievable,Proof of concept, network utilities
Description of Data Diligence
Our data diligence involve assessing the security and privacy of the data, ensuring that it is compliant with relevant regulations and standards, and documenting the entire process for future reference and auditing. We request data samples from clients and we keep them on file. A random sample of the data packaged by the client will be checked against the sample of the data within one month of each allocation by us. We will communicate publicly with our clients on github if there are any problems. In future we'll work on programs to automatically verify that the data matches.
Data Preparation
Client-provided,Go-CAR
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 of datacap according to the amount staked by the client.
Will you use FIDL tooling, such as allocator.tech and other bots?
Yes, all available tools
GitHub Bookkeeping Repo Link
https://github.com/lilimengm/TQ-clientstaking-allocator
Success metrics
Number of clients,Number of paid deals,Retrievability of data
Timeline to begin allocating to clients
1 month from RKH approval
Funnel: Expected DataCap usage over 12 months
75-100PiB
Risk mitigation strategies
We will design a program to check data actually allocated by clients to ensure that the speed is matching as their plans. Also, we manually check the usage from time to time. By using FIDL Tooling, we will stop the allocation of datacap as soon as we find out that our clients are using it abnormally. And we will keep the report on github.
Dispute Resolutions
We will not allocate more datacap to a client until the dispute is resolved. We'll put a record of the internal dispute on github. We will invite the gov team to participate in an online meeting with another notary to discuss the dispute. All disputes will be resolved in an open and fair way.
Compliance Audit Check
We will use cid checker and our own developed tools to get clients' usage report. https://filplus.starboard.ventures/
Compliance Report content presented for audit
Success metric: Proof of Payments from clients,Client Diligence: KYC/KYB report on clients,Compliance: CID report,Success metric: onchain report of data onboarded,Client Diligence: Client statements, client provided verification,Data Compliance: Manual report.
Connections to Filecoin Ecosystem
Storage provider,Big data contributor
Slack ID
liliM