[DataCap Application] - CognoCloud #388
Comments
|
Thanks for your request! |
large-datacap-requests
bot
added
governance review needed
status:Further info needed
and removed
application
labels
|
Thanks for your request! A Governance Team member will review the information provided and contact you back pretty soon. |
large-datacap-requests
bot
added
bot:lookingGood
and removed
governance review needed
status:Further info needed
labels
|
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. |
|
@jessie8o8 - going to need a few things from you for this one:
The default path for encrypted datasets today is what Seal did here: filecoin-project/notary-governance#489, however that was with a higher burden of proof that required NDAs to discuss the client and the dataset. If you can garner enough support from at least 5 notaries, we can either proceed the same way or find a better path here. |
|
I will support this one, and yes it’s PikNik |
|
Hi @dkkapur, Correct, I work for PiKNiK! We understand the reasonable doubt you may have and are please to present the following proposal with the support of 5 notaries. The following is the proposal for Cognocloud's dataset. Please let me know if you have any further questions! Cognocloud LDN ProposalProject Description Client we are representing : CognoCloud ESPA Participant that sourced the client: Moose Mining LLC Transparency in KYC We are completing a KYC process with CognoCloud with the help of trusted community notaries. Additionally, an email thread has been forward to [email protected] to validate our relationship with senior leadership at CognoCloud. Data Set Why is it useful to the Filecoin network? Another reason why CognoCloud is useful to the Filecoin network is because they are one of the first private clients willing to work with the ESPA community’s newly trained storage provider participants (Moose Mining, Lucky Strike, etc.), which increases the diversity of SPs willing to support real enterprise and FIL+ data beyond the usual few entities who have recently been dominating LDN requests. Notaries that Support the Project [person / org / region / Github app] Kobby Chen / Fenbushi / Greater China / filecoin-project/notary-governance#418 |
|
I will support it as well |
|
Hi @Sunnyiscoming, the form is complete and submitted. |
|
This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open. -- |
|
Comment to keep LDN open. |
|
checker:manualTrigger |
DataCap and CID Checker Report Summary1Storage Provider DistributionDeal Data ReplicationDeal Data Shared with other Clients2✔️ No CID sharing has been observed. Full reportClick here to view the CID Checker report. Footnotes |
|
@jamerduhgamer can you explain the reason why this LDN is not stored according to the rules of FIL+ ? |
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Please provide ID, City, Country, Organization of each SP here. |
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open. -- |
|
Keep open |
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
We will be working to resolve the above issues with the dataset soon when we start sealing progress on the dataset again. |
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
|
Client f01857951 does not follow the datacap usage rules. More info here.
|
and others
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.
Cloud services company offering iaas and dramas for our customers. We wish to have an archived backup copy of the data
What is the primary source of funding for this project?
N/A
What other projects/ecosystem stakeholders is this project associated with?
Moose Mining and other reputable North American SPs
Use-case details
Describe the data being stored onto Filecoin
VMDKs, VHDs, files, etc of our customers
Where was the data in this dataset sourced from?
Our servers and storage in Toronto
Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this.
cannot be shared
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).
Data will be encrypted
What is the expected retrieval frequency for this data?
Very rare
For how long do you plan to keep this dataset stored on Filecoin?
As long as possible for longer term archiving
DataCap allocation plan
In which geographies (countries, regions) do you plan on making storage deals?
United States and Canada
How will you be distributing your data to storage providers? Is there an offline data transfer process?
Online over the internet
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.
Moose Mining and other reputable North American SPs
How will you be distributing deals across storage providers?
There is going to be an offline data transfer process where files are hosted online and other storage providers can download them.
Do you have the resources/funding to start making deals as soon as you receive DataCap?
Yes
What support from the community would help you onboard onto Filecoin?
ESPA Community
The text was updated successfully, but these errors were encountered: