-
Notifications
You must be signed in to change notification settings - Fork 62
[DataCap Application] Slingshot Evergreen ( Protocol Labs ) #293
Comments
Thanks for your request! A Governance Team member will review the information provided and contact you back pretty soon. |
Thanks for your request! A Governance Team member will review the information provided and contact you back pretty soon. |
Thanks for your request! A Governance Team member will review the information provided and contact you back pretty soon. |
Thanks for your request! A Governance Team member will review the information provided and contact you back pretty soon. |
Multisig Notary requestedTotal DataCap requested
Expected weekly DataCap usage rate
|
**Multisig created and sent to RKH f01782465 |
DataCap Allocation requestedMultisig Notary address
Client address
DataCap allocation requested
|
Stats & Info for DataCap AllocationMultisig Notary address
Client address
Last two approvers
Rule to calculate the allocation request amount
DataCap allocation requested
Total DataCap granted for client so far
Datacap to be granted to reach the total amount requested by the client (5 PiB)
Stats
|
DataCap and CID Checker Report1
Approvers
Storage Provider DistributionThe below table shows the distribution of storage providers that have stored data for this client. If this is the first time a provider takes verified deal, it will be marked as For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Deal Data ReplicationThe below table shows how each many unique data are replicated across storage providers.
Deal Data Shared with other ClientsThe below table shows how many unique data are shared with other clients. However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset. Footnotes
|
This application needs porting over to LDN v3 rather than having a dedicated multisig from the v2 implementation of the LDN process. Last set of approvals have Error:17 (no DataCap balance) since the notary assigned to this is out. Based on this, pushing a manual allocation for #6 for this address, but we need to swap this over. cc @simonkim0515 @galen-mcandrew can we get this systematically swapped over from deprecated notary to updated LDN v3 address? |
DataCap Allocation requestedRequest number 6Multisig Notary address
Client address
DataCap allocation requested
|
manually patching last comment from bot as well, just in case. |
@s0nik42 @cryptowhizzard can you try resigning this one through notary tool now and let me know if it's working / the proposal is indeed for the intended 2000 TiB from the LDN v3 multisig? |
wip |
Request ProposedYour Datacap Allocation Request has been proposed by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
IdYou can check the status of the message here: https://filfox.info/en/message/bafy2bzacecdgtff4jkstmupgakfd7zkobumk6zs7tsj2hgwifgj6s2dbq6fbq |
Request ApprovedYour Datacap Allocation Request has been approved by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
IdYou can check the status of the message here: https://filfox.info/en/message/bafy2bzacedke2ujatzz7dlcfs75rohnrejflvpiygh4ipeoa7ew6wq2qvnhoi |
Stats & Info for DataCap AllocationMultisig Notary address
Client address
Last two approvers
Rule to calculate the allocation request amount
DataCap allocation requested
Total DataCap granted for client so far
Datacap to be granted to reach the total amount requested by the client (5 PiB)
Stats
|
hmmmm. ok still going to the old notary ID. cc @fabriziogianni7 might be a bug, but feels like quite an edge case. going to pivot into making a new application for this one instead to reduce complexity. Will stick with remaining PiBs but inflate the weekly rate for it to keep up. |
Closing this one out in favor of #1576 |
Large Dataset Notary Application
To apply for DataCap to onboard your dataset to Filecoin, please fill out the following.
Core Information
Please respond to the questions below by replacing the text saying "Please answer here". Include as much detail as you can in your answer.
Project details
Share a brief history of your project and organization.
What is the primary source of funding for this project?
What other projects/ecosystem stakeholders is this project associated with?
Use-case details
Describe the data being stored onto Filecoin
Where was the data in this dataset sourced from?
Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this.
Confirm that this is a public dataset that can be retrieved by anyone on the Network (i.e., no specific permissions or access rights are required to view the data).
What is the expected retrieval frequency for this data?
For how long do you plan to keep this dataset stored on Filecoin?
DataCap allocation plan
In which geographies (countries, regions) do you plan on making storage deals?
How will you be distributing your data to storage providers? Is there an offline data transfer process?
How do you plan on choosing the storage providers with whom you will be making deals? This should include a plan to ensure the data is retrievable in the future both by you and others.
How will you be distributing deals across storage providers?
Do you have the resources/funding to start making deals as soon as you receive DataCap? What support from the community would help you onboard onto Filecoin?
The text was updated successfully, but these errors were encountered: