Closed tanjian917 closed 12 months ago
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
Hey, great to see your reply.
Looking forward to seeing you agree us, best wishes to you!
@tanjian917
What are their business names and are they on VPN?
Thank you for your reminder, we added the company name, SP did not use VPN, we are honest, thank you! f02221112: GuangDong yuanxing f01920887: Australia Sindurot f02246008: Hong Kong Calculus f02199203: Inner Mongolia KuQi f02370792: GuangDong Star Alliance f02200472: Sichuan longcould
Have you completed Fil+ registration form?
Here are previous results of the same mining group. Seems to me that these miners belong to the same entity as they are noted by multiple KYC applicants as the same organisation. Most of them seem reachable and no previous VPN history.
Hey, brother, in your picture, there are other LDN SPs, which are basically completely different from the SPs we listed.
以下是同一采矿组之前的结果。在我看来,这些矿工属于同一实体,因为多个 KYC 申请人将它们视为同一组织。其中大多数似乎可以访问,并且以前没有 VPN 历史记录。
Yes, we submitted it, thank you @Sunnyiscoming
Total DataCap requested
10PiB
Expected weekly DataCap usage rate
1PiB
Client address
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
f02049625
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
512TiB
e6bae94c-e68e-4e9e-8e69-acbf599210fe
Please continue to do investigation about sp.
@Sunnyiscoming why do you open up a trench and then start to investigate?
$ lotus net connect f02221112
f02221112 -> {12D3KooWFoGjYwLmkzpDAnANZfBE5fRM7XDjxLeqn5ewhfaoiCqm: [/ip4/[14.119.112.16/tcp/21341](http://14.119.112.16/tcp/21341)]}
ERROR: failed to parse multiaddr "f02221112": must begin with /
$ lotus net connect f01920887
f01920887 -> {12D3KooWSWpG2Rsbwr2J7c7omDVuiw6BPBZwBMSrSHjpjfWa4GD2: [/ip4/[203.129.131.94/tcp/11288](http://203.129.131.94/tcp/11288)]}
ERROR: failed to parse multiaddr "f01920887": must begin with /
$ lotus net connect f02246008
f02246008 -> {12D3KooWQA1VguWa7de3ajNf2sQ5i7feaiKppjsjs12b8Qggj1cn: [/ip4/[116.92.243.2/tcp/24002](http://116.92.243.2/tcp/24002)]}
ERROR: failed to parse multiaddr "f02246008": must begin with /
$ lotus net connect f02199203
f02199203 -> {12D3KooWLUiX6qKj1RXHWdHGBifKPwT1DQ1UdAoTLAskC82mUTUS: [/ip4/[116.136.130.130/tcp/6789](http://116.136.130.130/tcp/6789)]}
ERROR: failed to parse multiaddr "f02199203": must begin with /
$ lotus net connect f02370792
f02370792 -> {12D3KooWKa1NQKxveFmppQAjkHG8RGpjoQ2ivubeNuEUgZGgc2T6: [/ip4/[119.147.160.231/tcp/41555](http://119.147.160.231/tcp/41555)]}
ERROR: failed to parse multiaddr "f02370792": must begin with /
$ lotus net connect f02200472
f02200472 -> {12D3KooWDeJTed3dzgLYEAHsfLcjCuBSCHj1XYzJppA9phf4kLbZ: [/ip4/[171.93.112.10/tcp/41335](http://171.93.112.10/tcp/41335)]}
ERROR: failed to parse multiaddr "f02200472": must begin with /
Checked all the MinerIDs provided by the client are reachable and use different IPs. In addition, the client has completed the KYC email certification and registration form submission. I will provide support in the first round and stay tuned.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecmgwx3xv4k7sf4gvfikdwwr3zyawfyp52aouj4vpjh2d7mhfjvze
Address
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
Datacap Allocated
512.00TiB
Signer Address
f1jyvhxp4kmwreo22ke4itspraznpudw3uqaink5i
Id
e6bae94c-e68e-4e9e-8e69-acbf599210fe
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecmgwx3xv4k7sf4gvfikdwwr3zyawfyp52aouj4vpjh2d7mhfjvze
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceakzk2kqhkctwyty72cgrb4y26hyorqgf2ivaqfiw4buiejcb3nzu
Address
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
Datacap Allocated
512.00TiB
Signer Address
f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga
Id
e6bae94c-e68e-4e9e-8e69-acbf599210fe
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceakzk2kqhkctwyty72cgrb4y26hyorqgf2ivaqfiw4buiejcb3nzu
@Bitengine-reeta & @Tom-OriginStorage - Highly questionable signatures, if the data or retrieval is not in order will instantly dispute.
f02049625
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
512TiB
79c2a989-b482-404a-bb8d-c48060f96afb
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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.
The data has not been updated, the retrieval data is incorrect, the SP has not received the bot's retrieval record. Please help to check it. @raghavrmadya @Sunnyiscoming @simonkim0515 @fabriziogianni7 @jbesraa
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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.
It's so weird why it hasn't been updated yet , we have to close it and reapply
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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.
✔️ Data replication looks healthy.
✔️ 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.
✔️ Data replication looks healthy.
✔️ 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.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebvi6gfhpbbslq6nwt4p75jbywpywmosboyed26gu4xyjdpc6ukpk
Address
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
Datacap Allocated
512.00TiB
Signer Address
f1xx6555qijma7igpnjspyvdunc4vfxkawnpqy5ii
Id
79c2a989-b482-404a-bb8d-c48060f96afb
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebvi6gfhpbbslq6nwt4p75jbywpywmosboyed26gu4xyjdpc6ukpk
The reports looks so nice.Willing to support it
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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.
There are two SPs with a retrieval rate of 0. Please provide an explanation for this situation and propose improvement plans.
@igoovo SP's machines have meet some problems and being repaired. We are helping them repair them. If they still cannot repair them within 10 days, we will no longer cooperate with them.
Review the history of LDN Github. The retrieval rate is gradually improving, and the Client has made improvement plans for some SPs with low retrieval rates. KYC is also verified as required. There is no CID sharing, and the SPs are relatively scattered. So willing to support the LDN in this round and will keep an eye on it.
⚠️ All retrieval success ratios are below 1%. Overall Graphsync retrieval success rate: 0.00% —————— Retrieval Statistics Overall Graphsync retrieval success rate: 33.33% Overall HTTP retrieval success rate: 0.00% —————— Retrieval Statistics Overall Graphsync retrieval success rate: 50.00%
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced56i7t4olcllcfa3ce7ihxs2a6k6mvoklqjgwam6cnc5l3btsv4m
Address
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
Datacap Allocated
512.00TiB
Signer Address
f1shnsfayxqll77svffaxnjenms7bbbysbqcatrpy
Id
79c2a989-b482-404a-bb8d-c48060f96afb
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced56i7t4olcllcfa3ce7ihxs2a6k6mvoklqjgwam6cnc5l3btsv4m
f02049625
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
1PiB
fb05e8f0-5ffa-496c-98a2-1e668d5263d0
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
✔️ 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.
The report shows healthy and we'd like to give support.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceaepyn3jyhmnmbsuuzvzwzr45dydc63emgfztgit25hsal6t5otds
Address
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
Datacap Allocated
1.00PiB
Signer Address
f1nknj7ayq4o43czrtdoauggtwl43fbqatmqis3yy
Id
fb05e8f0-5ffa-496c-98a2-1e668d5263d0
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaepyn3jyhmnmbsuuzvzwzr45dydc63emgfztgit25hsal6t5otds
Data Owner Name
Guangdong Zhiyun Urban Construction Technology Co., Ltd.
What is your role related to the dataset
Dataset Owner
Data Owner Country/Region
China
Data Owner Industry
Life Science / Healthcare
Website
https://www.jiancaiyi.com/
Social Media
Total amount of DataCap being requested
10PiB
Expected size of single dataset (one copy)
1024
Number of replicas to store
10
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1zvurht6mq5qbo6gq7r7wxisw25z262ocmbg7pva
Data Type of Application
Public, Open Commercial/Enterprise
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
If you are a data preparer. What is your location (Country/Region)
China
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
No response
If you are not preparing the data, who will prepare the data? (Provide name and business)
No response
Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution.
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.5 to 2 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
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
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, Bidbot
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