Asia minus GCR,Europe,Greater China Region,North America
GitHub ID
Heim94
On-chain address
I have a multisig I want to provide now
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
RFA: Market-based - Client/SP Fees
Allocator Description
Contributions to EcosystemBuild 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.
3rd party Know your business (KYB) service,3rd party Know your customer (KYC) service,Client promise/attestation,Manual verification
Description of client diligence
We verify the client's identity with the help of a third party kyc/kyb way. We'd collect clients' information and record it manully. It probably includes basic information about the client, the client's job information, and the client's basic contact information, so that we can contact the client in time. We may use offline, phone calls, emails, etc. to make contact with our clients.
For paying clients, we need client provide their proof of payment. It's a way to verify their identity. We'll decide the amount of datacap to allocate based on the amount they pay.
Type of data
Public, open, and retrievable,Private encrypted with on-chain deal pricing,Proof of concept, network utilities
Description of Data Diligence
For public data - Need client provide the source of data (website) and the license of dataset.
For private data - Need client provide proof of license for data or ownership of data. Data types need to comply with local laws and regulations. If it is enterprise data, the client needs to provide proof of data authorization from the enterprise.
Data Preparation
Client-provided,Other existing ecosystem tooling
Replicas required, verified by CID checker
5+
Distribution required
Single region of SPs
Number of Storage Providers required
5+
Retrieval Requirements
Public data highly retrievable over Spark.
Allocation Tranche Schedule TypeManual or other allocation schedule.
First allocation: lesser of 5% of total DataCap requested or 50% of weekly allocation rate
Second allocation: lesser of 10% of total DataCap requested or 100% of weekly allocation rate
Third allocation: lesser of 20% of total DataCap request or 200% of weekly allocation rate
Fourth allocation: lesser of 40% of total DataCap requested or 400% of weekly allocation rate
Will you use FIDL tooling, such as allocator.tech and other bots?
Number of clients,Number of returning client customers,Speed of allocations (TTD),Ecosystem marketing/comms
Timeline to begin allocating to clients
1 week from RKH approval
Funnel: Expected DataCap usage over 12 months
50-75PiB
Risk mitigation strategies
From time to time, we will check the client's datacap usage process. We have the right to stop the cooperation in case of violation by the client. If necessary, we will disclose all the information.
Dispute Resolutions
After facing a dispute, we will immediately communicate the case with the client and to publicize the process in time. We'll talk to the gov team about the overall process if necessary.
Compliance Audit Check
We will provide sample reports from FIDL tooling, links to dashboards, and specific data proofs.
Compliance Report content presented for audit
Success metric: onchain report of data onboarded,Success metric: onchain data report,Client Diligence: Client statements, client provided verification,Client Diligence: Legal Review documents,Client Diligence: KYC/KYB report on clients,Data Compliance: Data Samples,Data Compliance: Manual report,Compliance: CID report,Contributions: Github repos with the tools developed.
Allocator Application
Application Number
recfkjiR7qrmBCLRc
Organization Name
Cyberhash
Organization On-chain Identity
f1k67d7ggf3me4ce3t7a45vwmz3krrr2ce4f76d3q
Allocator Pathway Name
Cyberhash-RFA-Allocator
Github PR Number
101
Region of Operation
Asia minus GCR,Europe,Greater China Region,North America
GitHub ID
Heim94
On-chain address
I have a multisig I want to provide now
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
RFA: Market-based - Client/SP Fees
Allocator Description
Contributions to EcosystemBuild 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 fees,SP fees,Block rewards, pools.
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,Client promise/attestation,Manual verification
Description of client diligence
We verify the client's identity with the help of a third party kyc/kyb way. We'd collect clients' information and record it manully. It probably includes basic information about the client, the client's job information, and the client's basic contact information, so that we can contact the client in time. We may use offline, phone calls, emails, etc. to make contact with our clients. For paying clients, we need client provide their proof of payment. It's a way to verify their identity. We'll decide the amount of datacap to allocate based on the amount they pay.
Type of data
Public, open, and retrievable,Private encrypted with on-chain deal pricing,Proof of concept, network utilities
Description of Data Diligence
For public data - Need client provide the source of data (website) and the license of dataset. For private data - Need client provide proof of license for data or ownership of data. Data types need to comply with local laws and regulations. If it is enterprise data, the client needs to provide proof of data authorization from the enterprise.
Data Preparation
Client-provided,Other existing ecosystem tooling
Replicas required, verified by CID checker
5+
Distribution required
Single region of SPs
Number of Storage Providers required
5+
Retrieval Requirements
Public data highly retrievable over Spark.
Allocation Tranche Schedule TypeManual or other allocation schedule.
First allocation: lesser of 5% of total DataCap requested or 50% of weekly allocation rate Second allocation: lesser of 10% of total DataCap requested or 100% of weekly allocation rate Third allocation: lesser of 20% of total DataCap request or 200% of weekly allocation rate Fourth allocation: lesser of 40% of total DataCap requested or 400% of weekly allocation rate
Will you use FIDL tooling, such as allocator.tech and other bots?
Yes, all available tools
GitHub Bookkeeping Repo Link
https://github.com/Heim94/Cyberhash-RFA-Allocator
Success metrics
Number of clients,Number of returning client customers,Speed of allocations (TTD),Ecosystem marketing/comms
Timeline to begin allocating to clients
1 week from RKH approval
Funnel: Expected DataCap usage over 12 months
50-75PiB
Risk mitigation strategies
From time to time, we will check the client's datacap usage process. We have the right to stop the cooperation in case of violation by the client. If necessary, we will disclose all the information.
Dispute Resolutions
After facing a dispute, we will immediately communicate the case with the client and to publicize the process in time. We'll talk to the gov team about the overall process if necessary.
Compliance Audit Check
We will provide sample reports from FIDL tooling, links to dashboards, and specific data proofs.
Compliance Report content presented for audit
Success metric: onchain report of data onboarded,Success metric: onchain data report,Client Diligence: Client statements, client provided verification,Client Diligence: Legal Review documents,Client Diligence: KYC/KYB report on clients,Data Compliance: Data Samples,Data Compliance: Manual report,Compliance: CID report,Contributions: Github repos with the tools developed.
Connections to Filecoin Ecosystem
Big data contributor,Code contributor
Slack ID
Heim