Closed datalove2 closed 1 year ago
Thanks for your request!
Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
Yesterday this same application was filed under #1577 and #1578 by Github user ledecaevi. Both applications are deleted. @datalove2, can you please explain what the relation is here?
Hi there, The Github handle" ledecaevi" is also one of mine. I resubmitted an application because " ledecaevi" was flagged as "participate in the mining project" by Github Team. I have appealed to the GitHub Team for the specific reason.
lvschouwen @.***> 於 2023年2月2日 星期四寫道:
Yesterday this same application was filed under #1577 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1577 and #1578 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1578 by Github user ledecaevi. Both applications are deleted. @datalove2 https://github.com/datalove2, can you please explain what the relation is here?
[image: image] https://user-images.githubusercontent.com/6965171/216308684-7bcca977-447b-49aa-8848-6626cdf25aaa.png
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1579#issuecomment-1413563848, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5T7HZFWD3FYL5UXFSHDOZ3WVOIRZANCNFSM6AAAAAAUO3OZHU . You are receiving this because you were mentioned.Message ID: <filecoin-project/filecoin-plus-large-datasets/issues/1579/1413563848@ github.com>
Data samples you provided are mentioned in the following applications. How many duplicates are there? https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1123 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1130 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/3 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/46 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/136 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1112 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1488 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1489 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1490 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1491
@Sunnyiscoming Thank you for your reminder. This is a matter worth
discussing. The
Sunnyiscoming @.***> 於 2023年2月5日 星期日寫道:
Data samples you provided are mentioned in the following applications. How many duplicates are there?
1123
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1123
1130
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1130
3
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/3
46
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/46
136
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/136
1112
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1112
1488
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1488
1489
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1489
1490
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1490
1491
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1491
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1579#issuecomment-1416920331, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5T7HZBNZFROM6T47PFSFITWV4UODANCNFSM6AAAAAAUO3OZHU . You are receiving this because you were mentioned.Message ID: <filecoin-project/filecoin-plus-large-datasets/issues/1579/1416920331@ github.com>
Dear applicant,
Thank you for applying for datacap. As Filecoin FIL+ notary i am screening your application and conducting due diligence.
Can you show us visible proof of the size of your data and the storage systems you have there?
As last question i would like you to fill out this form to provide us with the necessary information to make a educated decision on your LDN request if we would like to support it.
Thanks!
5PiB
500TiB
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
f01858410
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
250TiB
e01dc661-fcec-415b-b14b-58818b8665d0
Dear Filecoin+ Github applicant,
We have noticed that some of you are submitting merged datacap requests for datasets that are already (partly) on the chain. While we appreciate your enthusiasm to contribute to the Filecoin network, we want to remind you that this behaviour may not be beneficial to the network in the long run. In fact, this behaviour has been questioned and discussed in issue https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/832 on the Filecoin notary-governance Github repository.
We encourage you to review the discussions in issue https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/832. It's important to ensure that your datacap requests are valid, necessary, and add value to the network. By doing so, you can help to maintain the integrity and sustainability of the Filecoin network.
You can find the link to issue https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/832 here: https://github.com/filecoin-project/notary-governance/issues/832
Thank you for your understanding and cooperation.
@datalove2 although there is no rule against merged datasets currently, but how do you plan to make the data available for public to use? Do you have your own website to perform indexing of these different datasets?
@herrehesse Thanks for the reminder. @kernelogic Thanks for the review. First of all, all the data we store will be retrievable, and we have optimized the efficiency of data retrieval to support fast retrieval. If you'd like to support us, you can review the data after data has been uploaded.
Fei Yan @.***> 於 2023年2月28日 星期二寫道:
@datalove2 https://github.com/datalove2 although there is no rule against merged datasets currently, but how do you plan to make the data available for public to use? Do you have your own website to perform indexing of these different datasets?
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1579#issuecomment-1447513010, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5T7HZCSIN2RB3V6KJXSJETWZVVILANCNFSM6AAAAAAUO3OZHU . You are receiving this because you were mentioned.Message ID: <filecoin-project/filecoin-plus-large-datasets/issues/1579/1447513010@ github.com>
For example, if I want to retrieve 3kricegenome, how do I know which CIDs belong to this dataset? Will you provide a list?
@kernelogic We will record the data with tags to distinguish different project data. In addition we will also provide a list of CIDs.
Fei Yan @.***> 於 2023年2月28日 星期二寫道:
For example, if I want to retrieve 3kricegenome, how do I know which CIDs belong to this dataset? Will you provide a list?
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1579#issuecomment-1447574295, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5T7HZA4VTADN4NVEAMM2GLWZWALNANCNFSM6AAAAAAUO3OZHU . You are receiving this because you were mentioned.Message ID: <filecoin-project/filecoin-plus-large-datasets/issues/1579/1447574295@ github.com>
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceael6yjkgibwgsm2hwlz3gnsvhtsezype7ylslfjlkcacx5a7bcsw
Address
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
Datacap Allocated
250.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
e01dc661-fcec-415b-b14b-58818b8665d0
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceael6yjkgibwgsm2hwlz3gnsvhtsezype7ylslfjlkcacx5a7bcsw
Which SPs have you contacted? Please list them and their distribution areas
@Tom-OriginStorage, Hi there, Here are some SPs we found, and the number of SPs will be increased with more allocation. f01896036 US; f02037700 KR; f02047841 CN; f02024315 Thailand; f01834253 US; f01853077 SG...
Tom-OriginStorage @.***> 於 2023年2月28日 星期二寫道:
Which SPs have you contacted? Please list them and their distribution areas
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1579#issuecomment-1447748743, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5T7HZCK3V6V7KH5BU7BU6DWZWXOVANCNFSM6AAAAAAUO3OZHU . You are receiving this because you were mentioned.Message ID: <filecoin-project/filecoin-plus-large-datasets/issues/1579/1447748743@ github.com>
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceaf2mpdp3zv7uncrbbcyzeru2had2wniqzilqx6zisnqx3f36v3jk
Address
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
Datacap Allocated
250.00TiB
Signer Address
f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga
Id
e01dc661-fcec-415b-b14b-58818b8665d0
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaf2mpdp3zv7uncrbbcyzeru2had2wniqzilqx6zisnqx3f36v3jk
f02049625
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
500TiB
1f5ba341-65a7-4e76-b991-1fd7d40f28a1
f01858410
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
llifezou & kernelogic
100% of weekly dc amount requested
500TiB
500TiB
4.51PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
7139 | 5 | 250TiB | 22.17 | 53.68TiB |
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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 full report.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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 full report.
Since this is the 3rd allocation, the following restrictions have been relaxed:
- No more than 70% of unique data are stored with less than 3 providers.
✔️ Data replication looks healthy.
Unique Data Size Total Deals Made Number of Providers Deal Percentage 229.19 TiB 229.19 TiB 1 59.03% 15.81 TiB 31.63 TiB 2 8.14% 21.75 TiB 65.25 TiB 3 16.80% 9.97 TiB 39.88 TiB 4 10.27% 4.47 TiB 22.34 TiB 5 5.75%
The unbalanced data distribution is acceptable in the first three rounds. But I personally recommend paying more attention to the Checker report, and please try to find more SPs in different locations. Would like to know more about your future plan.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebrz6472agrs3d322nqlf6w7bqh2z7vgnv6cfjb2du2rqwosaw7qq
Address
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
Datacap Allocated
500.00TiB
Signer Address
f1hlubjsdkv4wmsdadihloxgwrz3j3ernf6i3cbpy
Id
1f5ba341-65a7-4e76-b991-1fd7d40f28a1
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebrz6472agrs3d322nqlf6w7bqh2z7vgnv6cfjb2du2rqwosaw7qq
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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 full report.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacec74oqfsmtv6yj44inhoiispkdgnredmpvyue2aaemntyj4dnjxfc
Address
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
Datacap Allocated
500.00TiB
Signer Address
f1tbd632f6w62glfaf7wjpimacbnjiz26poyoes2q
Id
1f5ba341-65a7-4e76-b991-1fd7d40f28a1
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec74oqfsmtv6yj44inhoiispkdgnredmpvyue2aaemntyj4dnjxfc
f02049625
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
1.95PiB
214c4a34-ab6e-4575-a438-4a969ae00284
f02049625
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
400% of weekly dc amount requested
1.95PiB
454747350886464356352.0YiB
-5.49B
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
5772 | 9 | 500TiB | 27.63 | 124.25TiB |
✔️ Storage provider distribution looks healthy.
⚠️ 89.25% of deals are for data replicated across less than 4 storage providers.
⚠️ CID sharing has been observed. (Top 3)
[^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 full report.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceaxqhtwm2pnuw53yf7scowbcyqh4ifuwm6u6kli254p65tcezdzsa
Address
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
Datacap Allocated
1.95PiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaxqhtwm2pnuw53yf7scowbcyqh4ifuwm6u6kli254p65tcezdzsa
f02049625
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
1.95PiB
1348b904-e877-4545-a29f-b477b4b6cb58
f02049625
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
400% of weekly dc amount requested
1.95PiB
454747350886464356352.0YiB
-5.49B
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
11934 | 9 | 500TiB | 21.29 | 34.75TiB |
✔️ Storage provider distribution looks healthy.
⚠️ 85.65% of deals are for data replicated across less than 4 storage providers.
⚠️ CID sharing has been observed. (Top 3)
[^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 full report.
✔️ Storage provider distribution looks healthy.
⚠️ 85.65% of deals are for data replicated across less than 4 storage providers.
⚠️ CID sharing has been observed. (Top 3)
[^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 full report.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebe6gs2acrss4ihre4h3u3quklf2powvthwynrc3kgm5o6jlj2hbc
Address
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
Datacap Allocated
1.95PiB
Signer Address
f1a2lia2cwwekeubwo4nppt4v4vebxs2frozarz3q
Id
1348b904-e877-4545-a29f-b477b4b6cb58
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebe6gs2acrss4ihre4h3u3quklf2powvthwynrc3kgm5o6jlj2hbc
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 89.90% of deals are for data replicated across less than 4 storage providers.
⚠️ CID sharing has been observed. (Top 3)
[^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 report.
@datalove2 Although the sealing speed of different SPs is different, the data distribution problem at the current stage needs to be resolved as soon as possible. Part of the data can be retrieved, but the proportion of data that can be retrieved needs to be increased.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecnjuzoovihnkkq7yauyfm5ll7tt7xc67zazcojnr4p5axwbg3x7o
Address
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
Datacap Allocated
1.95PiB
Signer Address
f1foiomqlmoshpuxm6aie4xysffqezkjnokgwcecq
Id
1348b904-e877-4545-a29f-b477b4b6cb58
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecnjuzoovihnkkq7yauyfm5ll7tt7xc67zazcojnr4p5axwbg3x7o
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 89.90% of deals are for data replicated across less than 4 storage providers.
⚠️ CID sharing has been observed. (Top 3)
[^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 report.
lotus client retrieve --provider f01854080 --pieceCid baga6ea4seaqggenwkzclg2dtnp6jijwicbqi4llt4aslo75kuhstoizfh3j6mcq bafykbzacebmkzuqtlib52xe5mvojlqzmb3ovjjztjncrzqez33qqutpuntwq4 ~/ The customer contacted me and explained to me the reasons for CID sharing and retrieval. I am willing to support customers in this round for the time being, and I will keep paying attention.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedv3ap5kvtpkb62icr4q7vswvfljeyc66serjksqhk6xtwdmmowpw
Address
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
Datacap Allocated
1.95PiB
Signer Address
f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea
Id
1348b904-e877-4545-a29f-b477b4b6cb58
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedv3ap5kvtpkb62icr4q7vswvfljeyc66serjksqhk6xtwdmmowpw
Client f02048944 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 |
---|---|---|---|
Cid Checker score | > 25% | The client has a CID checker score of 11%. This should be greater than 25%. To find out more about CID checker score please look at this issue: https://github.com/filecoin-project/notary-governance/issues/986 |
Data Owner Name
RongYIn Open Data Project 1
Data Owner Country/Region
China
Data Owner Industry
IT & Technology Services
Website
https://www.qcc.com/firm/3380acbb3101bd58394d1ba4be51e877.html
Social Media
Total amount of DataCap being requested
5PiB
Weekly allocation of DataCap requested
500TiB
On-chain address for first allocation
f1es3jnh7ivhvc32s23mro7wuktehjkxlc7yjac6a
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
How do you plan to prepare the dataset
IPFS, lotus, singularity, graphsplit
If you answered "other/custom tool" in the previous question, enter the details here
No response
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
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, South America, Europe, Australia (continent)
How will you be distributing your data to storage providers
HTTP or FTP server, IPFS, Shipping hard drives, Lotus built-in data transfer
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, Lotus client, Singularity
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