Add new allocator: Allocator

[datacap-bot]

Filecoin Plus Allocator Application

Application Details

Field	Value
Applicant	Allocator
Organization	Oula Network
Address	TBD
GitHub Username

Grant Details

Field	Value
DataCap Amount	5 PiB
Allocation Method	RKH_ALLOCATOR

---

^{This message was automatically generated by the Filecoin Plus Bot. For more information, visit filecoin.io}

[datacap-bot]

Application Status: Rejected ❌

Application Rejected

• We regret to inform you that your application has been rejected

❌ Please contact our support team for more information

---

^{This message was automatically generated by the Filecoin Plus Bot. For more information, visit filecoin.io}

[OulaNetworkOrg]

Hi Galen @galen-mcandrew

I hope you're doing well.

I’m reaching out regarding our application currently listed under the name "Allocator". We would like to kindly request that the applicant name be updated to "Oula Allocator" to better reflect our branding and avoid any potential confusion.

Please let me know if you need any additional information from our side to make this change.

Thanks in advance for your help!

Best regards,

[OulaNetworkOrg]

Hello @Kevin-FF-USA,

Thank you for your valuable feedback during the Governance call on 08 July, 2025. We appreciate the opportunity to clarify and address the concerns raised regarding Oula Network’s Fil+ Allocator application. Below, we provide detailed responses to each point to demonstrate our commitment to transparency, compliance, and alignment with Filecoin’s governance standards. Please let us know if further clarification is needed.

Question 1:
Send email to filplus@fil.org with a company email. This is to demonstrate the OulaNetwork org faces clients for enterprise deals (and isn’t just a person)

Response:
As requested, I’ve already sent the email from our company address to filplus@fil.org. Please let me know if you need anything else.

Question 2:
Get an unchain address. Have it setup. If making Enterprise deals should have this ready to go. Same for the On chain address for DC allocations.

Response:
f1pfupotgwsrx5ahby6yafean7uxfmzc7foeqwb6q

Question 3:
Give more on how you will track metrics and KPIs. If running an enterprise pathway, how will that be tracked (this should be in more detail than a manual pathway)(much more detail)

Response:
Oula Network’s Allocator process is designed to track and report metrics and key performance indicators (KPIs) with precision and transparency, ensuring alignment with Filecoin’s governance and allocation goals. As we are pursuing a manual pathway rather than an enterprise pathway, our approach emphasizes rigorous manual verification and detailed record-keeping to monitor allocation performance, compliance, and abuse prevention. Below, we outline the metrics and KPIs we will track, along with the processes for data collection, validation, and reporting.

1.Allocation Compliance Metrics: To ensure DataCap allocations are used appropriately and align with client applications, we track the following metrics:
a)Dataset Size Validation: We manually verify that the dataset sizes requested by clients match the allocated DataCap. Any discrepancy exceeding 10% of the requested amount is flagged for further review.
b)Retrieval Success Rate: Measures the percentage of successful data retrievals per client and Storage Provider (SP), with a target of at least 80% retrieval success per client.
c)Replica Accuracy: Tracks the number of valid replicas per dataset to ensure compliance with Filecoin’s requirement of a minimum of three replicas per dataset.

2.Performance Scoring System: To evaluate client and SP performance and guide DataCap allocation decisions, we implement a scoring system based on multiple performance criteria. Scores are calculated and used to adjust allocations fairly and transparently.
a)Implements a scoring algorithm to evaluate clients and SPs based on retrieval rates, compliance with allocation rules, and data integrity. Scores are calculated monthly, with weights assigned as follows:
i.DC Received from Others: 20% (2 Points)
ii.SP Retrieval Rate: 30% (3 Points)
iii.Deal Replication: 20% (2 Points)
iv.Deal Shared with Others: 30% (3 Points)
Poor performers (scores <6/10) receive reduced DataCap allocations, while high performers (scores >8/10) are prioritized for additional allocations.
For clients with a score range of 8 to 10, their previous DataCap allocation will be increased by 10%, up to a maximum of 25%. For those scoring between 6 and 8, the previous allocation will be increased by 5%, also up to a maximum of 25%. Clients scoring between 4 and 6 will receive no change to their previous allocation. For clients with a score range of 0 to 4, their previous allocation will be reduced by 5%, with a minimum allocation of 5%.
3.Abuse Prevention Metrics: To prevent misuse of DataCap and maintain network integrity, we manually track metrics focused on identifying and mitigating potential abuse.
a)VPN & Geographic Verification: Cross-referencing client IPs with public VPN databases.
b)Replica & CID Validation: Ensuring allocated datasets are unique and not misused.
c)Onchain Data Integrity Checks: Using blockchain-based verification for transparent audit trails.
d)Score-Based DC Distribution: Poor performance or repeated violations receive reduced allocations or even suspension.

