Proposal: expire datacap not used by allocators #6
Comments
Kevin-FF-USA
added
the
Proposal
|
I haven't heard objections here -is it to go ahead with this? |
|
We should discuss in the next governance call. I think a month is too short, and we have heard from teams that require longer to build and test pathways. This is also more likely the case for more of the automated and market-based pathways. I think we could amend this proposal. What about:
|
|
those proposed limits sound fine to me |
|
Will add to the upcoming #48 and leave a comment in each Application. Key Points
Here are the Allocators who would be impacted. Web3mine | f03019928 //edit |
|
Hi! This is covering our 3 pathways. Julien |
|
We are also working to clean up old allocations, from previous election cycles. This will include removing DataCap from the previous LDN multisigs, as well as the previous 'direct client request pathways'. Flagging this, as it has been discussed a few times in various governance calls. These notaries go back to the third round of elections in some cases! |
|
luhong123/QC-Data-center#1 |
|
Hello, I'm sorry for the late reply. |
|
Hello , This is Harry from TopBlocks, Sorry for missing so important key info But May i ask you for help
Also json file 1069.json need to be updated Thanks |
|
Hello, We would like to retain the Allocator. We are currently undergoing a comprehensive product upgrade for our hot storage product, Titan Storage, to ensure it offers a better user experience and enhanced service capabilities. We will commence allocation shortly. Demo: Titan Storage Demo |
|
Hello, this is Newwebgroup. We apologize for the omission of such important and critical information. We plan to start distributing DC soon, and will proceed with the allocation in a reasonable and compliant manner according to the plan. |
Hi @newwebgroup
Warmly, |
|
Hello, here is ipfscn. Thank you for the reminder. We have already started the allocation. https://github.com/filplus-bookkeeping/IPFSCN/issues |
|
We have preliminary agreements with some partner clients. But now there is a configuration issue that prevents us from carrying out our work. Please check this issue, filecoin-project/Allocator-Registry#79 . Once this issue is resolved, we should be able to proceed with our allocation work quickly. |
Hi @stcloudlisa |
The application we originally applied for was here. |
Carrying forward a DM into this thread (for transparency) |
|
Remaining Organizations These organizations have yet to provide a timeline or taken any action for DataCap distribution. If not response by end of day, will have the DataCap sunset and need to reapply. Messages sent to each Application, Governance calls for 28May, 11June, 25June, as well as SLACK. Web3mine | f03019928 |
|
Hi @Kevin-FF-USA ! Thanks for reaching out. We wish to remain active. We are in the process of onboarding several PiBs of capacity and have allocated much of the available capacity to storage clients already. We expect to begin using the datacap allocated to this our allocator pathway in the next month. |
If an allocator doesn't take any action on chain in a month after datacap is allocated to them by the fil+ program, it seems maybe worthwhile to revoke that allowance and ask them to re-apply in the rolling applications once their system is ready to distribute datacap.
It seems like there's risk associated with having large outstanding / fragmented allowances.
The text was updated successfully, but these errors were encountered: