Closed PipengWang closed 1 year 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.
Total DataCap requested
5PiB
Expected weekly DataCap usage rate
100TiB
Client address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
f02049625
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
50TiB
f3b8cd53-72c8-4d52-a599-c9daaf0edadd
Hi @PipengWang
@YuanHeHK
hey @PipengWang Can you provide more detailed information about other storage providers participated in this program? Such as SP ID and geographic location.
hey @liyunzhi-666 ,Sorry for taking so long to reply. We plan to look for about 10 SPs, and currently we are dealing with 5 as follows:
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebe7iu6k2jaujv24a5rhnewmv7jpz6iq4rkcvn7hd2cy64p7g2qkm
Address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
Datacap Allocated
50.00TiB
Signer Address
f1pszcrsciyixyuxxukkvtazcokexbn54amf7gvoq
Id
f3b8cd53-72c8-4d52-a599-c9daaf0edadd
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebe7iu6k2jaujv24a5rhnewmv7jpz6iq4rkcvn7hd2cy64p7g2qkm
The information provided so currently appears to be fine, the first signature gives support, and later if there is a problem, it will not be supported.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacec7uyoyazxmklvirvuk5gasgbsnklp3drfofagobnq66ko5ywhdqk
Address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
Datacap Allocated
50.00TiB
Signer Address
f1fg6jkxsr3twfnyhdlatmq36xca6sshptscds7xa
Id
f3b8cd53-72c8-4d52-a599-c9daaf0edadd
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec7uyoyazxmklvirvuk5gasgbsnklp3drfofagobnq66ko5ywhdqk
f02049625
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
100TiB
9ee93a68-16e9-4b1e-b7c8-bdd16a953160
f01858410
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
liyunzhi-666 & not found
100% of weekly dc amount requested
100TiB
50TiB
4.95PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1166 | 6 | 50TiB | 21.01 | 10.84TiB |
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
Since this is the 3rd allocation, the following restrictions have been relaxed:
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908695 | Osaka, Ōsaka, JP | 7.50 TiB | 24.05% | 7.50 TiB | 0.00% |
f01908646 | Los Angeles, California, US | 7.06 TiB | 22.65% | 7.06 TiB | 0.00% |
f01949065 | Los Angeles, California, US | 5.72 TiB | 18.34% | 5.72 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JP | 5.31 TiB | 17.03% | 5.31 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JP | 5.28 TiB | 16.93% | 5.28 TiB | 0.00% |
f01955058 | Los Angeles, California, US | 320.00 GiB | 1.00% | 320.00 GiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
Since this is the 3rd allocation, the following restrictions have been relaxed:
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
256.00 GiB | 256.00 GiB | 1 | 0.80% |
1.59 TiB | 3.19 TiB | 2 | 10.22% |
352.00 GiB | 1.03 TiB | 3 | 3.31% |
960.00 GiB | 3.75 TiB | 4 | 12.02% |
4.22 TiB | 21.09 TiB | 5 | 67.64% |
320.00 GiB | 1.88 TiB | 6 | 6.01% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceclipbcmgti73go3npo36jda4wjskud3zt62ejbqxjrzyywlmki56
Address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
Datacap Allocated
100.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
9ee93a68-16e9-4b1e-b7c8-bdd16a953160
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceclipbcmgti73go3npo36jda4wjskud3zt62ejbqxjrzyywlmki56
CID Checker looks alright, willing to support
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedujwxe6wyzeb7spzrjg6bdjdptysa6k2l2uen7lt4647p7wgrgcg
Address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
Datacap Allocated
100.00TiB
Signer Address
f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga
Id
9ee93a68-16e9-4b1e-b7c8-bdd16a953160
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedujwxe6wyzeb7spzrjg6bdjdptysa6k2l2uen7lt4647p7wgrgcg
f02049625
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
200TiB
c56103e4-ad15-4bf7-b036-e54b415384d0
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908646 | Los Angeles, California, US | 7.66 TiB | 19.65% | 7.66 TiB | 0.00% |
f01908695 | Osaka, Ōsaka, JP | 7.66 TiB | 19.65% | 7.66 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JP | 7.66 TiB | 19.65% | 7.66 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JP | 7.66 TiB | 19.65% | 7.66 TiB | 0.00% |
f01949065 | Los Angeles, California, US | 7.63 TiB | 19.57% | 7.63 TiB | 0.00% |
f01955058 | Los Angeles, California, US | 736.00 GiB | 1.84% | 736.00 GiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
32.00 GiB | 128.00 GiB | 4 | 0.32% |
6.91 TiB | 34.53 TiB | 5 | 88.61% |
736.00 GiB | 4.31 TiB | 6 | 11.07% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceck6hbcavlen2gwx3fvs5ptawkp3io7l45px6wkozxhstkcyseage
Address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
Datacap Allocated
200.00TiB
Signer Address
f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga
Id
c56103e4-ad15-4bf7-b036-e54b415384d0
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceck6hbcavlen2gwx3fvs5ptawkp3io7l45px6wkozxhstkcyseage
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedt22nafugwjxcw7e5eel2vsh6o6w44z77ojza3b2qcithhilbyuc
Address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
Datacap Allocated
200.00TiB
Signer Address
f1fg6jkxsr3twfnyhdlatmq36xca6sshptscds7xa
Id
c56103e4-ad15-4bf7-b036-e54b415384d0
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedt22nafugwjxcw7e5eel2vsh6o6w44z77ojza3b2qcithhilbyuc
f02049625
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
400TiB
c67c26db-f8a9-4da9-bde9-8c0ec1341829
f01858410
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
fireflyHZ & llifezou
400% of weekly dc amount requested
400TiB
150TiB
4.85PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
4328 | 6 | 200TiB | 17.49 | 9.21TiB |
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
1
fireflyHZ1
kernelogic1
liyunzhi-6662
Tom-OriginStorage1
YuanHeHK
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908646 | Los Angeles, California, USFiber Logic Inc. |
23.53 TiB | 16.83% | 23.53 TiB | 0.00% |
f01949065 | Los Angeles, California, USIT7 Networks Inc |
23.47 TiB | 16.79% | 23.47 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JPIT7 Networks Inc |
23.47 TiB | 16.79% | 23.47 TiB | 0.00% |
f01908695 | Osaka, Ōsaka, JPIT7 Networks Inc |
23.41 TiB | 16.74% | 23.41 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JPIT7 Networks Inc |
23.34 TiB | 16.70% | 23.34 TiB | 0.00% |
f01955058 | Los Angeles, California, USIT7 Networks Inc |
22.59 TiB | 16.16% | 22.59 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
64.00 GiB | 256.00 GiB | 4 | 0.18% |
2.00 TiB | 10.00 TiB | 5 | 7.15% |
21.59 TiB | 129.56 TiB | 6 | 92.67% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
1
fireflyHZ1
kernelogic1
liyunzhi-6662
Tom-OriginStorage1
YuanHeHK
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908646 | Los Angeles, California, USFiber Logic Inc. |
56.47 TiB | 16.73% | 56.47 TiB | 0.00% |
f01949065 | Los Angeles, California, USIT7 Networks Inc |
56.41 TiB | 16.71% | 56.41 TiB | 0.00% |
f01908695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.69% | 56.34 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.69% | 56.34 TiB | 0.00% |
f01955058 | Los Angeles, California, USIT7 Networks Inc |
56.13 TiB | 16.63% | 56.13 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JPIT7 Networks Inc |
55.91 TiB | 16.56% | 55.91 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
32.00 GiB | 128.00 GiB | 4 | 0.04% |
2.28 TiB | 11.41 TiB | 5 | 3.38% |
54.34 TiB | 326.06 TiB | 6 | 96.58% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
1
fireflyHZ1
kernelogic1
liyunzhi-6662
Tom-OriginStorage1
YuanHeHK
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908646 | Los Angeles, California, USFiber Logic Inc. |
56.47 TiB | 16.73% | 56.47 TiB | 0.00% |
f01949065 | Los Angeles, California, USIT7 Networks Inc |
56.41 TiB | 16.71% | 56.41 TiB | 0.00% |
f01908695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.69% | 56.34 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.69% | 56.34 TiB | 0.00% |
f01955058 | Los Angeles, California, USIT7 Networks Inc |
56.13 TiB | 16.63% | 56.13 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JPIT7 Networks Inc |
55.91 TiB | 16.56% | 55.91 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
32.00 GiB | 128.00 GiB | 4 | 0.04% |
2.28 TiB | 11.41 TiB | 5 | 3.38% |
54.34 TiB | 326.06 TiB | 6 | 96.58% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
checker:manualTrigger
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
1
fireflyHZ1
kernelogic1
liyunzhi-6662
Tom-OriginStorage1
YuanHeHK
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908646 | Los Angeles, California, USFiber Logic Inc. |
56.47 TiB | 16.73% | 56.47 TiB | 0.00% |
f01949065 | Los Angeles, California, USIT7 Networks Inc |
56.41 TiB | 16.71% | 56.41 TiB | 0.00% |
f01908695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.69% | 56.34 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.69% | 56.34 TiB | 0.00% |
f01955058 | Los Angeles, California, USIT7 Networks Inc |
56.13 TiB | 16.63% | 56.13 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JPIT7 Networks Inc |
55.91 TiB | 16.56% | 55.91 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
32.00 GiB | 128.00 GiB | 4 | 0.04% |
2.28 TiB | 11.41 TiB | 5 | 3.38% |
54.34 TiB | 326.06 TiB | 6 | 96.58% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
checker result looks very good.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecfps27rsuf33bfiyuwi2ind2araoplvvl7d5ovd3vvfokz7y5sr6
Address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
Datacap Allocated
400.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
c67c26db-f8a9-4da9-bde9-8c0ec1341829
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecfps27rsuf33bfiyuwi2ind2araoplvvl7d5ovd3vvfokz7y5sr6
Looks normal
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebtkpprza35h6gy2zxfbuzrdyctayz6v7lsv3d75flptln6ilcll4
Address
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
Datacap Allocated
400.00TiB
Signer Address
f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq
Id
c67c26db-f8a9-4da9-bde9-8c0ec1341829
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebtkpprza35h6gy2zxfbuzrdyctayz6v7lsv3d75flptln6ilcll4
f02049625
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
800TiB
086f4beb-e223-4ea1-a5fa-a603af6a9a41
f01858410
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
newwebgroup & kernelogic
800% of weekly dc amount requested
800TiB
350TiB
4.65PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
10878 | 6 | 400TiB | 16.67 | 10.06TiB |
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
1
fireflyHZ2
kernelogic1
liyunzhi-6661
newwebgroup2
Tom-OriginStorage1
YuanHeHK
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908646 | Los Angeles, California, USFiber Logic Inc. |
56.47 TiB | 16.71% | 56.47 TiB | 0.00% |
f01949065 | Los Angeles, California, USIT7 Networks Inc |
56.41 TiB | 16.69% | 56.41 TiB | 0.00% |
f01908695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
f01955058 | Los Angeles, California, USIT7 Networks Inc |
56.13 TiB | 16.60% | 56.13 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
32.00 GiB | 128.00 GiB | 4 | 0.04% |
1.84 TiB | 9.22 TiB | 5 | 2.73% |
54.78 TiB | 328.69 TiB | 6 | 97.24% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Hello,
None of these miners are supporting retrieval of deals and none of this miners are reachable at all for retrieval.
This is against the FIL+ rules and guidelines and shall be fixed before next allocation of datacaps can proceed
lotus net connect f01908646 f01908646 -> {12D3KooWDr4AEQMuVqdhGFnC48vM1Vap5paan1yqsvpaF12yWwrf: [/ip4/74.211.110.65/tcp/59111]} ERROR: failed to parse multiaddr "f01908646": must begin with /
root@proposals:~# telnet 74.211.110.65 59111 Trying 74.211.110.65... Connected to 74.211.110.65. Escape character is '^]'. Connection closed by foreign host.
lotus net connect f01949065 f01949065 -> {12D3KooWDViFSHfrvC3usC8Nio9bJ6WbmrvoCgGiwDFw5ZCU7USE: [/ip4/173.242.116.70/tcp/59065]} ERROR: failed to parse multiaddr "f01949065": must begin with /
root@proposals:~# telnet 173.242.116.70 59065 Trying 173.242.116.70... telnet: Unable to connect to remote host: Connection refused
lotus net connect f01908695 f01908695 -> {12D3KooWNCSRj6bx4yhfzaJZyx8Pj9jnj9FwResNZHMkRCp9SDwJ: [/ip4/212.50.250.232/tcp/59218]} ERROR: failed to parse multiaddr "f01908695": must begin with /
root@proposals:~# telnet 212.50.250.232 59218 Trying 212.50.250.232... Connected to 212.50.250.232. Escape character is '^]'. Connection closed by foreign host.
lotus net connect f01941229 f01941229 -> {12D3KooWF7jrudF7k2tibthXrC2cyFrAMThm4qLbU4PRMFkj13JC: [/ip4/212.50.245.224/tcp/59112]} ERROR: failed to parse multiaddr "f01941229": must begin with /
root@proposals:~# telnet 212.50.245.224 59112 Trying 212.50.245.224... Connected to 212.50.245.224. Escape character is '^]'. Connection closed by foreign host.
lotus net connect f021695 f021695 -> {12D3KooWFbwEyLfARnZRR26DPJXw1v5tMQW63q2ybMVK8f4Tj69J: [/ip4/212.50.250.232/tcp/59204]} ERROR: failed to parse multiaddr "f021695": must begin with /
root@proposals:~# telnet 212.50.250.232 59204 Trying 212.50.250.232... Connected to 212.50.250.232. Escape character is '^]'. Connection closed by foreign host.
lotus net connect f01955058 f01955058 -> {12D3KooWRRsKt3q9XmisHgaxgv2uRnLnFRjbktCrMbLqzAxbiTob: [/ip4/173.242.116.70/tcp/55058]} ERROR: failed to parse multiaddr "f01955058": must begin with /
root@proposals:~# telnet 173.242.116.70 55058 Trying 173.242.116.70... telnet: Unable to connect to remote host: Connection refused
@PipengWang Hi! Great to see that you have gotten approval for DataCap! BDE is a verified deals auction house helping you to get paid storing your data with reliable storage providers. If you need any help, please get in touch.
checker:manualTrigger
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
1
fireflyHZ2
kernelogic1
liyunzhi-6661
newwebgroup2
Tom-OriginStorage1
YuanHeHK
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908646 | Los Angeles, California, USFiber Logic Inc. |
56.47 TiB | 16.71% | 56.47 TiB | 0.00% |
f01949065 | Los Angeles, California, USFiber Logic Inc. |
56.41 TiB | 16.69% | 56.41 TiB | 0.00% |
f01955058 | Los Angeles, California, USFiber Logic Inc. |
56.13 TiB | 16.60% | 56.13 TiB | 0.00% |
f01908695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
32.00 GiB | 128.00 GiB | 4 | 0.04% |
1.84 TiB | 9.22 TiB | 5 | 2.73% |
54.78 TiB | 328.69 TiB | 6 | 97.24% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Hangzhou Yueyuan Technology Co., Ltd
f166erfrtv2iggppt4mmr7rykcxrz5pkzrcv5a7ry
1
fireflyHZ2
kernelogic1
liyunzhi-6661
newwebgroup2
Tom-OriginStorage1
YuanHeHK
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01908646 | Los Angeles, California, USFiber Logic Inc. |
56.47 TiB | 16.71% | 56.47 TiB | 0.00% |
f01949065 | Los Angeles, California, USFiber Logic Inc. |
56.41 TiB | 16.69% | 56.41 TiB | 0.00% |
f01955058 | Los Angeles, California, USFiber Logic Inc. |
56.13 TiB | 16.60% | 56.13 TiB | 0.00% |
f01908695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
f01941229 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
f021695 | Osaka, Ōsaka, JPIT7 Networks Inc |
56.34 TiB | 16.67% | 56.34 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
32.00 GiB | 128.00 GiB | 4 | 0.04% |
1.84 TiB | 9.22 TiB | 5 | 2.73% |
54.78 TiB | 328.69 TiB | 6 | 97.24% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Hello!
None of your miners support retrieval, everything is firewalled. Please take note on the rules of FIL+ . Clients must be able to connect to download the data.
https://github.com/filecoin-project/filecoin-plus-large-datasets
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.
This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you!
Large Dataset Notary Application
To apply for DataCap to onboard your dataset to Filecoin, please fill out the following.
Core Information
Please respond to the questions below by replacing the text saying "Please answer here". Include as much detail as you can in your answer.
Project details
Share a brief history of your project and organization.
What is the primary source of funding for this project?
What other projects/ecosystem stakeholders is this project associated with?
Use-case details
Describe the data being stored onto Filecoin
Where was the data in this dataset sourced from?
Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this.
Confirm that th is is a public dataset that can be retrieved by anyone on the Network (i.e., no specific permissions or access rights are required to view the data).
What is the expected retrieval frequency for this data?
For how long do you plan to keep this dataset stored on Filecoin?
DataCap allocation plan
In which geographies (countries, regions) do you plan on making storage deals?
How will you be distributing your data to storage providers? Is there an offline data transfer process?
How do you plan on choosing the storage providers with whom you will be making deals? This should include a plan to ensure the data is retrievable in the future both by you and others.
How will you be distributing deals across storage providers?
Do you have the resources/funding to start making deals as soon as you receive DataCap? What support from the community would help you onboard onto Filecoin?