Closed jyma closed 7 months ago
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
This information will be reviewed by Fil+ Governance team to confirm validity and then the application will be triggered for notary review. Let us know if you have any questions.
@Sunnyiscoming
Have you prepared enough token for sector pledge?
Yes,My partners and I have diligently secured the requisite pledge tokens.Moreover, most of the Miner IDs I've listed have recently been undergoing large-scale DC sealing, which you can verify in the link below. f02228866;f01315130;f02240216
Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 4 or more storage provider operators or owners.You should list Miner ID, Business Entity, Location of sps you will cooperate with.
Got it,I will strictly adhere to the LDN guidelines. As of now, I can list the following SPs. I will continue to search for more SPs to seal in the future.
f02228866 - Feige IT, Tokyo, JP
f01761579 - Feige IT, Hangzhou, CN
f01315130 - Ouruan IT, Chengdu, CN
f02240216 - Lianxing storage, Tokyo, JP
f0673990 - Dayan IT, Hangzhou, CN
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.
I had complete the Fil+ registration form, Thanks for your reminder.
@jyma Welcome to FIL+!
I'd like to ask you why you selected the datasets:
Love to understand. Most of these sets are already stored multiple times so I am wondering why these add additional value from your request.
Thank you!
@herrehesse Hi~
Thank you for your inquiry regarding the selection of specific datasets, including ENCODE, 4DN, NCBI SRA, and UCSC Genome Browser. I understand your concern about the availability of these datasets elsewhere. Allow me to provide a concise overview of the rationale behind their inclusion:
Furthermore, I would like to confirm that the selected datasets do not overlap with the DC had sealed in our nodes. This ensures that we are adding unique value to our existing data resources.
Feel free to reach out if you need further clarification.
Best regards.
@jyma Appreciate your response. While you've shed light on the nature of the sets, you haven't clarified why there's a need to store these sets which seem to already exist multiple times on this network:
Additionally, as per the discussions and consensus reached here: https://github.com/filecoin-project/notary-governance/issues/832, merged datacap requests are not permissible.
I can't endorse an applicant aiming to store sets that have been stored repeatedly, especially when done through a merged request.
I'd suggest exploring other public datasets for this network.
Thank you.
@herrehesse I understand your concerns about the redundant storage of the "ENCODE" dataset, as I expressed in my previous response. It's possible that some of the data I've requested might already be on the Filecoin network, but the dataset I'm requesting hasn't been stored on our nodes.
Additionally, in the screenshot you shared, only a minor portion of the data I've requested has been stored on the Filecoin network.
Regarding the filecoin-project/notary-governance#832 you mentioned, is it the guidelines for LDN application? If it is, I will adhere to it. If not, I believe we shouldn't be discussing it here.
Thank you.
Confirming SP Entities submitted: f02228866 - Feige IT, Tokyo, JP f01761579 - Feige IT, Hangzhou, CN f01315130 - Ouruan IT, Chengdu, CN f02240216 - Lianxing storage, Tokyo, JP f0673990 - Dayan IT, Hangzhou, CN
@Filplus-govteam Yes,I hereby confirm the SP entities provided.
Thank you.
Total DataCap requested
12PiB
Expected weekly DataCap usage rate
1PiB
Client address
f1de4p54dgtlms5ldkjmitf5caafhov4i6vxtfmca
f02049625
f1de4p54dgtlms5ldkjmitf5caafhov4i6vxtfmca
512TiB
548ff25f-f018-4a5d-bf34-58ca435c4ae7
f0673990
f02228866 is located in US virginia f01761579 is located in CN , Zhejiang, Jiaxing f01315130 is located in CN , Sichuan, Meishan f02240216 is located in US virginia f0673990 is located in CN , Zhejiang , Ningbo , not online ( not reachable )
@cryptowhizzard
f0673990 now is the market , and we will switch to boost before sealing.
Thank you.
How about that the location mismatches what you were saying?
Miner is not open for connection btw.
@cryptowhizzard
f0673990 underwent an IP address change about half a year ago. It appears that the on-chain IP address is still the previous old address. On the Filfox browser, we can also see that we have already changed the IP address.
For f02240216、f02228866 the IP results I queried on the server are in Tokyo. I'm not sure where the issue lies, perhaps it's due to differences in the IP lookup websites we are using.
As for the other nodes, the locations you queried are very close to the ones I provided on the map. The administrative division of the node's location that I provided is accurate. The slight differences might be due to the IP lookup website you're using not being precise enough for Chinese IP addresses in terms of administrative regions.
Taking the public IP 115.227.36.111 of f01761579 as an example, I can obtain the accurate administrative region Zhejiang,Hangzhou using a domestic Chinese IP lookup website, while your result shows Zhejiang, Jiaxing.
Such discrepancies between the information provided by IP lookup websites and the actual administrative divisions are likely quite common.If this poses a problem, we can suggest using a unified IP lookup website, so there won't be any discrepancies.
Thank you.
checker:manualTrigger
No application info found for this issue on https://filplus.d.interplanetary.one/clients.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
@jyma
Thanks for the clarification. Please note my remark that the miner is not open for connection / retrieval.
@cryptowhizzard
Thank you for the reminder. We fixed the issue earlier, but due to my oversight, I didn't post a screenshot.
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.
Open
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebt7gpwjnbiuqu7t7hrenmtnaexcadxernu3utfxpzcj5heqxudh6
Address
f1de4p54dgtlms5ldkjmitf5caafhov4i6vxtfmca
Datacap Allocated
512.00TiB
Signer Address
f12mckci3omexgzoeosjvstcfxfe4vqw7owdia3da
Id
548ff25f-f018-4a5d-bf34-58ca435c4ae7
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebt7gpwjnbiuqu7t7hrenmtnaexcadxernu3utfxpzcj5heqxudh6
checker:manualTrigger
No application info found for this issue on https://filplus.d.interplanetary.one/clients.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedpvdg2izjb27rf6jtgalozqnexucjncbsiwi44vudwv5lw7p6qtg
Address
f1de4p54dgtlms5ldkjmitf5caafhov4i6vxtfmca
Datacap Allocated
512.00TiB
Signer Address
f1tbd632f6w62glfaf7wjpimacbnjiz26poyoes2q
Id
548ff25f-f018-4a5d-bf34-58ca435c4ae7
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedpvdg2izjb27rf6jtgalozqnexucjncbsiwi44vudwv5lw7p6qtg
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.
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!
-- Commented by Stale Bot.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
SPs taking Deals: f02823036new | Tsuen Wan, Tsuen Wan, HKACT International Telecom Limited | 49.50 TiB | 9.93% | 49.50 TiB | 0.00% f01315130 | Chengdu, Sichuan, CNCHINA UNICOM China169 Backbone | 149.59 TiB | 30.02% | 149.59 TiB | 0.00% f02240216 | Tokyo, Tokyo, JPPCCW Global, Inc. | 149.59 TiB | 30.02% | 149.59 TiB | 0.00% f02228866 | Tokyo, Tokyo, JPPCCW Global, Inc. | 149.56 TiB | 30.02% | 149.50 TiB | 0.04%
SPs listed in application: f02228866 - Feige IT, Tokyo, JP f01761579 - Feige IT, Hangzhou, CN f01315130 - Ouruan IT, Chengdu, CN f02240216 - Lianxing storage, Tokyo, JP f0673990 - Dayan IT, Hangzhou, CN
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
@jyma could you explain the new SP f02823036 not on the list?
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
@kernelogic Ours application process has been taking too long, and some of our partners have made changes to their sealing plans. f02823036 is the new node we've added. The information for f02823036 is as follows: f02823036- GX , Tsuen Wan, HK
The explanation looks fair. Do you have any plans to increase the retrieval rate of http?
@spaceT9 We are working on sealing as quickly as possible, and we may using HTTP retrieval during the next Lotus upgrade. Thank you.
Sounds good, willing to support.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedw6v3mn6ldwzlblvtl4vrctvgmek7nabhhrjutdmy46ghrvavq2y
Address
f1de4p54dgtlms5ldkjmitf5caafhov4i6vxtfmca
Datacap Allocated
512.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
548ff25f-f018-4a5d-bf34-58ca435c4ae7
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedw6v3mn6ldwzlblvtl4vrctvgmek7nabhhrjutdmy46ghrvavq2y
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
Scrolled through the history and checked out the bot report, looks good, willing to support this round
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedhgkkm7wtglfyya4bzsaiuquibojiv2twolsbtdos6pvwcqllty6
Address
f1de4p54dgtlms5ldkjmitf5caafhov4i6vxtfmca
Datacap Allocated
512.00TiB
Signer Address
f1cjzbiy5xd4ehera4wmbz63pd5ku4oo7g52cldga
Id
548ff25f-f018-4a5d-bf34-58ca435c4ae7
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedhgkkm7wtglfyya4bzsaiuquibojiv2twolsbtdos6pvwcqllty6
Add new Sps: | ids | sps | region |
---|---|---|---|
f02301 | topblocks | Santa Clara(US) | |
f03223 | topblocks | Santa Clara(US) | |
f0240185 | topblocks | Santa Clara(US) | |
f0143858 | topblocks | Santa Clara(US) | |
f02818480 | SJX | Kentucky(USA) | |
f02817832 | SJX | Kentucky(USA) | |
f02823036 | GX | Tsuen Wan, HK |
f02049625
f1de4p54dgtlms5ldkjmitf5caafhov4i6vxtfmca
1PiB
2f2027d7-7974-40a9-9933-b56325f8d705
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard.
Data Owner Name
CryptoCraft-Public Dataset
What is your role related to the dataset
Storage provider filling out application on behalf of the data owner
Data Owner Country/Region
United States
Data Owner Industry
Life Science / Healthcare
Website
https://www.encodeproject.org;https://data.4dnucleome.org;https://www.ncbi.nlm.nih.gov;https://hgdownload.soe.ucsc.edu/downloads.html
Social Media
Total amount of DataCap being requested
12PiB
Expected size of single dataset (one copy)
2.5Pb
Number of replicas to store
5
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1de4p54dgtlms5ldkjmitf5caafhov4i6vxtfmca
Data Type of Application
Public, Open Dataset (Research/Non-Profit)
Custom multisig
Identifier
No response
Share a brief history of your project and organization
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
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 (City and Country)
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
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.
Please share a sample of the data
Confirm that this is a public dataset that can be retrieved by anyone on the Network
If you chose not to confirm, what was the reason
No response
What is the expected retrieval frequency for this data
Sporadic
For how long do you plan to keep this dataset stored on Filecoin
Permanently
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
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
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