filecoin-plus-large-datasets
filecoin-plus-large-datasets copied to clipboard
[DataCap Application] JMA Himawari-8/9 Open Data
Data Owner Name
NOAA
What is your role related to the dataset
Data Preparer
Data Owner Country/Region
Japan
Data Owner Industry
Environment
Website
https://www.noaa.gov/
Social Media
https://www.facebook.com/NOAA
https://www.youtube.com/usnoaagov
Total amount of DataCap being requested
15PiB
Expected size of single dataset (one copy)
1.5P
Number of replicas to store
10
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1itqagmoxyc35kozkvle6mtsaqchxgpjojkn6szi
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.
- github: https://github.com/orgs/froghub-io
- twitter: https://twitter.com/froghub_io
Is this project associated with other projects/ecosystem stakeholders?
No
If answered yes, what are the other projects/ecosystem stakeholders
No response
Describe the data being stored onto Filecoin
Himawari-8, stationed at 140E, owned and operated by the Japan Meteorological Agency (JMA), is a geostationary meteorological satellite, with Himawari-9 as on-orbit back-up, that provides constant and uniform coverage of east Asia, and the west and central Pacific regions from around 35,800 km above the equator with an orbit corresponding to the period of the earth’s rotation.
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)
China
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 SP.
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
https://registry.opendata.aws/noaa-himawari/
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
Shipping hard drives
How do you plan to choose storage providers
Slack, 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 |
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.
- Have you prepared enough token for sector pledge?
- Has this dataset been stored on Filecoin before? If so, why are you choosing to store it again?
- Per the https://github.com/filecoin-project/notary-governance/issues/922 for Open, Public Dataset applicants, please complete the following Fil+ registration form to identify yourself as the applicant and also please add the contact information of the SP entities you are working with to store copies of the data.
- Have you prepared enough token for sector pledge?
- Has this dataset been stored on Filecoin before? If so, why are you choosing to store it again?
- Per the Modification: Changes required to public open dataset application flow notary-governance#922 for Open, Public Dataset applicants, please complete the following Fil+ registration form to identify yourself as the applicant and also please add the contact information of the SP entities you are working with to store copies of the data.
Hello @Sunnyiscoming ,
- Yes, SPs have prepared enough FIL for sector pledge.
- I have not found that this data is completely stored on Filecoin.
- I have submitted the form.
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.
-- Commented by Stale Bot.
Hi @Sunnyiscoming . Any update ?
Datacap Request Trigger
Total DataCap requested
15 PiB
Expected weekly DataCap usage rate
1 PiB
Client address
f1itqagmoxyc35kozkvle6mtsaqchxgpjojkn6szi
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.
-- Commented by Stale Bot.
@Sunnyiscoming
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.
-- Commented by Stale Bot.
waiting
Hi @Sunnyiscoming ,Can you fix this bug for me? I've been waiting for this for a long time...
SP List provided: [{"providerID": "f0870354", "City": "beijing", "Country": "CN", "SPOrg","XYZ"}, {"providerID": "f01989372", "City": "beijing", "Country": "CN", "SPOrg","XYZ"}, {"providerID": "f02816837 ", "City": "guangdong", "Country": "CN", "SPOrg","B.B Tech"}, {"providerID": "f01907578 ", "City": "Putian ", "Country": "CN", "SPOrg","ssdminer"}, {"providerID": "f0123931 ", "City": "Fuzhou ", "Country": "CN", "SPOrg","ssdminer"}, {"providerID": "f02806894", "City": "Seoul ", "Country": "Korea ", "SPOrg","Chimsen "}, {"providerID": "f02372022 ", "City": "Tokyo ", "Country": "Japan ", "SPOrg","Chimsen "}, {"providerID": "f02810687 ", "City": "HK ", "Country": "CN", "SPOrg","DR66 Tech"}, {"providerID": "f02636860 ", "City": "HK ", "Country": "CN", "SPOrg","DR66 Tech"}, {"providerID": "f01854510 ", "City": "HK ", "Country": "CN", "SPOrg","3cloud tech"}, {"providerID": "f02803754 ", "City": "Osaka ", "Country": "Japan ","SPOrg","XYZ},]
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2243#issuecomment-1834184439 Sorry. I can not fix this bug. Please wait for a moment.
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.
-- Commented by Stale Bot.
waiting...
This application is ready to sign since one month ago, please use this one and close #2292
Client address f1itqagmoxyc35kozkvle6mtsaqchxgpjojkn6szi is present in other Fil+ applications (#2292). This may cause unexpected behavior.
Still unable to sign, can you help me with that?
@clriesco @Sunnyiscoming
DataCap Allocation requested
Multisig Notary address
f02049625
Client address
f1itqagmoxyc35kozkvle6mtsaqchxgpjojkn6szi
DataCap allocation requested
512TiB
Id
4a469e58-2a69-4083-a185-71cf8f54cfcc
Now it's visible in the app
Thank you so much
Support the first round.
Request Proposed
Your Datacap Allocation Request has been proposed by the Notary
Message sent to Filecoin Network
bafy2bzacec4eokmur4vlxhnqrvkroip2zlvdm2pxykw6is27yru6wmm5ecrng
Address
f1itqagmoxyc35kozkvle6mtsaqchxgpjojkn6szi
Datacap Allocated
512.00TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
4a469e58-2a69-4083-a185-71cf8f54cfcc
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec4eokmur4vlxhnqrvkroip2zlvdm2pxykw6is27yru6wmm5ecrng
Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network
bafy2bzacedhzke6mpnp2z222xbgzoidpdklv7ddt2om63u2k5tmditght76wu
Address
f1itqagmoxyc35kozkvle6mtsaqchxgpjojkn6szi
Datacap Allocated
512.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
4a469e58-2a69-4083-a185-71cf8f54cfcc
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedhzke6mpnp2z222xbgzoidpdklv7ddt2om63u2k5tmditght76wu
In support for first round
DataCap Allocation requested
Request number 2
Multisig Notary address
f02049625
Client address
f1itqagmoxyc35kozkvle6mtsaqchxgpjojkn6szi
DataCap allocation requested
512TiB
Id
1d9655b4-e184-4f69-8a8f-8b88203c6299
checker:manualTrigger
DataCap and CID Checker Report Summary[^1]
Storage Provider Distribution
✔️ Storage provider distribution looks healthy.
Deal Data Replication
✔️ Data replication looks healthy.
Deal Data Shared with other Clients[^3]
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Full report
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard.
checker:manualTrigger
DataCap and CID Checker Report Summary[^1]
Storage Provider Distribution
✔️ Storage provider distribution looks healthy.
Deal Data Replication
✔️ Data replication looks healthy.
Deal Data Shared with other Clients[^3]
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Full report
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard.