-
Notifications
You must be signed in to change notification settings - Fork 62
[DataCap Application] Speedium - NexRad V2 [ Replica distribution ] Part 1 / 5 #483
Comments
Thanks for your request! A Governance Team member will review the information provided and contact you back pretty soon. |
@cryptowhizzard Hi,
|
Fair points. 1 -> https://registry.opendata.aws/noaa-nexrad/ 2 -> I am not sure if it is 2 PB exactly , this dataset is growing over the course of months. It can be that i won't apply for the last tranche. 3 -> This is rather difficult. I can't start sealing #340 solely with one miner by our own as this would violate the program rules. This is the reason i am doing this applications in parallel. |
I don't quite understand your third point. Why can't datacap of #340 be allocated to other storage providers? |
@Sunnyiscoming this can be done. But if i assign and they don't start in the same pace or rythm it will result in 1 provider taking the whole first allocation. |
I will talk about this with governance team because I think it is a problem which can be solved. |
Hi @cryptowhizzard , can you elaborate on the difficulties? I'm unsure why you would only be able to seal with one SP? |
@raghavrmadya because the dataset is the same size as the datacap. Only one can seal the first replica to get it on chain. This is no problem as i will do the replica’s in a separate LDN, i just want to give notification here. |
If this problem can be solved. Maybe you can close this issue and continue #340 |
Hi @cryptowhizzard, we have a PR open that was presented at the last gov call to increase the request limit to 25 PiBs. Do you mind waiting until end of this week when we merge that or are there SPs waiting on you? |
Hi @raghavrmadya that is ok. I will also update the wallet address so it is a unique wallet address per datacap request. |
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. |
Datacap Request TriggerTotal DataCap requested
Expected weekly DataCap usage rate
Client address
|
DataCap Allocation requestedMultisig Notary address
Client address
DataCap allocation requested
Id
|
@cryptowhizzard The distribution looks healthy, but can you please explain the CID sharing with other entity #335 ? |
@xingjitansuo Yes i can. #335 and we did build exactly the same dataset from AWS S3. This means the same CID's will be created. |
The same CID only happens when the Data preparer uses the same way on the same raw data to prepare the car file. |
@xingjitansuo yes , we did. We build it with Singularity, so did Xinan. |
Request ProposedYour Datacap Allocation Request has been proposed by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceapnxsq4z54ed4fxvihz4bjuy2dhycfz4sdkqtolw4exp5x3hcyeu |
checker:manualTrigger f1ws3n5tuxtyg26lraqkjirz7qon7y7ckju7hhmii f1pc5usvsbfgxxbq7c7quhhg6k7l6y5reiwqr3noy |
DataCap and CID Checker Report1
Approvers
Other Addresses2Storage 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.
Deal Data ReplicationThe below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
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.3
Footnotes
|
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. |
This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you! |
This user’s identity has been verified through filplus.storage |
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
Short addendum on this project
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: