Closed hhhhxiao closed 11 months ago
The report shows that the data distribution is relatively concentrated. What is the reason for this and how to avoid it in the future?
checker:manualTrigger
⚠️ 1 storage providers sealed more than 30% of total datacap - f02121645: 42.82%
⚠️ 100.00% of deals are for data replicated across less than 4 storage providers.
✔️ 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 full report.
The report shows that the data distribution is relatively concentrated. What is the reason for this and how to avoid it in the future?
Some SPs have faster encapsulation speed, and some are slower. However, the ratio has improved compared with the previous round of signatures. Next, we will optimize this to ensure that it meets the requirements.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebk376wtgg3qzmaegsjkhj7ue3dcmyvq72myykeiermk2vodijglg
Address
f16xlgzogkkd5qm44uftfprkvh44gu4ruo7dmngca
Datacap Allocated
1.17PiB
Signer Address
f1cjzbiy5xd4ehera4wmbz63pd5ku4oo7g52cldga
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebk376wtgg3qzmaegsjkhj7ue3dcmyvq72myykeiermk2vodijglg
Retrieval looks ok, willing to support this round
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceavcynpcdwubmbq6a5kuuwmuj7rs2lhns3csnfevwcw4vcpdkhmhw
Address
f16xlgzogkkd5qm44uftfprkvh44gu4ruo7dmngca
Datacap Allocated
1.17PiB
Signer Address
f1txboxiscdm4f3okffyjmbilmwjtbisrbee72j6q
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceavcynpcdwubmbq6a5kuuwmuj7rs2lhns3csnfevwcw4vcpdkhmhw
checker:manualTrigger
⚠️ 1 storage providers sealed more than 30% of total datacap - f01261113: 33.72%
⚠️ 76.80% of deals are for data replicated across less than 4 storage providers.
✔️ 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 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.
thanks please keep it open
Can you check retrievals please?
Not all your miners are online at the moment.
cat 1436-f02060232-f0130556-34793173-baga6ea4seaql42yqhusbdveijmmvgdlfyaj44nseaehv7bhfh2x5lih6jmqqwhi.log 2023-07-27T06:20:59.711+0200 WARN rpc go-jsonrpc@v0.3.1/client.go:615 unmarshaling failed {"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW:\n [/ip4/120.232.233.80/tcp/24001] dial tcp4 120.232.233.80:24001: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0130556\",\"MinerPeer\":{\"Address\":\"f0130556\",\"ID\":\"12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW\",\"PieceCID\":null}}"} 2023-07-27T06:20:59.711+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-27T06:22:13.005+0200 WARN rpc go-jsonrpc@v0.3.1/client.go:615 unmarshaling failed {"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW:\n [/ip4/120.232.233.80/tcp/24001] dial tcp4 120.232.233.80:24001: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0130556\",\"MinerPeer\":{\"Address\":\"f0130556\",\"ID\":\"12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW\",\"PieceCID\":null}}"} 2023-07-27T06:22:13.005+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-27T06:24:57.602+0200 WARN rpc go-jsonrpc@v0.3.1/client.go:615 unmarshaling failed {"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW:\n [/ip4/120.232.233.80/tcp/24001] dial tcp4 120.232.233.80:24001: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0130556\",\"MinerPeer\":{\"Address\":\"f0130556\",\"ID\":\"12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW\",\"PieceCID\":null}}"} 2023-07-27T06:24:57.602+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-27T06:27:17.107+0200 WARN rpc go-jsonrpc@v0.3.1/client.go:615 unmarshaling failed {"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW:\n [/ip4/120.232.233.80/tcp/24001] dial tcp4 120.232.233.80:24001: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0130556\",\"MinerPeer\":{\"Address\":\"f0130556\",\"ID\":\"12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW\",\"PieceCID\":null}}"} 2023-07-27T06:27:17.107+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-27T06:29:43.846+0200 WARN rpc go-jsonrpc@v0.3.1/client.go:615 unmarshaling failed {"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW:\n * [/ip4/120.232.233.80/tcp/24001] dial tcp4 120.232.233.80:24001: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0130556\",\"MinerPeer\":{\"Address\":\"f0130556\",\"ID\":\"12D3KooWMAvCj89Vc9bYL7F41swmHV1YGLck6nSfhKQPPugZAeBW\",\"PieceCID\":null}}"} 2023-07-27T06:29:43.847+0200 ERROR retry retry/retry.go:29 Failed after 5 attempts, last error: RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' ERROR: RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"'
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.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 64.93% of deals are for data replicated across less than 4 storage providers.
✔️ 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.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 65.56% of deals are for data replicated across less than 4 storage providers.
✔️ 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.
Only 3 of your SP's are online at the moment. Why?
Only 3 of your SP's are online at the moment. Why?
Thanks, we are contacting SP to find out why.
Some SPs could not be contacted, and one of them said that their technology encountered a problem and could not be solved temporarily. We decided to suspend cooperation with the problematic SP and wait for their repair to be completed before re-cooperating. @cryptowhizzard
You have only 3 Sp's left , only 42% of your data is retrievable at maximum. :(
Let me know who you consider for replacement. I hope SP's with reputation this time?
f02049625
f16xlgzogkkd5qm44uftfprkvh44gu4ruo7dmngca
1.17PiB
c3f95fcb-b8ad-458e-b685-2cbfa298420f
f02049625
f16xlgzogkkd5qm44uftfprkvh44gu4ruo7dmngca
400% of weekly dc amount requested
1.17PiB
1.0896474123001104e+36YiB
1.0896474123001104e+36YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
53254 | 10 | 1.17PiB | 27.33 | 302.92TiB |
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 40.75% of deals are for data replicated across less than 4 storage providers.
✔️ 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.
I downloaded the data and made it available here:
The data does not match the data applicant indicated he is storing.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 31.91% of deals are for data replicated across less than 4 storage providers.
✔️ 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.
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.
Project in progress
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.
Project in progress
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.
Project in progress
Hello, @hhhhxiao 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.
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.
@Sunnyiscoming Sorry, it took me so long to reply to your message. Fil+ registration form has been submitted. Please check it. Thank you.
SP list provided f0130556 | Lanhe | CN | no | no f02051716 | US | no | no f02040772 | HB | UK | no | no f02320270 | R1 | US | no | no
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 31.91% of deals are for data replicated across less than 4 storage providers.
✔️ 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.
SPs taking deals: 130556 | Guangzhou, Guangdong, CNChina Mobile communications corporation | 145.06 TiB | 6.81% | 144.97 TiB | 0.06% f02226869 | Nanchang, Jiangxi, CNCHINA UNICOM China169 Backbone | 463.34 TiB | 21.74% | 463.34 TiB | 0.00% f01261113 | Shenzhen, Guangdong, CNCHINANET-BACKBONE | 451.22 TiB | 21.18% | 438.78 TiB | 2.76% f02059207 | Shenzhen, Guangdong, CNCHINANET-BACKBONE | 126.03 TiB | 5.91% | 126.03 TiB | 0.00% f01261218 | Shenzhen, Guangdong, CNCHINANET-BACKBONE | 50.28 TiB | 2.36% | 50.28 TiB | 0.00% f02121645 | Hanoi, Hanoi, VNDREAM POWER TECHNOLOGY LIMITED | 370.69 TiB | 17.40% | 370.69 TiB | 0.00% f02329561new | Hong Kong, Central and Western, HKDREAM POWER TECHNOLOGY LIMITED | 303.00 TiB | 14.22% | 303.00 TiB | 0.00% f02051716new | Seattle, Washington, USGTHost | 116.13 TiB | 5.45% | 116.13 TiB | 0.00% f02040772new | London, England, GBGTHost | 105.06 TiB | 4.93% | 105.06 TiB | 0.00%
SPs don't match list provided. Closing until a clear list of SP entities and distribution is provided
Sorry for replying so late, please confirm, thank you @Filplus-govteam
f02226869 | Nanchang | Frogbt | Darren | mantttsun@outlook.com f012611139 | Shenzhen | LunaTec | Lou | 1971197597@qq.com f021216459 | Hanoi | InfinityGroup | Eric | xvecos@163.com f02329561new9 | Hong Kong | AlphaConnections | Connor | xigancheng@gmail.com f02051716new9 | Seattle | StellarTech | Lucien | toneysgp@gmail.com f02040772new9 | London | APWS | Ken | furo2861@gmail.com
OK. Please collect SP entity and location information and send to filplus.govteam@gmail.com
@Filplus-govteam The email has been sent, please confirm
@Filplus-govteam @Sunnyiscoming Who do I need to ask for help to use it properly?
Data Owner Name
Shenzhen Weite Network Culture Co., Ltd.
Data Owner Country/Region
China
Data Owner Industry
Information, Media & Telecommunications
Website
http://www.oktrust.com.cn/
Social Media
Total amount of DataCap being requested
5PiB
Weekly allocation of DataCap requested
300TiB
On-chain address for first allocation
f16xlgzogkkd5qm44uftfprkvh44gu4ruo7dmngca
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
lotus
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
More than 3 years
In which geographies do you plan on making storage deals
Greater China
How will you be distributing your data to storage providers
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
No response
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