Proposal: Manual Pathway MetaAllocator

[Kevin-FF-USA]

Issue Description
The governance team is proposing the creation of a Manual Pathway MetaAllocator to streamline DataCap allocation for Manual Allocators. This new system aims to increase the speed of datacap refresh, reduce the back and forth in diligence reviews, and improve accountability by placing all Manual Allocators under a unified governance structure. To begin this process, proposing 100 PiBs from Root Key Holders, while will allocate DataCap that is available for audits and ongoing allocation refresh distributions.

Currently every Manual Allocator application as well as applications for Data Cap are reviewed by the governance team who then requests the Root Key Holders to approve DataCap allocation for that Manual Allocator. This creates additional level of complexity and opportunities for delays. This proposal is for those Manual Allocators that are ready receive refresh to receive DataCap from a shared pool held by the Manual Pathway MetaAllocator, which will be managed by the governance team. The goal is faster processing time for Datacap refresh to meet community needs.

Details
In the design of (v5 cycle) which created the Allocator process for Fil+, the intention was to create a tree structure with groups of allocators being governed by MetaAllocators, with the responsibility structure of parent (MetaAllocator) being held accountable for managing and holding accountable the children (allocators). This was first raised by FIDL in a Blog from April 2024 outlining the application process blog post]

Until 2025, creating MetaAllocators was not possible due to the lack of the Smart Contract code to run MetaAllocators. Over the course of 2024, FIDL has been in development of such a Smart Contract, which in now ready. This Smart Contract has been [audited by Composable Security] and [tested out in the automated allocator] on [[faucet.allocator.org (http://faucet.allocator.org/)]. Based on reported success in testing now proposing rollout of this framework to create a new MetaAllocator to govern current and future Manual Allocators.

Graphics
New Model

Previous Model

Proposing

1. Feedback from the allocator community. (via this issue or on the upcoming Governance Calls for Fil+)

2. FIDL to deploy an instance of the Smart Contract that will hold the DataCap Allocation.

3. Root Key Holders to approve a transfer of an initial 100PiBs of DataCap to this contract. This amount will allow us to conduct refresh of Data Cap for outstanding audits.

Next Steps
Pending the community discussion and input, will be submitting a simultaneous application for a MetaAllocator through GitHub on behalf of the Governance team.

[Kevin-FF-USA]

Hello,
With this proposal open, wanted to propose a slight update to the timelines.
This proposal will substantially reduce the wait times between approval of Refresh between Governance Team and the RKH.

Updating the review and discussion period of this proposal FROM: 18Feb Governance call TO: Friday 07Feb. This will allow the applications for refresh to be processed and approved (without having to wait another 2 weeks).

Open for community feedback.

[Kevin-FF-USA]

Request for pathway DC setup in issue: #289

[Destore2023]

The small changes but big step on FIL+

[Destore2023]

Hello, With this proposal open, wanted to propose a slight update to the timelines. This proposal will substantially reduce the wait times between approval of Refresh between Governance Team and the RKH.

Updating the review and discussion period of this proposal FROM: 18Feb Governance call TO: Friday 07Feb. This will allow the applications for refresh to be processed and approved (without having to wait another 2 weeks).

Open for community feedback.

Hope to see the detail in the upcoming meeting.