Question 4:
Description of Description of Data Diligence should have more detail.

Response:
Oula Network’s data diligence process is designed to ensure transparency, integrity, and compliance in DataCap allocations, addressing the concerns raised by the Filecoin community. Our automated system implements the following rigorous checks:

1.Dataset Size Verification:
a)Process: Prior to approving a client’s DataCap application, Oula Network conducts a manual review to verify that the requested dataset size aligns with the actual data available. For example, if a client applies for 1 PiB but only 500 TiB of verifiable data can be identified, the application is flagged for further scrutiny to prevent over-requesting. After the initial allocation (e.g., 256 TiB as per the standard tranche schedule), a secondary manual check is performed to cross-reference the allocated DataCap against the actual encapsulated data, using on-chain data to validate consistency. Any discrepancy exceeding 20% triggers a manual review to investigate potential misuse or errors.
b)Implementation: The verification process relies on manual checks by Oula Network’s team. For pre-application reviews, we assess the client’s submitted dataset details against the requested DataCap, ensuring the proposed dataset is verifiable and matches the stated size. Post-allocation, we manually query Filecoin’s blockchain-based metadata to confirm that the encapsulated data corresponds to the allocated DataCap. For instance, if a client encapsulates only 200 TiB of an approved 256 TiB allocation, this discrepancy is flagged for further investigation to ensure compliance.
Outcome: Reduces over-allocation risks, ensuring DataCap is used efficiently and aligns with actual storage needs.

2.Data Downloadability and Description Consistency:
a)Process: Oula Network verifies that data encapsulated in sectors is downloadable and consistent with the dataset description provided in the client’s application. This involves manually sampling stored data and attempting retrievals using Filecoin’s retrieval protocols to confirm accessibility. The dataset description is cross-checked against the actual content to ensure alignment.
b)Implementation: OulaNetwork’s team conducts periodic manual retrieval tests on a sample of sectors to ensure at least 80% are accessible via Filecoin’s standard retrieval mechanisms. To validate description consistency, we manually compare the dataset’s metadata (e.g., CIDs, file types) with the client’s submitted documentation. Any mismatches, such as a dataset described as “genomic data” but containing unrelated content, are flagged for further review and documented in our allocation reports.
Outcome: This manual verification process ensures data integrity, prevents misuse and maintains trust in the Filecoin network by confirming that stored data is both accessible and accurately represented.

3.Sector Data Indexing for Community Access:
a)Process: Oula Network maintains a comprehensive index of encapsulated data to enable the Filecoin community to locate and download specific sectors. The index includes key details such as Content Identifiers (CIDs), sector IDs, client IDs, and a concise description of the dataset’s content. This index is designed to facilitate transparent access to stored data, allowing community members to verify and retrieve sectors as needed.
b)Implementation: The index is manually compiled and updated by Oula Network’s team, ensuring accuracy and relevance. It is published on a publicly accessible platform integrated with Filecoin’s ecosystem, such as a dedicated webpage or Filecoin-compatible repository. For example, a dataset entry like “CID: bafy..., sector ID: 12345, client ID: XYZ, description: climate research data” allows community members to query the index, locate the corresponding sector, and initiate retrievals using standard Filecoin tools.
Outcome: The index enhances transparency by providing clear, accessible documentation of encapsulated data, enabling community members to independently verify and access sectors, thereby fostering trust and accountability in the allocation process.

Question 5:
If public open data, what SPARK % for retrieval will you hold clients to (and you will be held to in an Audit)

Response:
Specifically, for any DataCap batch allocated to at least three clients, no single client will be permitted to exceed 40% of the total retrieval volume during audits. This ensures equitable distribution of retrieval responsibilities and prevents any single client from monopolizing access to public data.

Question 6:
Tranch Schedule - What does the first time applicant receive.

Response:
As a first-time applicant, Oula Network proposes to adhere to the standard allocation tranche schedule recommended by FIDL, which is well-suited for our manual Allocator pathway. The schedule is as follows:

1.First Allocation: Maximum 5% of total DataCap, capped at 256 TiB.
2.Second Allocation: Maximum 10%.
3.Third Allocation: Maximum 15%.
4.Fourth Allocation: Maximum 20%.
5.Fifth and Subsequent Allocations: Maximum 25%.

Question 7:
Disclose relationship to IPFSFORCE.

Response:
Oula Network is an independent organization with no operational or structural affiliation with IPFSForce. Regarding Steven Li, he is one of several investors in Oula Network. Oula Network maintains full autonomy in its strategic and operational activities, including its pursuit of the Fil+ Allocator role.