-
Notifications
You must be signed in to change notification settings - Fork 73
Client Allocation Request for: Textile.io #417
Comments
Thanks for your request!
|
Hi @XnMatrixSV, this is tagged to the wrong assignee currently but is intended for you. I wanted to share some project background here to get the application started.
New project: We are building a high-throughput deal-making system that will allow miners to connect to and receive deals easily. We aim to deploy the system at a much larger scale but are in a testing phase. We are performing tests using non-Mainnet miner setups now but are getting ready for Mainnet testing next. For our tests, we'll be connecting with 3-5 miners over the next month to ensure the full deal creation and storage workflow works properly on mainnet (including payments etc). For that, we'll be storing a mix of useful public data and some arbitrary data for testing purposes alone. I've had a few conversations to date to assess if this kind of testing should be eligible for datacap, and it seems that so far, the consensus is that it should, but let me know what you think. In the spirit of experimentation, though, I'm keeping the datacap request reasonably small. |
Hi,@andrewxhill |
If you experience problems in practice, you can write to me, and I'm always ready to help you. |
If I understand your proposal it doesn't work that well in practice for a client. I think our setup will be common in larger FIL integrations. Let me explain our situtation.
The Datacap we applied for originally was for a project that involved our system backup and recovery systems. So it had a specific address that it uses to manage deals on Filecoin from that area of work. We plan to continue the backup and recovery project using that address and will continue to use that Datacap. This new project, is using a new node that is run as part of a different stack unrelated to our SAAS systems. We cannot transfer the address in use to this new node. So, reassigning the existing datacap from one node to another isn't an option. This is a totally new project, so it made sense to me to apply for a totally different datacap. Happy to open the old ticket, but the old address isn't helpful. Let me know if you have any questions. |
1.Could you give a description of the cooperation mechanisms with miners you chose before, such as how do you find them, the reason why you choose them, and datacap allocation proportion, etc. |
We focused on a list of small miners that were part of the first minerx fellowship.
Sure, for continuity of the other proposal, I've added it as a comment here #234 (comment). The summary is that we used 13 miners. They each received a portion of the deals between 4.5% and 13.6% of all the deals we created.
Not really. As mentioned in the first grant application:
|
One more question:
As we know, the same Filecoin address can be used for different nodes. We can't understand this statement. Could you give more explanation about that? |
This just reflects the architecture of our systems. We generally create new addresses for different jobs or different infrastructure, we don't mix them or transfer them. |
Considering the demand of the new project, we will still agree with your application this time |
Thank you! Confirmed, |
Request ApprovedYour Datacap Allocation Request has been approved by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebnpc2n757dsehndpjbrtybc7t4bh5k4kfzevnhta4bcp3kxcvgpk |
Client Allocation Questions
Core Information
@andrewxhill Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.
The text was updated successfully, but these errors were encountered: