[Allocator Application] <Aleo Pool>< Aleo Pool> PR #199

[martapiekarska]

Allocator Application

Application Number

recSfPh76d1q0jsw2

Organization Name

Aleo Pool

Organization On-chain Identity

f1xyonjjbcuzlz6oenocllmwyt66jke3gx64ratyq

Allocator Pathway Name

Aleo Pool

Github PR Number

199

Region of Operation

Asia minus GCR,Greater China Region,North America

GitHub ID

Aleo-pool-work

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 - Client/SP Fees

Allocator Description

1. When a client submits a request through our allocator, we will require the client to stake 2 FIL per TiB of Datacap in the upcoming round and also pay a review fee of 10 FIL per application.
2. The client needs to transfer funds to our developed contract for staking. Once staking is complete, we will review the information and allocate Datacap after approval.
3. After the client completes the Datacap sealing, the contract will retrieve the sealed data from the blockchain and transfer the staked funds to the storage provider (SP) that completed the sealing.

Contributions to EcosystemDevelop Open-Source Tools

Monetization and Fee structure

Client fees.

Target Clients

Web3 developers,Nonprofit organizations,Commercial/Enterprise,Individuals

Client Diligence Check

3rd party Know your business (KYB) service,3rd party Know your customer (KYC) service,On-chain deal pricing

Description of client diligence

1. Client Identity Verification: We will perform background checks on enterprise clients using social media and business history to confirm legitimacy.
2. Data Ownership Verification: Clients must provide business-related data, verified through metadata or encryption proofs to confirm ownership.
3. Mitigating Sybil Attacks: Implement rate limits and account verification to prevent multiple false applications. Datacap allocation will increase progressively based on performance.
4. Audit Mechanism: Chain-based transaction records will provide evidence of client deposits, payments, and data sealing for governance auditing.

Type of data

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

Description of Data Diligence

1\.	**Data Compliance Verification**: We will cross-check the data against local and regional laws using legal resources and compliance tools to ensure the data meets regulations.
2\.	**Ownership Validation**: Clients must provide cryptographic proofs of ownership, such as metadata or legal documentation.
3\.	**Data Sampling**: We will randomly sample and review datasets, checking format, size, and content type.
4\.	**Tools for Verification**: Chain-based tools (like CID checks) will be used to confirm the stored data matches the client’s initial claims.

Audit Evidence: For governance audits, we will present metadata logs, transaction proofs, cryptographic hashes, and legal documentation confirming ownership and data compliance.

Data Preparation

Other existing ecosystem tooling,Client-provided

Replicas required, verified by CID checker

4+

Distribution required

Equal distribution of deals across regions

Number of Storage Providers required

5+

Retrieval Requirements

Public data highly retrievable over Spark.

Allocation Tranche Schedule TypeStandardized scaling tranche schedule.

50

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

Yes, all available tools

GitHub Bookkeeping Repo Link

https://github.com/Aleo-pool-work/Allocator-Aleo-pool

Success metrics

Number of clients,Retrievability of data,Number of paid deals,Amount of data onboarded, daily & aggregate

Timeline to begin allocating to clients

1 month from RKH approval

Funnel: Expected DataCap usage over 12 months

100-200PiB

Risk mitigation strategies

1.Operational Security (OpSec) Standards: Adopting strict security protocols, such as encrypted data transmission, authentication mechanisms, and access controls, to safeguard data integrity and privacy.
2.User Agreements: Enforcing clear user guidelines prohibiting illegal or malicious activities, which users must agree to follow.
3.Alert Systems: Setting up monitoring and alerts to detect unusual or abusive behavior in real-time.
4.Rate Limiting: Implementing access and transaction rate limits to prevent misuse.

Dispute Resolutions

1.First, transparent communication will be initiated. All parties need to explain their positions clearly and promptly, ensuring transparency and leaving records on GitHub.
2.Review the audit logs. By examining transaction records, client data, and allocation processes, the root cause of the issue will be identified.
3.Neutral arbitration: If the issue cannot be resolved internally, it will be escalated to the Fil+ governance team or notaries for arbitration during a notary meeting.

Compliance Audit Check

1.Example reports: Generate regular reports outlining the DataCap allocation, consumption, and client activity, showing adherence to rules.
2.Dashboard links: Provide access to a dashboard with real-time data, such as SP performance, DataCap usage, and compliance metrics.
3.Specific data proofs: Use on-chain data to demonstrate transactions, including client payments and data retrieval statistics, to confirm transparency.

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: Proof of provenance report,Data Compliance: Data Samples,Compliance: CID report,Contributions: Github repos with the tools developed,Client/Data Compliance: external third-party audit .

Connections to Filecoin Ecosystem

Developer

Slack ID

Aleo-pool-work