Closed Joss-Hua closed 8 months ago
f02049625
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
400% of weekly dc amount requested
800TiB
7.275957614183429e+35YiB
7.275957614183429e+35YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
39078 | 13 | 800TiB | 23.08 | 195.70TiB |
checker:manualTrigger
⚠️ 2 storage providers have unknown IP location - f01874063, f01874059
⚠️ 100.00% 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.
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.
keep on
checker:manualTrigger
⚠️ 1 storage providers sealed more than 30% of total datacap - f02002688: 34.05%
⚠️ 100.00% 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 Dashboard. Click here to view the Retrieval report.
Thank you for your review @liyunzhi-666 . Regarding 'data replicated', we are continuously expanding the inclusion of SP, and more sps are coming here to provide storage.
Just to explain here, the reason for 'less than 4 storage providers' is:
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedciqkvsltmdr2jmx7ls3qe4a3igppc4m7qdkoplwvzumz6e45nzg
Address
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
Datacap Allocated
800.00TiB
Signer Address
f1pszcrsciyixyuxxukkvtazcokexbn54amf7gvoq
Id
110d9612-c8ff-46e2-ad18-841189e3b01c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedciqkvsltmdr2jmx7ls3qe4a3igppc4m7qdkoplwvzumz6e45nzg
checker:manualTrigger
⚠️ 1 storage providers sealed more than 30% of total datacap - f02002688: 33.89%
⚠️ 100.00% 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 Dashboard. Click here to view the Retrieval report.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedpdxzwovf5ie5yi6cq7hwofnpuvpvm756vmjpt7hyniwhex24ko6
Address
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
Datacap Allocated
800.00TiB
Signer Address
f1cjzbiy5xd4ehera4wmbz63pd5ku4oo7g52cldga
Id
110d9612-c8ff-46e2-ad18-841189e3b01c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedpdxzwovf5ie5yi6cq7hwofnpuvpvm756vmjpt7hyniwhex24ko6
This user’s identity has been verified through filplus.storage
f02049625
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
800TiB
341749a0-78e6-4254-b30e-091fa5a28ff7
f02049625
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
400% of weekly dc amount requested
800TiB
7.275957614183433e+50YiB
7.275957614183433e+50YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
45821 | 13 | 800TiB | 33.89 | 295.83TiB |
checker:manualTrigger
⚠️ 1 storage providers sealed more than 30% of total datacap - f02002688: 33.89%
⚠️ 100.00% 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 Dashboard. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ 1 storage providers sealed more than 30% of total datacap - f02002688: 33.89%
⚠️ 100.00% 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 Dashboard. Click here to view the Retrieval report.
I'm a little concerned about the CID sharing. It is somehow reasonable to see CID sharing with LDN from other venus team, but why NOAA project?
I'm a little concerned about the CID sharing. It is somehow reasonable to see CID sharing with LDN from other venus team, but why NOAA project?
Thank you for your inspection and questions @junyaoren . I hope the following explanation solves your question:
Honestly, looking at Venus LDNs as a whole, it is a bit like aggregated data LDNs. As a client, we are committed to striving to comply with the overall rules of FIL+ and VDA's own rules, so it is inevitable that there will be more or less data sharing between different LDNs.
We hope to achieve a "perfect" report through the management of quotas for each round and the management of relevant community SPs, but to be honest, the difficulty is significant mainly because SPs are truly from the community and have a large number. Timely adjustment of tasks between clients and SPs based on actual situations, rather than "perfect planning" and "step-by-step progress".
Above.
Feel free to contact me if you have any further questions.
Yeah, I can totally understand that as a platform, it is not easy to manage and keep a super clean record. Yet, almost 500TB sharing with NOAA still sounds questionable to me. It'll be best if you could show more evidence of how this exactly happened and how to avoid further incidents like this.
I need to pay more attention to this than usual because the community now is being more cautious about CID sharing, such as discussed here https://github.com/filecoin-project/notary-governance/issues/955#issuecomment-1655490560.
Maybe the governance team can be involved here to see what should be our next step in such a situation. @dkkapur @raghavrmadya @Filplus-govteam
Yeah, I can totally understand that as a platform, it is not easy to manage and keep a super clean record. Yet, almost 500TB sharing with NOAA still sounds questionable to me. It'll be best if you could show more evidence of how this exactly happened and how to avoid further incidents like this.
I need to pay more attention to this than usual because the community now is being more cautious about CID sharing, such as discussed here filecoin-project/notary-governance#955 (comment).
Maybe the governance team can be involved here to see what should be our next step in such a situation. @dkkapur @raghavrmadya @Filplus-govteam
Yes, I absolutely agree with your strictness here and the current community's caution towards data sharing.@junyaoren Because I am also a notary, this is also the issue I am thinking about. CC @Filplus-govteam
What I want to say here is that I can prove that I am good, but I cannot prove that every SP is good. So sadly, I may not be able to avoid it happening again in the future (the reason is as stated in the previous reply). My suggestion for the governance method of this situation is to develop a mechanism from the SP side through FIP, rather than the client side. The current state of clients (whether good or bad) is' thorny but not pleasing '.
Just like when dealing with corruption, if the bribe giver reports the bribe giver, they can be exempted from punishment. This way, the bribe giver and the bribe giver are placed on two ships, so that even if the bribe giver is a direct beneficiary, they no longer dare to take the bribe.
By analogy, when data sharing occurs, deleting the storage power of the violating sector and recycling the DC will effectively prevent recurrence. At the same time, the evaluation criteria of notaries will be unified, making the review work easier. Even the client can report SP violations to avoid being misunderstood. (I often need to explain the retrieval exception of a certain SP, and this should be explained by the SP because in reality, the client cannot control future changes, and everyone seems to forget that the client is customer of Filecoin.)
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.
keep going please
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 66.68% 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 Dashboard. Click here to view the Retrieval report.
@stcouldlisa As mentioned in our other comments in this series, this project includes multiple LDNs and multiple SPs, and we hope to see them as a whole. There are two main reasons for 'data sharing':
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebfqoqwlpjxwis35watxbmneszygg5zj2ksr6hbz2whmtvovyqcdg
Address
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
Datacap Allocated
800.00TiB
Signer Address
f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea
Id
341749a0-78e6-4254-b30e-091fa5a28ff7
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebfqoqwlpjxwis35watxbmneszygg5zj2ksr6hbz2whmtvovyqcdg
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebv2s2lwphlo6h6wlz2n7qa7pu3yqhsahc5nlu7uy6bz57vamk4xm
Address
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
Datacap Allocated
800.00TiB
Signer Address
f12mckci3omexgzoeosjvstcfxfe4vqw7owdia3da
Id
341749a0-78e6-4254-b30e-091fa5a28ff7
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebv2s2lwphlo6h6wlz2n7qa7pu3yqhsahc5nlu7uy6bz57vamk4xm
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.
keep going
f02049625
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
800TiB
1d7d0c0f-efbc-48ce-a2c8-3926a42bb16f
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceb7zmt4khcaaqly3tprsnzdtkuv6varlopd2g4zfw5pzutimfuydy
Address
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
Datacap Allocated
800.00TiB
Signer Address
f1k6wwevxvp466ybil7y2scqlhtnrz5atjkkyvm4a
Id
1d7d0c0f-efbc-48ce-a2c8-3926a42bb16f
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb7zmt4khcaaqly3tprsnzdtkuv6varlopd2g4zfw5pzutimfuydy
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 57.56% 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 Dashboard. Click here to view the Retrieval report.
please increase the number of data replicas in the subsequent process.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebuuknt77wyt2riy7yp357dk7scw7ujlanoucpdgya4fenpqrt2ca
Address
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
Datacap Allocated
800.00TiB
Signer Address
f1foiomqlmoshpuxm6aie4xysffqezkjnokgwcecq
Id
1d7d0c0f-efbc-48ce-a2c8-3926a42bb16f
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebuuknt77wyt2riy7yp357dk7scw7ujlanoucpdgya4fenpqrt2ca
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.
keep going
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.
keep going
checker:manualTrigger
⚠️ 1 storage providers have unknown IP location - f02001777
⚠️ 51.11% 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 Dashboard.
Hello, @Joss-Hua 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.
This information will be reviewed by Fil+ Governance team to confirm validity and then the application will be allowed to move forward for additional notary review.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 54.42% 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 Dashboard.
Yes. Received that.
Data Owner Name
Venus team
Data Owner Country/Region
American Samoa
Data Owner Industry
Other
Website
https://venushub.io
Social Media
Total amount of DataCap being requested
5PiB
Weekly allocation of DataCap requested
200TiB
On-chain address for first allocation
f1fppo2nhn3zd2zfpa6fdqwuqwlho3nerbkrenquq
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
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
Monthly
For how long do you plan to keep this dataset stored on Filecoin
1 to 1.5 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, Shipping hard drives, Others
How do you plan to choose storage providers
Slack, Filmine, Big data exchange, Others
If you answered "Others" in the previous question, what is the tool or platform you plan to use
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
Others/custom tool
If you answered "Others/custom tool" in the previous question, enter the details here
Can you confirm that you will follow the Fil+ guideline
Yes