Open willscott opened 6 months ago
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 https://github.com/filecoin-project/Allocator-Governance/issues/48 and leave a comment in each Application.
Key Points
Here are the Allocators who would be impacted. Please see discussion https://github.com/filecoin-project/Allocator-Governance/discussions/59 for additional metrics
Web3mine | f03019928 Nebula Block | f03019861 TopBlocks | f03019931 QC Data Center | f03014608 FBG Capital | f03019934 ZhongYiGuoLian | f03019935 XnMatrix | f03019938 SUPERB GRACE LIMITED | f03018026 New Web Group | f03015081 Lighthouse.Storage | f03019939 IPFSCN | f03019942 ANTPOOL | f03019944 ZetaCube Inc | f03018530 Power Meta Corp | f03019948 Titan Network | f03018977 Flamenco team | f03019950
//edit Updated per input from Organization for activity Twinquasar - CIDgravity | f03019296 Twinquasar - CIDgravity | f03019298
Hi! We're currently developing our Pathways We have a whole stack to develop. We released our new product offers that include Datacap and automatic datacap allocation : last week : https://www.cidgravity.com/pricing
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!
https://github.com/luhong123/QC-Data-center/issues/1 We are working on a series of tests, including spark retrieval access, so please give us some time!
Hello, I'm sorry for the late reply. I started DC allocation, and I will do allocation according to the trench schedule. https://github.com/ipfsAllen/Fil-DC-Allocator-Allen/issues And I am going to participate in the Allocator Call.
Hello , This is Harry from TopBlocks, Sorry for missing so important key info We are working on it and will update recently Also will take part in the next allocator call
But May i ask you for help
My ledger address comes from LedgerLive, but it seems that it different from allocator website Ledger nano s Want to change address from "f13scefkwue5cpivykug4qod4tkcmuqf4bgu7yzsy" to f1ez4nfx4lbqmddefk3gpqisf2xcfr3g6qm4qes7i Also update 1069
Transfer Topblocks repo from filplus-bookkeeping to TopBlocks It could be convenient for us to handle new tools in the future
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 Code Repository: GitHub - Titan Storage SDK
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.
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 Thanks for posting and confirming the organization wishes to proceed as an Allocator. To make sure we have a action plan, can you please provide
Warmly, -Kevin
Hello, here is ipfscn. Thank you for the reminder. We have already started the allocation.
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, https://github.com/filecoin-project/Allocator-Registry/issues/79 . Once this issue is resolved, we should be able to proceed with our allocation work quickly.
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 Which organization is this for? Shenzhen SpaceTime Cloud Technology Co.; Ltd., STCloud?
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 Which organization is this for? Shenzhen SpaceTime Cloud Technology Co.; Ltd., STCloud?
The application we originally applied for was here. https://github.com/filecoin-project/notary-governance/issues/1038. Our organization's name is this Shenzhen SpaceTime Cloud Technology Co., Ltd. The name of this organization may also need to be revised
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 Which organization is this for? Shenzhen SpaceTime Cloud Technology Co.; Ltd., STCloud?
The application we originally applied for was here. filecoin-project/notary-governance#1038. Our organization's name is this Shenzhen SpaceTime Cloud Technology Co., Ltd. The name of this organization may also need to be revised
Carrying forward a DM into this thread (for transparency) Organization reached out, due to a bookkeeping issue will not be sunset for DataCap - but will be taking action to start distributions within the next 30 days
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 Nebula Block | f03019861 FBG Capital | f03019934 ZhongYiGuoLian | f03019935 XnMatrix | f03019938 SUPERB GRACE LIMITED | f03018026 Power Meta Corp | f03019948 Flamenco team | f03019950
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.