Closed nicelove666 closed 11 months ago
checker:manualTrigger
⚠️ 2 storage providers sealed too much duplicate data - f02363308: 46.02%, f02217602: 22.82%
✔️ 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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
Hi, dear notary, thank you for your question. We have explained this problem many times. Because the technical guy mailed the hard drive repeatedly, there was a problem of duplicate data. Since we discovered it, we immediately informed the SP to stop using it. Since then, we have not continued to cooperate with SP, so the backup data will not increase. Thank you.
Hi, dear notary, thank you for your question. We have explained this problem many times. Because the technical guy mailed the hard drive repeatedly, there was a problem of duplicate data. Since we discovered it, we immediately informed the SP to stop using it. Since then, we have not continued to cooperate with SP, so the backup data will not increase. Thank you.
That's not the problem.it's storing too much duplicate data, it's over 20%, is there a plan to fix this at a later stage?
According to communication, the two SP are not encapsulated for the time being. If they need to continue to encapsulate, we hope to continue to work with them and send different data, so we can solve the problem of duplicate data.
Okay, looking forward to getting to health
Browsing past comments will support this round of
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedshz3iaj6frduvujmb3a6i4b5q4vgtotb6cr46o4rxhnvkuvnwum
Address
f1y5mkyvzsfxsapuecbbs4hrrmio2te6ajdqpgedq
Datacap Allocated
2.00PiB
Signer Address
f1cjzbiy5xd4ehera4wmbz63pd5ku4oo7g52cldga
Id
443282f1-5a84-4010-b624-387267c960c5
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedshz3iaj6frduvujmb3a6i4b5q4vgtotb6cr46o4rxhnvkuvnwum
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.
please keep it open, thanks
f02049625
f1y5mkyvzsfxsapuecbbs4hrrmio2te6ajdqpgedq
2PiB
23542cfc-5d9c-48fd-9138-4e22abd4bf76
Hi @kevzak I have found that this application has been involved in several irregular activities in several aspects.
The applied quantity of DC and the actual distribution quantity do not match. In the chat records of this post, it can be seen that the applicant initially applied for 15P, but after communication with Sunnyiscoming, for reasons unknown, the DC allocation was increased to 27P. According to the existing LDN application rules, such a large-scale DC distribution should not have been granted here.
The applicant engaged in repetitive signing by the same two notaries. In the below picture I provided, two notaries, Darleen and Peng Kai, simultaneously signed two applications. This action clearly violates LDN's notary signing regulations.
Once again, I believe this post involves fraudulent activities and should be closed.
checker:manualTrigger
This application was overlooked as a very large Dataset. Anything above 15PiB needs to follow E-Fil+ pathway. Closing until client completes KYC and provides clear SP list
⚠️ 1 storage providers sealed too much duplicate data - f02217602: 22.82%
✔️ 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 CID Checker report. Click here to view the Retrieval Dashboard.
Was 12PiB of DC Stolen here by @nicelove666 again? @kevzak can you investigate?
Now, the maxmium of datacap requested is not 15 PB. If you want to apply for this dataset later, why did you apply for 15 PB this time, not total amount of all remaining data?
We originally applied for 6 copies of 5Pib (1947-1952), but they were closed because they were not used. Later we decided to reapply. We initially applied for 15Pib, and then we expressed that we would apply for another LDN after using the 15Pib. Later, sunyiscoming expressed that the LDN application quota can exceed 15PiB, so we applied for 27PiB.
Why it is 27Pib, we have a detailed explanation in the 1947 application: We counted the data on this website, a total of 500,800 pieces of information, with a total capacity of 4.2P.
Since 1947+1948+1949 used 15Pib, 42-15=27Pib.
The entire series holds 42pib of data, and it is very reasonable for a single sp to store 2Pib.
At the same time, according to my observation, sunyiscoming multiple applications for a single LDN can exceed 15Pib.
Data Owner Name
National Radio Astronomy Observatory
What is your role related to the dataset
Data Preparer
Data Owner Country/Region
United States
Data Owner Industry
Life Science / Healthcare
Website
https://data.nrao.edu/portal/#/
Social Media
Total amount of DataCap being requested
27PiB
Expected size of single dataset (one copy)
1P
Number of replicas to store
10
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1y5mkyvzsfxsapuecbbs4hrrmio2te6ajdqpgedq
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
How do you plan to prepare the dataset
IPFS, lotus, singularity
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, Africa, North America, Europe
How will you be distributing your data to storage providers
Cloud storage (i.e. S3), HTTP or FTP server, IPFS, Shipping hard drives, Lotus built-in data transfer
How do you plan to choose storage providers
Slack, Filmine, Big Data Exchange
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, Droplet 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