Closed Lind111 closed 11 months ago
The reports look so nice.It has a CID sharing warning.The client has explained it was the cause of SP and an unexpected situation.
Thanks you!
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval 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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
f02049625
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
2PiB
9a952ab0-754f-4bab-8cf6-c35874708480
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 21.79%
✔️ 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.
Can you explain CID sharing and how do you make sure it doesn't happen in the future?
Can you explain CID sharing and how do you make sure it doesn't happen in the future?
@mikezli Thanks,You can check out this comment from 3 weeks ago that,You can also check out the bot report for the past two weeks, there's been no more additions to the,Thank you for your review
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceaukjnpmzvcepf65iu4mrwwqp5qdlqioptstkrh2d3vcdx74bdype
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
2.00PiB
Signer Address
f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea
Id
9a952ab0-754f-4bab-8cf6-c35874708480
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaukjnpmzvcepf65iu4mrwwqp5qdlqioptstkrh2d3vcdx74bdype
Deal Data Shared with other Clients2 ⚠️ CID sharing has been observed. (Top 3) 2.25 TiB - f1xvsgtyg7ymo6giksv6qb6gxrr6xsfhjjjyylfey - #2100 This problem is being investigated.
The reason has been found Because we have the same cooperation with the domestic SPs :f01836766, we also use the same method in his local generation of car files, because the SP sent me the information contains a duplicate belongs to the #2100 car file, so send the same order, resulting in this problem!
Make sense to me. Willing to support this round.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebww72k766gh3zj2q7hg3l3euhf3n7yonqpelh4ecdkfvyukyzrce
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
2.00PiB
Signer Address
f1bp3tzp536edm7dodldceekzbsx7zcy7hdfg6uzq
Id
9a952ab0-754f-4bab-8cf6-c35874708480
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebww72k766gh3zj2q7hg3l3euhf3n7yonqpelh4ecdkfvyukyzrce
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 24.88%
✔️ 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.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.63%
✔️ 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.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
f02049625
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
2PiB
83041cad-7339-4fb5-b717-ab2be582cb97
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
Can you please explain the CID sharing with Liaoning Zhongguan Environmental engineering ?
Can you please explain the CID sharing with Liaoning Zhongguan Environmental engineering ?
Check out the previous comments, thanks!
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecyz23lw5x5lptnbtskfwlfqkt36p4ivemv2fszxumm4z3ep5ncf6
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
2.00PiB
Signer Address
f1a2lia2cwwekeubwo4nppt4v4vebxs2frozarz3q
Id
83041cad-7339-4fb5-b717-ab2be582cb97
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecyz23lw5x5lptnbtskfwlfqkt36p4ivemv2fszxumm4z3ep5ncf6
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
The client contacted me again and explained the problems with the robot report, and for such quality data, I'm happy to support this round again!
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacec4twygihgxbods2rscaho5u2tvqc5s3kfwmwlbzeboj7325ulo3w
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
2.00PiB
Signer Address
f1cjzbiy5xd4ehera4wmbz63pd5ku4oo7g52cldga
Id
83041cad-7339-4fb5-b717-ab2be582cb97
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec4twygihgxbods2rscaho5u2tvqc5s3kfwmwlbzeboj7325ulo3w
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f0240185: 25.71%
✔️ 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.
Data Owner Name
EF
What is your role related to the dataset
Dataset Owner
Data Owner Country/Region
China
Data Owner Industry
Education & Training
Website
https://www.hzxsef.com/
Social Media
Total amount of DataCap being requested
15PiB
Expected size of single dataset (one copy)
2.2P
Number of replicas to store
7
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
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
My Own Storage Infra
If you answered "Other" in the previous question, enter the details here
No response
How do you plan to prepare the dataset
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
Monthly
For how long do you plan to keep this dataset stored on Filecoin
More than 3 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China, North America, Europe
How will you be distributing your data to storage providers
HTTP or FTP server, Shipping hard drives
How do you plan to choose storage providers
Slack
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
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