Open fengqiangjun opened 1 year ago
Thanks for your request!
Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!
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
400TiB
Client address
f1q6nz6hvnif6uakrebwyio74b5ggfhgvn4jqz7tq
f02049625
f1q6nz6hvnif6uakrebwyio74b5ggfhgvn4jqz7tq
200TiB
b399b4d3-43a5-4815-8822-1405a5d4b2c5
We are contacting sp and will start packaging shortly.
Dear applicant,
Thank you for applying for datacap. As Filecoin FIL+ notary i am screening your application and conducting due diligence.
Looking at your application i have some questions: As you are brand new on Github and have no history of past applications it seems to me that applying for 5PB of datacap is a lot. One needs comprehensive knowledge of Filecoin, packing of data, distribution of data and all it's requirements coming with it. Are you brand new in the Filecoin space or have you applied for datacap in the past on different Github account names?
Can you show us visible proof of the size of your data and the storage systems you have there?
As last question i would like you to fill out this form to provide us with the necessary information to make a educated decision on your LDN request if we would like to support it.
Thanks!
Can you send confirmation email to filplus-app-review@fil.org using the email address of your company domain? @Sunnyiscoming please help verify and confirm.
Data sample link is invalid now.
@Joss-Hua @Sunnyiscoming
The email has been sent, please check.
Data sample link is invalid now.
Thanks for your reply, the above sample data link has expired, here is the new data sample link, please check. https://drive.google.com/file/d/1ViDtaOk9QXo2VnNu3yLMulL43S89aH1T/view?usp=share_link https://drive.google.com/file/d/1satxm0PmKYzHpAkydo84RCLVHEX-4pc8/view?usp=share_link https://drive.google.com/file/d/13hoTMxQUFKErmpicEeJBbOsL-zs7SCJ8/view?usp=share_link https://drive.google.com/file/d/1yGz2PvELTDGgXIorlLOxLYcLjHus3xeN/view?usp=share_link https://drive.google.com/file/d/1UCOHJTBiXd80ZajwttOj8F2F9tGOXIHK/view?usp=share_link https://drive.google.com/file/d/1g0FDuQwpyhsOyqOG9TPcjnMxoYbbjxMX/view?usp=share_link
@Joss-Hua
I know that the filecoin network stores public data. No disputes will arise.
Support the first round and wait for the first retrieval check
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacec4ym6wn6efdric5wzm245hdrl343b43rheoqion53ywq2j6re65m
Address
f1q6nz6hvnif6uakrebwyio74b5ggfhgvn4jqz7tq
Datacap Allocated
200.00TiB
Signer Address
f1tfg54zzscugttejv336vivknmsnzzmyudp3t7wi
Id
b399b4d3-43a5-4815-8822-1405a5d4b2c5
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec4ym6wn6efdric5wzm245hdrl343b43rheoqion53ywq2j6re65m
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceabndd27fwnmtbltluwn56lumbgjrutzmnyweayusngvchbgtmesq
Address
f1q6nz6hvnif6uakrebwyio74b5ggfhgvn4jqz7tq
Datacap Allocated
200.00TiB
Signer Address
f12mckci3omexgzoeosjvstcfxfe4vqw7owdia3da
Id
b399b4d3-43a5-4815-8822-1405a5d4b2c5
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceabndd27fwnmtbltluwn56lumbgjrutzmnyweayusngvchbgtmesq
How much public data do you currently have? Can you screen capture and show me the size of the data you have?
Are there any selected storage providers? If you have, please list it.
- How much public data do you currently have? Can you screen capture and show me the size of the data you have?
- Are there any selected storage providers? If you have, please list it.
I'll apply for the first round.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacearssvb7kjbkjojerha7limlaihn4gbtdjzkiw5bz4bhtvlxzcmy2
Address
f1q6nz6hvnif6uakrebwyio74b5ggfhgvn4jqz7tq
Datacap Allocated
200.00TiB
Signer Address
f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i
Id
b399b4d3-43a5-4815-8822-1405a5d4b2c5
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacearssvb7kjbkjojerha7limlaihn4gbtdjzkiw5bz4bhtvlxzcmy2
⚠️ All retrieval success ratios are below 1%.
⚠️ 1 storage providers sealed more than 90% of total datacap - f0155829: 95.68%
⚠️ 91.32% of deals are for data replicated across less than 2 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.
⚠️ 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.
f02049625
f1q6nz6hvnif6uakrebwyio74b5ggfhgvn4jqz7tq
400TiB
50669e69-4d26-45e7-b3a5-bc9854730cf6
f02049625
f1q6nz6hvnif6uakrebwyio74b5ggfhgvn4jqz7tq
100% of weekly dc amount requested
400TiB
200TiB
4.80PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
4699 | 2 | 200TiB | 63.31 | 49.71TiB |
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedqoh3tjxsbg3z7itysif5352yv6l5zrou36lmawwxru5ojhpveey
Address
f1q6nz6hvnif6uakrebwyio74b5ggfhgvn4jqz7tq
Datacap Allocated
400.00TiB
Signer Address
f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea
Id
50669e69-4d26-45e7-b3a5-bc9854730cf6
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedqoh3tjxsbg3z7itysif5352yv6l5zrou36lmawwxru5ojhpveey
checker:manualTrigger
⚠️ 1 storage providers sealed more than 70% of total datacap - f0155829: 71.47%
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 28.92%
⚠️ 100.00% of deals are for data replicated across less than 3 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.
We have found some problems in the information provided in the Approved Comment. We could not find Address** field in the information provided
Please, take a look at the comment and edit the body of the comment providing all the required information.
@mikezli
Why are you proposing when there is so much duplicate data and with almost 0% retrieval?
Btw,
"In which geographies (countries, regions) do you plan on making storage deals? HongKong or North America."
It seems to me that you are storing elsewhere?
Yes, Hong Kong and North America are the locations where we prefer to store data. However, unfortunately, we have encountered many challenges in finding service providers (SPs). Many Filecoin SPs come from the Greater China region, and since we have a company in Beijing and a larger network within the Chinese community, we initially found two SPs in China. Fortunately, we have now managed to find some reliable overseas SPs who will perform better in terms of retrieval. We will start packaging in the next few days. As newcomers to Filecoin, we still have a lot of room for improvement in selecting SPs and implementing Fil+.
Btw,
"In which geographies (countries, regions) do you plan on making storage deals? HongKong or North America."
It seems to me that you are storing elsewhere?
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 31.53%
⚠️ 100.00% of deals are for data replicated across less than 3 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.
Hello,
cat 1365-f01938503-f01302188-47802139-baga6ea4seaqlqh7f33uhdumv7a6noypuj3huoiwhj36375o6jdd3yg7vnuutgda.log Recv 0 B, Paid 0 FIL, Open (New), 7.446s [1690024162200370533|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 7.449s [1690024162200370533|0]
It seems you are not proving readily retrieval since you did not store the unsealed sectors and now the retrieval times out.
Pleases fix this with your SP's before we move / sign next allocation so notary's can do proper due diligence.
Hello,
cat 1365-f01938503-f01302188-47802139-baga6ea4seaqlqh7f33uhdumv7a6noypuj3huoiwhj36375o6jdd3yg7vnuutgda.log Recv 0 B, Paid 0 FIL, Open (New), 7.446s [1690024162200370533|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 7.449s [1690024162200370533|0]
It seems you are not proving readily retrieval since you did not store the unsealed sectors and now the retrieval times out.
Pleases fix this with your SP's before we move / sign next allocation so notary's can do proper due diligence.
Regarding the CID you mentioned, we have conducted tests and confirmed that it can be retrieved successfully. However, we believe that part of the reason for the low success rate in retrieval is due to the deployment of retrieval clients mostly outside of China, resulting in high latency. In order to address this issue, we have identified several service providers outside mainland China, and we hope that they can help change the current situation. We kindly request your continued support. Thank you.
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 31.78%
⚠️ 82.00% of deals are for data replicated across less than 3 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.
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 30.95%
⚠️ 79.06% of deals are for data replicated across less than 3 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.
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 28.96%
⚠️ 78.76% of deals are for data replicated across less than 3 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.
@cryptowhizzard
Can you sign for me, please? @cryptowhizzard
Seems the SP that stored 42% of your data is offline. Can you fix so i can do retrieval?
Yes, I have already contacted the service provider (SP) to handle the situation. If they don't handle it properly, I will terminate the partnership with them. If you have any good methods to punish the SP, I believe they will quickly fix the issue. That's why we choose to store multiple copies of the data. Fortunately, I have found some SPs with data retrieval guarantees. It is unreasonable to halt the entire project's progress due to issues with only 1.7% of the SPs. If you have any SPs with data retrieval guarantees to recommend or any good selection methods to share, it would be helpful for someone new to the Filecoin community. @cryptowhizzard
We have already contacted the sp to handle it. Please double-check and support us. Thank you.
@cryptowhizzard
@cryptowhizzard
@fengqiangjun
The retrieval bot can be gamed for downloads. PL is working on a new improved version that does real downloads.
Anyway, please see:
root@proposals:/var/www/html/filplus# ls | grep 1365 1365-f01938503-f01302188-46933839-baga6ea4seaqp7behkxklmzl2nfrmtuk6theikqls7jza5jv4onwbtajdam2ughq.log 1365-f01938503-f01302188-47802139-baga6ea4seaqlqh7f33uhdumv7a6noypuj3huoiwhj36375o6jdd3yg7vnuutgda.log 1365-f01938503-f0155829-45237977-baga6ea4seaqimfjvkvx5dtch5lbrrc5a7uipbd6lwufyhzsbwmsgt2nl7bdfwai.log 1365-f01938503-f02058146-48526029-baga6ea4seaqhqwqj633fhtgvjqtmo6kjqgbdrylgsxbvduibtg3u2i4rawer2ki.log root@proposals:/var/www/html/filplus# ls -l | grep 1365 -rw-r--r-- 1 root root 145 Aug 1 12:12 1365-f01938503-f01302188-46933839-baga6ea4seaqp7behkxklmzl2nfrmtuk6theikqls7jza5jv4onwbtajdam2ughq.log -rw-r--r-- 1 root root 152 Jul 26 18:15 1365-f01938503-f01302188-47802139-baga6ea4seaqlqh7f33uhdumv7a6noypuj3huoiwhj36375o6jdd3yg7vnuutgda.log -rw-r--r-- 1 root root 4371 Jul 31 22:17 1365-f01938503-f0155829-45237977-baga6ea4seaqimfjvkvx5dtch5lbrrc5a7uipbd6lwufyhzsbwmsgt2nl7bdfwai.log -rw-r--r-- 1 root root 373 Aug 1 18:23 1365-f01938503-f02058146-48526029-baga6ea4seaqhqwqj633fhtgvjqtmo6kjqgbdrylgsxbvduibtg3u2i4rawer2ki.log root@proposals:/var/www/html/filplus# cat 1365- Recv 0 B, Paid 0 FIL, Open (New), 0s [1690024162200371271|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 9ms [1690024162200371271|0] Recv 0 B, Paid 0 FIL, Open (New), 7.446s [1690024162200370533|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 7.449s [1690024162200370533|0] 2023-07-31T22:09:48.883+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 12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM:\n [/ip4/115.236.46.84/tcp/45580] dial tcp4 212.6.53.183:64532-\u003e115.236.46.84:45580: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0155829\",\"MinerPeer\":{\"Address\":\"f0155829\",\"ID\":\"12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM\",\"PieceCID\":null}}"} 2023-07-31T22:09:48.883+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-31T22:12:51.763+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 12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM:\n [/ip4/115.236.46.84/tcp/45580] dial tcp4 212.6.53.183:64532-\u003e115.236.46.84:45580: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0155829\",\"MinerPeer\":{\"Address\":\"f0155829\",\"ID\":\"12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM\",\"PieceCID\":null}}"} 2023-07-31T22:12:51.763+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-31T22:14:44.939+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 12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM:\n [/ip4/115.236.46.84/tcp/45580] dial tcp4 212.6.53.183:64532-\u003e115.236.46.84:45580: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0155829\",\"MinerPeer\":{\"Address\":\"f0155829\",\"ID\":\"12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM\",\"PieceCID\":null}}"} 2023-07-31T22:14:44.939+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-31T22:16:22.484+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 12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM:\n [/ip4/115.236.46.84/tcp/45580] dial tcp4 212.6.53.183:64532-\u003e115.236.46.84:45580: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0155829\",\"MinerPeer\":{\"Address\":\"f0155829\",\"ID\":\"12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM\",\"PieceCID\":null}}"} 2023-07-31T22:16:22.484+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-31T22:17:18.644+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 12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM:\n [/ip4/115.236.46.84/tcp/45580] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f0155829\",\"MinerPeer\":{\"Address\":\"f0155829\",\"ID\":\"12D3KooWMek8PGWh5DMnzpnj9kKFNvwwbnfFounK4mwUs8f9oRFM\",\"PieceCID\":null}}"} 2023-07-31T22:17:18.644+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"'
ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid QmXh9EUgxrM7BA8gvTN9YpW38ADRZ5BD1fxLKTEVMuiZTa: getting pieces containing block QmXh9EUgxrM7BA8gvTN9YpW38ADRZ5BD1fxLKTEVMuiZTa: failed to lookup index for mh 12208af90ce11eeaf0e9fd99fcefc267fc2faf2f103682457f053e024f550aa3fc2d, err: datastore: key not found
You have new mail in /var/mail/root root@proposals:/var/www/html/filplus#
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 28.52%
⚠️ 78.51% of deals are for data replicated across less than 3 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.
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 28.52%
⚠️ 78.51% of deals are for data replicated across less than 3 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.
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 28.52%
⚠️ 78.34% of deals are for data replicated across less than 3 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.
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 28.52%
⚠️ 78.32% of deals are for data replicated across less than 3 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.
⚠️ 1 storage providers sealed too much duplicate data - f01302188: 28.52%
⚠️ 78.32% of deals are for data replicated across less than 3 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.
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 this 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?