Closed AohuanTec 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.
Can you provide evidence that the background images, music, button clicks, and sound effects of animation transitions are generated and owned by your organization? Additionally, we need more details on how much data you have. It is difficult to determine the request for 3 PiBs
There are two sources of material resources used in the front-end development process. Common materials such as button styles and transition effects generally use public resources on the Internet. We have integrated and summarized the scattered resources. In addition, for special effects, we will use generative software (such as Houdini) to customize the generation.
At present, we've collected and created about >700TiB of material files:
One direct details are as follows:
We plan to store a minimum of 4-5 copies on the Filecoin network, so we applied for a DC capacity of 3PiB. In the future, the material files will be continuously added and updated, and we will continue to store the data on the chain.
Hello, team, @raghavrmadya , we offered evidence a few days ago. if you noticed our reply and have no other questions, could you please update our application? Thanks!
Total DataCap requested
3PiB
Expected weekly DataCap usage rate
100TiB
Client address
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
f01858410
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
50TiB
ed917fb0-7f87-4c75-a298-efee6a379039
1:Could you send an email to filplus-app-review@fil.org ? 2:Can you provide more detailed information about other storage providers participated in this program, such as you can list SPs you have contacted with at present?
As mentioned above, the transmission mode of data sets is online downloading. Please provide a download link to verify that you have a 700TIB dataset
Because the notary has raised questions and has not responded, waiting for the client to deal with it...
@Tom-OriginStorage
The email address is not from your domain name(aohuanit.com). Could you send an email to filplus-app-review@fil.org with your official domain in order to confirm your identity? Email name should includes the issue id #940.
@Sunnyiscoming
We don't have an email with domain (aohuanit.com), but the "master@360server.cn" is the official email address of our company, you can get this address from our official website.
In addition, the content of the email contains a complete link to this issue.
Ok. I saw that.
Some notaries require to use the mail with the domain name (aohuanit.com) for KYC verification. Our company has been using the free corporate mail provided by 360, and the domain name is 360server.cn. In order to comply with the review rules of Fil+, we specially applied for our own domain name email address and resent the email. Official staff and notaries are requested to verify.
Currently contacted SPs include NWG, Shenzhen Star-Storage, SXX Future Data, node numbers: f01943316, f01964215, f022820, f0815838, f01801587, f01981603
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecngbijcytqaes46nlk2eilhkbeotkhsajajwqs5hyhs6b6xwpkdc
Address
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
Datacap Allocated
50.00TiB
Signer Address
f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga
Id
ed917fb0-7f87-4c75-a298-efee6a379039
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecngbijcytqaes46nlk2eilhkbeotkhsajajwqs5hyhs6b6xwpkdc
Sign the primary DC allocation based on the initial verified data.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceai6au6p7lf7dfdi3udkztr2ybxaoege7rvgleua7tvniqtygbzai
Address
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
Datacap Allocated
50.00TiB
Signer Address
f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i
Id
ed917fb0-7f87-4c75-a298-efee6a379039
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceai6au6p7lf7dfdi3udkztr2ybxaoege7rvgleua7tvniqtygbzai
f01858410
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
100TiB
0cf0ef0a-7940-4a31-93a1-dcbe60c7d477
f01858410
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
psh0691 & llifezou
100% of weekly dc amount requested
100TiB
50TiB
2.95PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1337 | 4 | 50TiB | 29.92 | 6.46TiB |
BeijingAohuan Technology Co., Ltd.
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
1
psh06911
Tom-OriginStorage
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 |
---|---|---|---|---|---|
f01771695 | Wuhan, Hubei, CNCHINA UNICOM China169 Backbone |
10.38 TiB | 24.98% | 10.38 TiB | 0.00% |
f01964215 | Shenzhen, Guangdong, CNCHINANET-BACKBONE |
6.22 TiB | 14.97% | 6.22 TiB | 0.00% |
f01753456 | Hong Kong, Central and Western, HKUNION FU WAH DIGITAL TECHNOLOGY LIMITED |
12.50 TiB | 30.10% | 12.50 TiB | 0.00% |
f01681234 | Hong Kong, Central and Western, HKUNION FU WAH DIGITAL TECHNOLOGY LIMITED |
12.44 TiB | 29.95% | 12.44 TiB | 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 |
---|---|---|---|
1.16 TiB | 2.31 TiB | 2 | 5.57% |
6.16 TiB | 18.47 TiB | 3 | 44.47% |
5.19 TiB | 20.75 TiB | 4 | 49.96% |
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
Client Contact me on slack, waiting for reply questions for further review.
I contacted the relevant SP manufacturer, and the response to me was that IDC’s China Unicom network service provider had bandwidth problems in the past two days. They were dealing with this problem yesterday, and I will continue to track the network situation.
@AohuanTec If that is the case, then please perform another check and let us know if the miners are reachable. We wil do automated tests every day to see if they stay online, we will also download and extract the data to see if everything is in order.
Until then I kindly ask notaries not to sign and continue with this application.
@AohuanTec How are you going to resolve the distribution, all your SP's are in the same region.
@cryptowhizzard Yes, we urge the relevant SP to continue to fix the retrieval problem. It is worth affirming that their engineers are continuing to improve even during the Chinese New Year holidays, and it seems to have achieved results so far. Now that the holiday is over, we have to start the next storage work. If you approve of our work, please help us sign it.
? f0187709 does not belong to our SPs, nor does the data CID
That is strange. Please ignore my message above, i will check again for you today.
// Cleaning up my above message to start with a clean slate.
Ok , i tested here and i can retrieve data. I don't want to check the data itself and don't want to hold up the proces. I will do a propose.
For the next round, can you please show us some proof of data stored? And please, fill out the KYC form -> this form
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceb66pjbu7o7rgizyemrh7ihwgohetnvpltdirjyhto2ahckppbozm
Address
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
Datacap Allocated
100.00TiB
Signer Address
f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb66pjbu7o7rgizyemrh7ihwgohetnvpltdirjyhto2ahckppbozm
Okay, next round I'll provide evidence that we backed up the unseal files for quick retrieval. If you support our project, please help me complete the signature, this project has been stopped for a while.
@cryptowhizzard I will fill the form later, Thanks!
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedc73sycq4gwkv2ukjgdt5yyxuu7ktvcfsbr7uerfms3qdyys4c6y
Address
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
Datacap Allocated
100.00TiB
Signer Address
f1hhippi64yiyhpjdtbidfyzma6irc2nuav7mrwmi
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedc73sycq4gwkv2ukjgdt5yyxuu7ktvcfsbr7uerfms3qdyys4c6y
f01858410
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
200TiB
21653558-acc7-4cb7-a0df-d22c94baf9d3
f01858410
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
Alex11801 & cryptowhizzard
200% of weekly dc amount requested
200TiB
150TiB
2.85PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
4503 | 7 | 100TiB | 40.42 | 24.75TiB |
BeijingAohuan Technology Co., Ltd.
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
1
Alex118011
cryptowhizzard1
psh06911
Tom-OriginStorage
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 4th allocation, the following restrictions have been relaxed:
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01964253 | Guangzhou, Guangdong, CNChina Unicom Guangdong IP network |
4.25 TiB | 3.42% | 4.25 TiB | 0.00% |
f01986229 | Hangzhou, Zhejiang, CNCHINANET-BACKBONE |
43.16 TiB | 34.74% | 43.16 TiB | 0.00% |
f01964215 | Shenzhen, Guangdong, CNCHINANET-BACKBONE |
18.34 TiB | 14.77% | 18.34 TiB | 0.00% |
f01771695 | Hong Kong, Central and Western, HKHONG KONG BRIDGE INFO-TECH LIMITED |
10.38 TiB | 8.35% | 10.38 TiB | 0.00% |
f01876488 | Ho Chi Minh City, Ho Chi Minh, VNUCLOUD INFORMATION TECHNOLOGY (HK) LIMITED |
4.41 TiB | 3.55% | 4.41 TiB | 0.00% |
f01681234 | Hong Kong, Central and Western, HKUNION FU WAH DIGITAL TECHNOLOGY LIMITED |
31.19 TiB | 25.11% | 30.44 TiB | 2.40% |
f01753456 | Hong Kong, Central and Western, HKUNION FU WAH DIGITAL TECHNOLOGY LIMITED |
12.50 TiB | 10.06% | 12.50 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
Since this is the 4th allocation, the following restrictions have been relaxed:
⚠️ 55.12% of deals are for data replicated across less than 4 storage providers.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
15.25 TiB | 15.25 TiB | 1 | 12.28% |
19.63 TiB | 39.25 TiB | 2 | 31.60% |
4.66 TiB | 13.97 TiB | 3 | 11.25% |
4.28 TiB | 17.16 TiB | 4 | 13.81% |
4.88 TiB | 24.59 TiB | 5 | 19.80% |
2.25 TiB | 14.00 TiB | 6 | 11.27% |
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
Hi,
I tested retrieval today with SP f01964215, it did not work. Can you please take a look.
Feb 9 12:20:03 proposals dealscanner-f01914993-f01964215: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675842797944985820|0] Feb 9 12:20:03 proposals dealscanner-f01914993-f01964215: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 13ms [1675842797944985820|0] Feb 9 12:20:04 proposals dealscanner-f01914993-f01964215: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 461ms [1675842797944985820|0] Feb 9 12:20:04 proposals dealscanner-f01914993-f01964215: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 462ms [1675842797944985820|0] Feb 9 12:20:04 proposals dealscanner-f01914993-f01964215: Recv 0 B, Paid 0 FIL, ProviderCancelled (Cancelling), 464ms [1675842797944985820|0] Feb 9 12:20:04 proposals dealscanner-f01914993-f01964215: Recv 0 B, Paid 0 FIL, CancelComplete (Cancelled), 465ms [1675842797944985820|0] Feb 9 12:20:04 proposals dealscanner-f01914993-f01964215: ERROR: Retrieval Proposal Cancelled: Provider cancelled retrieval Feb 9 12:20:04 proposals dealscanner-f01914993-f01964215:
unseal files for quick retrieval:
@herrehesse Since the CIDs that have just been sealed must be manually merged with metadata before they can be retrieved, there will be a time lag in the retrieval of a new batch of dealids. I just contacted SP operation and maintenance to manually merge metadata, and I have tested it locally. If you find a dealid that cannot be retrieved later, you can notify me to solve it.
#lotus state get-deal 24199558
{
"Proposal": {
"PieceCID": {
"/": "baga6ea4seaqhlu5rnceguvmmrbrbeqv7dskbn3t424p3olt3mcq4tb6qtligwfy"
},
"PieceSize": 34359738368,
"VerifiedDeal": true,
"Client": "f01914993",
"Provider": "f01964215",
"Label": "uAXASIB2-4-qdjlm2dQMf9jSe80kzAPi0TWuLgvVrSbkqny8z",
"StartEpoch": 2594873,
"EndEpoch": 4135816,
"StoragePricePerEpoch": "0",
"ProviderCollateral": "10382840982189418",
"ClientCollateral": "0"
},
"State": {
"SectorStartEpoch": 2585917,
"LastUpdatedEpoch": -1,
"SlashEpoch": -1,
"VerifiedClaim": 6663278
}
}
# lotus client retrieve --provider f01964215 uAXASIB2-4-qdjlm2dQMf9jSe80kzAPi0TWuLgvVrSbkqny8z test.car
Recv 0 B, Paid 0 FIL, Open (New), 0s
Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3ms
Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 179ms
Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 179ms
Recv 25.99 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 551ms
Recv 27.85 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 552ms
Recv 1.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 903ms
Recv 2.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1.198s
Recv 3.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1.658s
Recv 4.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1.869s
Recv 5.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.051s
Recv 6.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.11s
Recv 7.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.433s
Recv 8.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.843s
Recv 9.027 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.248s
Recv 10.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.755s
Recv 11.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 4.248s
Recv 12.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 4.7s
Recv 13.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 5.15s
Recv 14.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 5.56s
Recv 15.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 5.999s
@AohuanTec Thank you for the collaboration and continued work. Together we must strive for perfection. Can you provide us with information about which SP's are which businesses?
As long as the data that you claim to store is packed and inside the retrieved sectors, will continue to support.
@herrehesse pls check Slack PM
Received. Please let me know if your retrievals are OK and willing to support this next round.
checker:manualTrigger
BeijingAohuan Technology Co., Ltd.
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
1
Alex118011
cryptowhizzard1
psh06911
Tom-OriginStorage
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 4th allocation, the following restrictions have been relaxed:
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01964253 | Guangzhou, Guangdong, CNChina Mobile communications corporation |
4.25 TiB | 2.89% | 4.25 TiB | 0.00% |
f01986229 | Hangzhou, Zhejiang, CNCHINANET-BACKBONE |
43.16 TiB | 29.36% | 43.16 TiB | 0.00% |
f01964215 | Shenzhen, Guangdong, CNCHINANET-BACKBONE |
18.34 TiB | 12.48% | 18.34 TiB | 0.00% |
f01986236 | Los Angeles, California, USCogent Communications |
12.00 TiB | 8.17% | 12.00 TiB | 0.00% |
f01771695 | Hong Kong, Central and Western, HKHONG KONG BRIDGE INFO-TECH LIMITED |
10.38 TiB | 7.06% | 10.38 TiB | 0.00% |
f01876488 | Singapore, Singapore, SGSingNet |
15.16 TiB | 10.31% | 15.16 TiB | 0.00% |
f01681234 | Hong Kong, Central and Western, HKUNION FU WAH DIGITAL TECHNOLOGY LIMITED |
31.19 TiB | 21.22% | 30.44 TiB | 2.40% |
f01753456 | Hong Kong, Central and Western, HKUNION FU WAH DIGITAL TECHNOLOGY LIMITED |
12.50 TiB | 8.51% | 12.50 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
Since this is the 4th allocation, the following restrictions have been relaxed:
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
13.06 TiB | 13.06 TiB | 1 | 8.89% |
13.25 TiB | 26.50 TiB | 2 | 18.03% |
1.22 TiB | 3.66 TiB | 3 | 2.49% |
16.28 TiB | 65.16 TiB | 4 | 44.33% |
4.88 TiB | 24.59 TiB | 5 | 16.73% |
2.25 TiB | 14.00 TiB | 6 | 9.53% |
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.[^3]
✔️ 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> ...
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebdkrk3ksttjvlerym4qafox44r6ysevub3zse5jxtb62nmtr4izc
Address
f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq
Datacap Allocated
200.00TiB
Signer Address
f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i
Id
21653558-acc7-4cb7-a0df-d22c94baf9d3
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebdkrk3ksttjvlerym4qafox44r6ysevub3zse5jxtb62nmtr4izc
Hi,
I would love to do due diligence here and move forward on this LDN, however, retrieval does not work.
Feb 15 17:22:08 proposals dealscanner-f01914993-f01986236: Error: Failed to retrieve content with candidate miner f01986236: data transfer failed: datatransfer error: data transfer channel 12D3KooWGJpT1vdLktshKZRWrA3Apw1eKBxwjPfoJF64AtEwdKrq-12D3KooWGgu8UiXJF3rBiBKdShrWDaffcWZwpAndyCY5qehQimj5-1676477401279110771 failed to transfer data: channel 12D3KooWGJpT1vdLktshKZRWrA3Apw1eKBxwjPfoJF64AtEwdKrq-12D3KooWGgu8UiXJF3rBiBKdShrWDaffcWZwpAndyCY5qehQimj5-1676477401279110771: graphsync request failed to complete: expected link (bafybeig5hmw4g6ywjev4plgkilbsf3ynwuvcr4kowysi5gg54jza2qwkb4) at path does not match link sent by remote (bafkreigat6c4kd6smbpi6jxgu24m4qhejrfxd3nsko7tyzclx73w5ze724), possible malicious responder
@cryptowhizzard Can you provide the deal_id or dataCID which cannot retrieve? I will contact SP to resolve the issue.
Done on slack.
Feb 16 19:01:26 proposals dealscanner-f01914993-f01986236: Recv 43.62 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 17m22.031s [1676445845934082941|45734848] Feb 16 19:13:30 proposals dealscanner-f01914993-f01986236: Recv 43.62 MiB, Paid 0 FIL, DataTransferError (Erroring), 29m26.178s [1676445845934082941|45734848] Feb 16 19:13:30 proposals dealscanner-f01914993-f01986236: Recv 43.62 MiB, Paid 0 FIL, BlockstoreFinalized (Errored), 29m26.18s [1676445845934082941|45734848] Feb 16 19:13:30 proposals dealscanner-f01914993-f01986236: ERROR: Retrieval Error: error generated by data transfer: deal data transfer failed: data transfer channel 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWGgu8UiXJF3rBiBKdShrWDaffcWZwpAndyCY5qehQimj5-1676445845928232540 failed to transfer data: channel 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWGgu8UiXJF3rBiBKdShrWDaffcWZwpAndyCY5qehQimj5-1676445845928232540: graphsync request failed to complete: error traversing node at "Links/4/Hash/Links/18/Hash": could not load link "bafkreig4aimtr2tzizarpfppoxczhi2oviq36xums54576ia6qz7jrnzbm": expected link (bafybeig5hmw4g6ywjev4plgkilbsf3ynwuvcr4kowysi5gg54jza2qwkb4) at path does not match link sent by remote (bafkreie6cckkyqr2ymixq2d462tushww3oakcug7iof72mzd5cb67wk6qq), possible malicious responder Feb 16 19:13:30 proposals dealscanner-f01914993-f01986236:
Still not working btw.
@cryptowhizzard It can be seen that the data is not unretrievable. There is no problem with our server, but your location is too far away from the location of the node, causing network packet loss, so let's not be too pedantic.
I went all the way to spin up a AWS node in Singapore zone and was able to retrieve a full sector and validate its content. In the future I will use this Singapore node to validate Asian SPs.
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?