filecoin-plus-large-datasets
filecoin-plus-large-datasets copied to clipboard
filecoin-project
[DataCap Application] Public Datasets -- Digital Earth Africa
Data Owner Name
Digital Earth Africa
What is your role related to the dataset
Data Preparer
Data Owner Country/Region
South Africa
Data Owner Industry
Environment
Website
https://www.digitalearthafrica.org/
Social Media
Twitter: https://twitter.com/DEarthAfrica
Youtube: https://www.youtube.com/channel/UCBasD3Dz-TdQTRoyG30kVVw
Total amount of DataCap being requested
8PiB
Expected size of single dataset (one copy)
700
Number of replicas to store
10
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
Data Type of Application
Public, Open Dataset (Research/Non-Profit)
Custom multisig
- [ ] Use Custom Multisig
Identifier
No response
Share a brief history of your project and organization
FrogHub has always defined itself as a tool developer and infrastructure builder in the Filecoin ecosystem. In 2019, we started to focus on technical solutions and development based on the IPFS protocol and Filecoin network. We have been working hard to become a qualified builder in the filecoin ecosystem.
Our team is a very pure development team, more than 90% of which are developers, more than half of whom have more than 5 years of development experience in communication, Internet, blockchain and other industries. We hope that we can gain users' recognition by exporting useful tools and platforms.
In order to contribute to the filecoin community, we have developed the open source sector repair tool Filecoin-Sealer-Recover and the nft free authoring platform NFT-Creator.
In addition, we plan to provide a sector browser for the community in 2023 and build the liquidity pledge platform STFIL on FVM.
See the links below for details.
- making: https://github.com/orgs/froghub-io
Is this project associated with other projects/ecosystem stakeholders?
Yes
If answered yes, what are the other projects/ecosystem stakeholders
No response
Describe the data being stored onto Filecoin
Landsat scenes and metadata. DE Africa provides data from Landsat 5, 7 and 8 satellites, including historical observations dating back to late 1980s and regularly updated new acquisitions.
Where was the data currently stored in this dataset sourced from
AWS Cloud
If you answered "Other" in the previous question, enter the details here
No response
If you are a data preparer. What is your location (Country/Region)
Hong Kong
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
After we download data from the Internet, the data is cut into disks through Singularity, and then the hard disk is mailed to the SPs.
If you are not preparing the data, who will prepare the data? (Provide name and business)
No response
Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution.
No response
Please share a sample of the data
s3://deafrica-landsat/
s3://deafrica-landsat-inventory/
Confirm that this is a public dataset that can be retrieved by anyone on the Network
- [X] I confirm
If you chose not to confirm, what was the reason
No response
What is the expected retrieval frequency for this data
Yearly
For how long do you plan to keep this dataset stored on Filecoin
1.5 to 2 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China, North America
How will you be distributing your data to storage providers
Cloud storage (i.e. S3), HTTP or FTP server, Shipping hard drives
How do you plan to choose storage providers
Big Data Exchange, Partners
If you answered "Others" in the previous question, what is the tool or platform you plan to use
No response
If you already have a list of storage providers to work with, fill out their names and provider IDs below
| MinerID | Entity | City | Continent |
| --------- | ---------- | ---------- | --------- |
| f0870354 | Personal | beijing | CN |
| f01989372 | Personal| beijing | CN |
| f02816837 | B.B Tech| guangdong | CN |
| f01907578 | ssdminer| Putian | CN |
| f0123931 | ssdminer| Fuzhou | CN |
| f02806894 | Chimsen | Seoul | Korea |
| f02372022 | Chimsen | Tokyo | Japan |
| f02810687 | DR66 Tech| HongKong | CN |
| f02636860 | DR66 Tech| HongKong | CN |
| f01854510 | 3cloud tech| HongKong | CN |
| f02803754 | Personal | Osaka | Japan |
These are some of the SPs we are currently cooperating with, and more SPs may join in the future. I have already done KYC in other applications. I can do it again if necessary.
How do you plan to make deals to your storage providers
Boost client
If you answered "Others/custom tool" in the previous question, enter the details here
No response
Can you confirm that you will follow the Fil+ guideline
Yes
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
![large-datacap-requests[bot] avatar](https://avatars.githubusercontent.com/in/116297?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @FroghubMan - Can we expect storage in EU/USA as well (No VPN). As far as I can see all data storage remains on one continent.
Hi @herrehesse ,OK, I will look for some new partners in different continents soon
Datacap Request Trigger
Total DataCap requested
8PiB
Expected weekly DataCap usage rate
1PiB
Client address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
DataCap Allocation requested
Multisig Notary address
f02049625
Client address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
DataCap allocation requested
409.59TiB
Id
99f2c163-119b-4647-993b-a79a63cdb216
| f0870354 | Personal | beijing | CN | | f01989372 | Personal| beijing | CN | | f02816837 | B.B Tech| guangdong | CN | | f01907578 | ssdminer| Putian | CN | | f0123931 | ssdminer| Fuzhou | CN | | f02806894 | Chimsen | Seoul | Korea | | f02372022 | Chimsen | Tokyo | Japan | | f02810687 | DR66 Tech| HongKong | CN | | f02636860 | DR66 Tech| HongKong | CN | | f01854510 | 3cloud tech| HongKong | CN | | f02803754 | Personal | Osaka | Japan | | f02806522 | HCXYTech |Ashburn,Virginia | f02806528 | HCXYTech |Ashburn,Virginia | f01708981 | HCXYTech |Jiangmen,Guangdong
Request Proposed
Your Datacap Allocation Request has been proposed by the Notary
Message sent to Filecoin Network
bafy2bzacecziwgalpgfcpjuocnjfvav25y3dyfl7jnwb5r5por6d3x734bozq
Address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
Datacap Allocated
409.59TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
99f2c163-119b-4647-993b-a79a63cdb216
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecziwgalpgfcpjuocnjfvav25y3dyfl7jnwb5r5por6d3x734bozq
Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network
bafy2bzaced4xqo7mi4ldohmv3wkrf4tlq5re7vbym522l4qvpf33os4w7x5s6
Address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
Datacap Allocated
409.59TiB
Signer Address
f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea
Id
99f2c163-119b-4647-993b-a79a63cdb216
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced4xqo7mi4ldohmv3wkrf4tlq5re7vbym522l4qvpf33os4w7x5s6
Dear all. We discovered a serious mistake. We are data preparers. Due to our work error, we used the wrong data source. (Use "Open Atmospheric Research Datasets" - #2119 as "Digital Earth Africa Datasets" - #2289.) Therefore #2289 is currently using the wrong data and has a CID sharing problem with #2119. Sorry for this! Now we need to pause the distribution of this application and take a period of time to delete the erroneous data and re-prepare the right data to correct our errors.
DataCap Allocation requested
Request number 2
Multisig Notary address
f02049625
Client address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
DataCap allocation requested
512TiB
Id
e96af19d-8b32-4813-9bf6-9315e0344d25
Hi @Sunnyiscoming ,I think I should let you know about this situation. This is the first time we have encountered this problem🥲. Do you think I should close this LDN and start a new application, or continue this process after we correct the error?
Client f02884258 does not follow the datacap usage rules. More info here. This application has been failing the requirements for 7 days. Please take appropiate action to fix the following DataCap usage problems.
| Criteria | Treshold | Reason |
|---|---|---|
| Shared data percent | < 20% | 74.47% of the clients data is shared with other clients. This should be less than 20% |
![aggregation-and-compliance-bot[bot] avatar](https://avatars.githubusercontent.com/in/648889?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hello, in my reply two weeks ago I clarified the reason for this error. Sorry again. We have now deleted all incorrectly processed data and processed the correct data. I hope to continue this process, if anyone has any suggestions please let me know.
If possible I will restart the process after 3 working days. Thanks a lot.
Client f02884258 does not follow the datacap usage rules. More info here. This application has been failing the requirements for 14 days. Please take appropiate action to fix the following DataCap usage problems.
| Criteria | Treshold | Reason |
|---|---|---|
| Shared data percent | < 20% | 74.47% of the clients data is shared with other clients. This should be less than 20% |
Client f02884258 does not follow the datacap usage rules. More info here. This application has been failing the requirements for 21 days. Please take appropiate action to fix the following DataCap usage problems.
| Criteria | Treshold | Reason |
|---|---|---|
| Shared data percent | < 20% | 74.47% of the clients data is shared with other clients. This should be less than 20% |
Client f02884258 does not follow the datacap usage rules. More info here. This application has been failing the requirements for 28 days. Please take appropiate action to fix the following DataCap usage problems.
| Criteria | Treshold | Reason |
|---|---|---|
| Shared data percent | < 20% | 74.47% of the clients data is shared with other clients. This should be less than 20% |
Hello, in my reply two weeks ago I clarified the reason for this error. Sorry again. We have now deleted all incorrectly processed data and processed the correct data. I hope to continue this process, if anyone has any suggestions please let me know.
If possible I will restart the process after 3 working days. Thanks a lot.
Hope you can solve the problem soon.
Request Proposed
Your Datacap Allocation Request has been proposed by the Notary
Message sent to Filecoin Network
bafy2bzacedaalo4flfqwomqsqgk7fxxomoohfczmcgsj6wczpeyf73y5hfhum
Address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
Datacap Allocated
512.00TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
e96af19d-8b32-4813-9bf6-9315e0344d25
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedaalo4flfqwomqsqgk7fxxomoohfczmcgsj6wczpeyf73y5hfhum
Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network
bafy2bzaceacdyfj6ojcazwk2drldyw4ucv7tt3olccusckrp6bawlrt7ggefk
Address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
Datacap Allocated
512.00TiB
Signer Address
f1foiomqlmoshpuxm6aie4xysffqezkjnokgwcecq
Id
e96af19d-8b32-4813-9bf6-9315e0344d25
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceacdyfj6ojcazwk2drldyw4ucv7tt3olccusckrp6bawlrt7ggefk
DataCap Allocation requested
Request number 2
Multisig Notary address
f02049625
Client address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
DataCap allocation requested
512TiB
Id
67a9bddf-f881-4712-ba12-1f302f08b34a
we've checked their data and shows healthy, so we are willing to give a support for this round
Request Proposed
Your Datacap Allocation Request has been proposed by the Notary
Message sent to Filecoin Network
bafy2bzaceauflsbds5kaifkstkwyxjidd6gdbpgj5rzasys2hl7dlkzamiuqq
Address
f1zqgvy24nodtsrqms7he2muk2xvni6alnbm3mf7i
Datacap Allocated
512.00TiB
Signer Address
f1nknj7ayq4o43czrtdoauggtwl43fbqatmqis3yy
Id
67a9bddf-f881-4712-ba12-1f302f08b34a
