blog.allocator.tech

In November 2023 the Fil+ Governance team announced move from Notary triggered DataCap allocation to an Allocator system. The program is evolving and we thought it would be useful to document the process of being an Allocator and what is the right way for you to receive DataCap.  There are 2 ways of becoming an allocator: Respond to the Request for Allocator Propose your own Allocator.  If you are proposing your own Allocator you will need to prove the novelty of your solution - whether it is the way you will select your clients, the economics of your allocator, the way you will manage it etc. As the number of Allocators grow we will move to a meta allocator structure, where Allocators operating in similarly will be aggregated under a meta-allocator, and meta allocators will report to Root Key Holders.  Useful Links: Registry of all active allocators The proposal   (Github link) FAQ for Allocators  (created by FIDL team, takes you to an external website) More about Fil+ Governance  (Gi

As we described in a previous post, there are two ways of becoming an Allocator - either you respond to this RFA or propose your own, novel Allocator. Introduction At present, we have a vast selection of Allocators falling under the Manual (requiring human intervention) Meta-allocator structures. The governance team of Fil+ program would like to encourage the community to run allocators in other meta-pathways. This RFA enlists types of Allocators that, we believe, will contribute to growing a healthy system and faster allocation of DataCap to honest SPs.  Types of Allocators The types of Allocators we are seeking: In Automated Meta-Pathway: Github WeChat and other social media Staked FIL up-front In Market Based Meta-Pathway: Fee based Auction based Proof of Payment In Experimental Meta-Pathway Anonymous-review-guild Research Archival Details Github Allocator Similar to how Glif Verifier worked. This allocator would run a service verifying a Github account and upon verification of a Gi