search

filecoin-project / filecoin-plus-large-datasets

Hub for client applications for DataCap at a large scale
110 stars 62 forks source link

[DataCap Application] Aohuan Technology - Front-end material #940

Closed AohuanTec closed 9 months ago

AohuanTec commented 2 years ago

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.

Beijing Aohuan Technology Co., Ltd. was established in 2008. As a leading IT service provider in China, Aohuan has been focusing on the development and operation of high-end Internet e-commerce and information system platform for many years. Based on the deep cultivation of the Internet industry, Aohuan provides comprehensive digital solutions from the aspects of strategy, technology and operation, creating the ultimate ecology in the "Internet +" era, and helping enterprises to successfully transform.

What is the primary source of funding for this project?

Currently, it mainly comes from financing and operating income, and we do not rule out the introduction of further strategic investment partners in the future.

What other projects/ecosystem stakeholders is this project associated with?

There is no other projects/ecosystem stakeholders associated with.

Use-case details

Describe the data being stored onto Filecoin

The data are material files used in front-end software development, such as background images, music, button clicks and sound effects of animation transitions. We use different styles of materials according to customers' needs to present the most satisfactory results.

Where was the data in this dataset sourced from?

The materials are the virtual effects videos generated by the company's data resources department. Audio files are the materials used in the past front-end software development process. The above resources do not exist copyright disputes, which is the whole network can use.

Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this. 

Audio material sample:
https://drive.google.com/drive/folders/1P3JePaGnuiG7BO4U4KsoO0NIQ3i8I_WN?usp=sharing
Video material sample:
https://drive.google.com/drive/folders/1tUjWtKcz74FyLvhKEd0EH1g2sEdfkRV2?usp=sharing

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).

Yes, it is a public data.

What is the expected retrieval frequency for this data?

The expected retrieval frequency is about 10 times per year.

For how long do you plan to keep this dataset stored on Filecoin?

18 months at least. We will have a try to store a longer time.

DataCap allocation plan

In which geographies (countries, regions) do you plan on making storage deals?

Asia

How will you be distributing your data to storage providers? Is there an offline data transfer process?

There is no offline transmission.
You can upload or download files from an online storage server.

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.

We want to select SPs with a certain level of strength, which will be measured in terms of R&D capability, Oems capability, and maintained storage Filecoin power. We will fully examine the relevant certificates and historical credit ratings of storage enterprises. Of course, we will preferentially select SPs that contribute to the Filecoin retrieval market.

How will you be distributing deals across storage providers?

We will allocate the data according to the comprehensive strength of the storage provider, and the provider with stronger comprehensive strength will get more data capacity.

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?

Yes, we are ready to carry out the project.
If the authorities can provide more FVM related development examples.It would help us learn how to use the Filecoin network to build Dapps.
kernelogic commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceakbese4zuuvv6rg4g6yrakhxoxbxjeuotqb2i2ljss5npmydz6b6

Address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Datacap Allocated

200.00TiB

Signer Address

f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa

Id

21653558-acc7-4cb7-a0df-d22c94baf9d3

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceakbese4zuuvv6rg4g6yrakhxoxbxjeuotqb2i2ljss5npmydz6b6

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Request number 4

Multisig Notary address

f01858410

Client address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

DataCap allocation requested

400TiB

Id

ea6c04a6-2ca5-4860-b072-6055f9154a57

large-datacap-requests[bot] commented 1 year ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Last two approvers

kernelogic & psh0691

Rule to calculate the allocation request amount

400% of weekly dc amount requested

DataCap allocation requested

400TiB

Total DataCap granted for client so far

150TiB

Datacap to be granted to reach the total amount requested by the client (3PiB)

2.85PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
5209 8 200TiB 34.94 2.93TiB
filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^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> ...

Full report

Click here to view the full report.

psh0691 commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceawvbyzcqgopmuaf2v7zppjvjydxcy3huiie7zykgqc4cczoxjf3w

Address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Datacap Allocated

400.00TiB

Signer Address

f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i

Id

ea6c04a6-2ca5-4860-b072-6055f9154a57

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceawvbyzcqgopmuaf2v7zppjvjydxcy3huiie7zykgqc4cczoxjf3w

Joss-Hua commented 1 year ago
image
Joss-Hua commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecxrndvuwxpbyyp6ueohbipoafjne7vcl4p4n63zycouwsnraduf2

Address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Datacap Allocated

400.00TiB

Signer Address

f1tfg54zzscugttejv336vivknmsnzzmyudp3t7wi

Id

ea6c04a6-2ca5-4860-b072-6055f9154a57

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecxrndvuwxpbyyp6ueohbipoafjne7vcl4p4n63zycouwsnraduf2

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Request number 4

Multisig Notary address

f02049625

Client address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

DataCap allocation requested

400TiB

Id

02cf33eb-2318-4a62-87fa-b2e5db93b65e

large-datacap-requests[bot] commented 1 year ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Rule to calculate the allocation request amount

400% of weekly dc amount requested

DataCap allocation requested

400TiB

Total DataCap granted for client so far

36379788070917140480.0YiB

Datacap to be granted to reach the total amount requested by the client (3PiB)

36379788070917140480.0YiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
20981 12 400TiB 21.12 95.84TiB
Bitengine-reeta commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^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> ...

Full report

Click here to view the CID Checker report. Click here to view the Retrieval report.

kernelogic commented 1 year ago

Report LGTM however the retrieval success rate is on the lower end, please improve.

kernelogic commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedcou3snnooijospafjvfncxrbcujcwywjhvhsntjczvvyfpdsszy

Address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Datacap Allocated

400.00TiB

Signer Address

f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa

Id

02cf33eb-2318-4a62-87fa-b2e5db93b65e

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedcou3snnooijospafjvfncxrbcujcwywjhvhsntjczvvyfpdsszy

AohuanTec commented 1 year ago

@kernelogic Thank you for your attention. I contacted the relevant SPs to modify the retrieval problem. I believe that the retrieval rate will be improved in about a week.

large-datacap-requests[bot] commented 1 year ago

Thanks for your request! :exclamation: We have found some problems in the information provided. We could not find Organization Name field in the information provided We could not find Website \/ Social Media field in the information provided We could not find Total amount of DataCap being requested (between 500 TiB and 5 PiB) field in the information provided We could not find Weekly allocation of DataCap requested (usually between 1-100TiB) field in the information provided We could not find On-chain address for first allocation field in the information provided We could not find Data Type of Application field in the information provided

Please, take a look at the request and edit the body of the issue providing all the required information.
AohuanTec commented 1 year ago

@galen-mcandrew @simonkim0515
The request Bot seems to have some problems, I hope it can help solve it, thank you

AohuanTec commented 1 year ago

@kevzak @Kevin-FF-USA @fabriziogianni7 The request Bot seems to have some problems, I hope it can help solve it, thank you

huseyincansoylu commented 1 year ago

hey @AohuanTec thanks for pinging us, it should be working now

AohuanTec commented 1 year ago

@huseyincansoylu nice, thank you so much!

AohuanTec commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^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> ...

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

Bitengine-reeta commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^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> ...

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

Bitengine-reeta commented 1 year ago

img_v2_731c9eba-01fa-46cf-b5b8-0f5109ab876g At the invitation of the client, I have been paying attention to this LDN for a while. The CID checker report shows that there is no problem, but the retrieval rate is low. However, there has been a significant improvement recently. I hope it can be continuously optimized. I will support this round.

Bitengine-reeta commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceboabis2vikso64he6fdg2osnqqz7mfq4brkdydfgq5ak2yreuyys

Address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Datacap Allocated

400.00TiB

Signer Address

f1jyvhxp4kmwreo22ke4itspraznpudw3uqaink5i

Id

02cf33eb-2318-4a62-87fa-b2e5db93b65e

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceboabis2vikso64he6fdg2osnqqz7mfq4brkdydfgq5ak2yreuyys

AohuanTec commented 1 year ago

https://www.aohuanit.com/

herrehesse commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^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> ...

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

cryptowhizzard commented 1 year ago

Recv 0 B, Paid 0 FIL, Open (New), 25ms [1690024162200371979|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 79ms [1690024162200371979|0]RRecv 0 B, Paid 0 FIL, DataTransferError (Erroring), 21h55m27.403s [1690024162200371979|0]RRecv 0 B, Paid 0 FIL, BlockstoreFinalized (Errored), 21h55m27.86s [1690024162200371979|0] ERROR: Retrieval Error: error generated by data transfer: deal data transfer failed: 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWBZmoa1BtHBa8PSUbr43yvudWjqHscHuemXfbkDAmr3Pj-1690024162185104572: after 4 consecutive restarts failed to transfer any data

Recv 0 B, Paid 0 FIL, Open (New), 12m56.931s [1690024162200372288|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 12m56.999s [1690024162200372288|0] 2023-07-31T15:24:03.528+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/10.100.248.104/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e10.100.248.104:12814: i/o timeout\n [/ip4/103.120.228.37/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e103.120.228.37:12814: i/o timeout\n [/ip4/43.255.52.212/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e43.255.52.212:12814: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-07-31T15:24:03.529+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-31T15:25:29.910+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/103.120.228.37/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e103.120.228.37:12814: i/o timeout\n [/ip4/43.255.52.212/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e43.255.52.212:12814: i/o timeout\n [/ip4/10.100.248.104/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e10.100.248.104:12814: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-07-31T15:25:29.910+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-31T15:27:10.159+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/10.100.248.104/tcp/12814] dial backoff\n [/ip4/43.255.52.212/tcp/12814] dial backoff\n [/ip4/103.120.228.37/tcp/12814] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-07-31T15:27:10.159+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-31T15:28:16.151+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/10.100.248.104/tcp/12814] dial backoff\n [/ip4/43.255.52.212/tcp/12814] dial backoff\n [/ip4/103.120.228.37/tcp/12814] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-07-31T15:28:16.152+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-31T15:30:20.736+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/10.100.248.104/tcp/12814] dial backoff\n [/ip4/43.255.52.212/tcp/12814] dial backoff\n * [/ip4/103.120.228.37/tcp/12814] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-07-31T15:30:20.737+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"'

2023-08-01T20:41:12.725+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/10.100.248.104/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e10.100.248.104:12814: i/o timeout\n [/ip4/43.255.52.212/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e43.255.52.212:12814: i/o timeout\n [/ip4/103.120.228.37/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e103.120.228.37:12814: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-08-01T20:41:12.725+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-08-01T20:42:03.948+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/10.100.248.104/tcp/12814] dial backoff\n [/ip4/43.255.52.212/tcp/12814] dial backoff\n [/ip4/103.120.228.37/tcp/12814] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-08-01T20:42:03.948+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-08-01T20:44:08.876+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/10.100.248.104/tcp/12814] dial backoff\n [/ip4/43.255.52.212/tcp/12814] dial backoff\n [/ip4/103.120.228.37/tcp/12814] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-08-01T20:44:08.876+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-08-01T20:46:27.266+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/103.120.228.37/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e103.120.228.37:12814: i/o timeout\n [/ip4/10.100.248.104/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e10.100.248.104:12814: i/o timeout\n [/ip4/43.255.52.212/tcp/12814] dial tcp4 212.6.53.183:64532-\u003e43.255.52.212:12814: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-08-01T20:46:27.266+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-08-01T20:47:44.101+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 12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp:\n [/ip4/10.100.248.104/tcp/12814] dial backoff\n [/ip4/43.255.52.212/tcp/12814] dial backoff\n * [/ip4/103.120.228.37/tcp/12814] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02189999\",\"MinerPeer\":{\"Address\":\"f02189999\",\"ID\":\"12D3KooWHrZETgYzQRs1Mx5mibAnnp4eARZV69pNGG7jXDeoqtpp\",\"PieceCID\":null}}"} 2023-08-01T20:47:44.101+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"'

rror: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' ERROR: RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"'

2023-08-05T18:12:32.134+0200 WARN rpc go-jsonrpc@v0.3.1/client.go:615 unmarshaling failed {"message": "{\"Err\":\"stream reset\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f02309112\",\"MinerPeer\":{\"Address\":\"f02309112\",\"ID\":\"12D3KooWKebAQfRGckoFFM4MboJAe2i94iBjacoE9BWiwj5Pdqgs\",\"PieceCID\":null}}"} 2023-08-05T18:12:32.134+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Recv 0 B, Paid 0 FIL, Open (New), 3ms [1691224441483171965|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 162ms [1691224441483171965|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 56.077s [1691224441483171965|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 56.147s [1691224441483171965|0] Recv 0 B, Paid 0 FIL, DataTransferError (Erroring), 2h33m18.049s [1691224441483171965|0] Recv 0 B, Paid 0 FIL, BlockstoreFinalized (Errored), 2h33m18.06s [1691224441483171965|0] ERROR: Retrieval Error: error generated by data transfer: deal data transfer failed: 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWKebAQfRGckoFFM4MboJAe2i94iBjacoE9BWiwj5Pdqgs-1691224441467119457: after 4 consecutive restarts failed to transfer any data

Recv 0 B, Paid 0 FIL, Open (New), 1ms [1691497513256515380|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 32ms [1691497513256515380|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 706ms [1691497513256515380|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 721ms [1691497513256515380|0] Recv 24.78 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 28.415s [1691497513256515380|25378]RRecv 233.3 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 22m42.318s [1691497513256515380|238926] Recv 233.9 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 23m28.556s [1691497513256515380|239535] Recv 233.9 KiB, Paid 0 FIL, DataTransferError (Erroring), 7h26m38.668s [1691497513256515380|239535] Recv 233.9 KiB, Paid 0 FIL, BlockstoreFinalized (Errored), 7h26m38.966s [1691497513256515380|239535] ERROR: Retrieval Error: error generated by data transfer: deal data transfer failed: 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWKebAQfRGckoFFM4MboJAe2i94iBjacoE9BWiwj5Pdqgs-1691497513254960627: after 4 consecutive restarts failed to transfer any data

sh": could not load link "bafkreicnetolt2de6ehrwc4zwtasaqos3t36fmbalbiwtmqvlroqrjvuua": expected link (bafkreicnetolt2de6ehrwc4zwtasaqos3t36fmbalbiwtmqvlroqrjvuua) at path Links/0/Hash does not match link sent by remote (bafybeigvj7sgk7hjp3j3d4kytlggj72l5dytnhygdko5i2xb3zwbbx4py4), possible malicious responder

Recv 0 B, Paid 0 FIL, Open (New), 3m7.113s [1691497513256515735|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3m7.178s [1691497513256515735|0] Recv 0 B, Paid 0 FIL, DataTransferError (Erroring), 13h34m4.622s [1691497513256515735|0] Recv 0 B, Paid 0 FIL, BlockstoreFinalized (Errored), 13h34m4.636s [1691497513256515735|0] ERROR: Recv 0 B, Paid 0 FIL, DealRejected (Rejecting), 13h34m23.869s [1691497513256515734|0] Recv 0 B, Paid 0 FIL, BlockstoreFinalized (Rejected), 13h34m23.92s [1691497513256515734|0] ERROR: Retrieval Proposal Rejected: deal rejected: rejected for unknown reasons

ata

Recv 0 B, Paid 0 FIL, Open (New), 0s [1692607139086044721|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 24ms [1692607139086044721|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 1.461s [1692607139086044721|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 1.469s [1692607139086044721|0]RRecv 22.77 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.08s [1692607139086044721|23312] Recv 34.98 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.089s [1692607139086044721|35817] Recv 219.3 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.548s [1692607139086044721|224601] Recv 510.8 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.558s [1692607139086044721|523062] Recv 514.7 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.567s [1692607139086044721|527072] Recv 1.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.031s [1692607139086044721|1575648] Recv 2.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.512s [1692607139086044721|2624224] Recv 3.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.756s [1692607139086044721|3672800] Recv 4.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 19.898s [1692607139086044721|4721376] Recv 5.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 20.347s [1692607139086044721|5769952] Recv 6.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 21.306s [1692607139086044721|6818528] Recv 7.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 21.78s [1692607139086044721|7867104] Recv 8.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 22.275s [1692607139086044721|8915680] Recv 9.503 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 22.52s [1692607139086044721|9964256] Recv 9.552 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m24.019s [1692607139086044721|10256381324] Recv 9.553 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m24.263s [1692607139086044721|10257429900] Recv 9.554 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m25.481s [1692607139086044721|10258478476] Recv 9.555 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m30.057s [1692607139086044721|10259527052] Recv 9.556 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m31.71s [1692607139086044721|10260575628] Recv 9.557 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m32.439s [1692607139086044721|10261624204] Recv 9.558 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m33.394s [1692607139086044721|10262672780] Recv 9.559 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m34.345s [1692607139086044721|10263721356] Recv 9.56 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m35.298s [1692607139086044721|10264769932] Recv 9.561 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m36.257s [1692607139086044721|10265818508] Recv 9.562 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m37.726s [1692607139086044721|10266867084] Recv 9.562 GiB, Paid 0 FIL, DataTransferError (Erroring), 3h14m19.794s [1692607139086044721|10266867084] Recv 9.562 GiB, Paid 0 FIL, BlockstoreFinalized (Errored), 3h14m19.868s [1692607139086044721|10266867084] ERROR: Retrieval Error: error generated by data transfer: deal data transfer failed: data transfer channel 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWKebAQfRGckoFFM4MboJAe2i94iBjacoE9BWiwj5Pdqgs-1692607139083204651 failed to transfer data: channel 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWKebAQfRGckoFFM4MboJAe2i94iBjacoE9BWiwj5Pdqgs-1692607139083204651: graphsync request failed to complete: error traversing node at "Links/204/Hash/Links/78/Hash": could not load link "bafkreic45sx2a627cz53kbdxqun2h6sbwpectopepk3lltqxlwxsf652e4": expected link (bafybeibm5kdtwyp6sxrrx4yk3uxqlv5mzdagxjlvmjarg2fp6sjgvoqq5i) at path does not match link sent by remote (bafkreiatwauohxjlsprbr2yxjmswzz74whyly7ceumktx2yptmfsdtlnda), possible malicious responder

8s [1692607139086044720|10279449996] Recv 9.574 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m23.776s [1692607139086044720|10280498572] Recv 9.575 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m24.745s [1692607139086044720|10281547148] Recv 9.576 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m25.006s [1692607139086044720|10282595724] Recv 9.577 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m29.528s [1692607139086044720|10283644300] Recv 9.578 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m30.785s [1692607139086044720|10284692876] Recv 9.579 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m32.212s [1692607139086044720|10285741452] Recv 9.58 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m33.161s [1692607139086044720|10286790028] Recv 9.581 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m34.129s [1692607139086044720|10287838604] Recv 9.582 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m35.077s [1692607139086044720|10288887180] Recv 9.583 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m36.045s [1692607139086044720|10289935756] Recv 9.584 GiB, Paid 0 FIL, BlocksReceived (Ongoing), 2h59m38.196s [1692607139086044720|10290984332] Recv 9.584 GiB, Paid 0 FIL, DataTransferError (Erroring), 3h14m17.484s [1692607139086044720|10290984332] Recv 9.584 GiB, Paid 0 FIL, BlockstoreFinalized (Errored), 3h14m17.532s [1692607139086044720|10290984332] ERROR: Retrieval Error: error generated by data transfer: deal data transfer failed: data transfer channel 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWKebAQfRGckoFFM4MboJAe2i94iBjacoE9BWiwj5Pdqgs-1692607139083204650 failed to transfer data: channel 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW-12D3KooWKebAQfRGckoFFM4MboJAe2i94iBjacoE9BWiwj5Pdqgs-1692607139083204650: graphsync request failed to complete: error traversing node at "Links/204/Hash/Links/101/Hash": could not load link "bafkreiezcpgguvllukdif6d7mpogq4rfjfwdxpd4yvkzdrafvngzsx4rxu": expected link (bafybeibm5kdtwyp6sxrrx4yk3uxqlv5mzdagxjlvmjarg2fp6sjgvoqq5i) at path does not match link sent by remote (bafkreifryfsgodcpavnnnr6jyfjzktianclkf6okg2jqshzu56tzszlxw4), possible malicious responder

When can we expect the first transfer to be working 100% so we can do due diligence on your data?

AohuanTec commented 1 year ago

@cryptowhizzard It seems that the network is unstable. I suggest switching the network or selecting a more stable SP to download data.

cryptowhizzard commented 1 year ago

Dear AohuanTec,

As notary I am doing due diligence on your LDN. I could not get retrieval to work. Can you please upload the car file of CID baga6ea4seaqi7rnfsvtq7suk24cci57rioz5o6ntkpnlj4tcz4l3yprnj63s4gi ?

You can use our upload system at http://send.datasetcreators.com. Please select 7 days for the system to keep the file and post the link you received here so I (and other notaries) can download your content.

AohuanTec commented 1 year ago

@cryptowhizzard I have tried uploading data via http://send.datasetcreators.com/ several times, but I get an interruption error after 50% of the transfer. However, I uploaded the data to baidu cloud, and the data will be kept for 30 days. https://pan.baidu.com/s/1I7HGhEfZyeJ9rNzAsdwzcA?pwd=0adm

cryptowhizzard commented 1 year ago

Sorry, i can't get that to work here unfortunately :(

I have tried some new retrievals , perhaps it works this time.

large-datacap-requests[bot] commented 1 year ago

DataCap Allocation requested

Request number 5

Multisig Notary address

f02049625

Client address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

DataCap allocation requested

400TiB

Id

c722d8f2-f82d-4929-89b5-2ee5fe8f6d3a

large-datacap-requests[bot] commented 1 year ago

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Rule to calculate the allocation request amount

400% of weekly dc amount requested

DataCap allocation requested

400TiB

Total DataCap granted for client so far

3.6379788070917166e+34YiB

Datacap to be granted to reach the total amount requested by the client (3PiB)

3.6379788070917166e+34YiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
8484 4 400TiB 47.15 102.93TiB
AlanGreaterheat commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

⚠️ 1 storage providers have unknown IP location - f02222321

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^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> ...

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

AlanGreaterheat commented 1 year ago

The retrievals looks improved, please note the IP location of f02222321 ！

AohuanTec commented 1 year ago

Okay, I will contact the SP immediately to solve this problem. It should be solved soon.

AohuanTec commented 1 year ago 
$ lotus net connect f02222321
f02222321 -> {12D3KooWQNChzv4PTL7ZAhj1KAJabUt2Q3YAKmuU5hpinY4JAw7E: [/ip4/[119.36.32.147/tcp/12844](http://119.36.32.147/tcp/12844)]}

@AlanGreaterheat public IP works

AlanGreaterheat commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedzlppe4l67kzdwjj526gcrgqsmhsdcu7klrt5iuspf3xibnqm2vo

Address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Datacap Allocated

400.00TiB

Signer Address

f1pnmzlxj7cfeo2v6oj5nco46hkg2l46wj7o4xxui

Id

c722d8f2-f82d-4929-89b5-2ee5fe8f6d3a

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedzlppe4l67kzdwjj526gcrgqsmhsdcu7klrt5iuspf3xibnqm2vo

liyunzhi-666 commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^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> ...

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

liyunzhi-666 commented 1 year ago

@AohuanTec Retrieval success rate is a bit low, but in conjunction with previous reports the success rate is gradually improving, please contact SP to continue to improve the retrieval success rate. I can support this round.

liyunzhi-666 commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebr5izpifzey7244pmmhuvgaxvlfjmex4wvxolkavzmovlc5leupw

Address

f1g3pn5gkliwaoeatenmqzfzbqiys6ntyb4sbqfnq

Datacap Allocated

400.00TiB

Signer Address

f1pszcrsciyixyuxxukkvtazcokexbn54amf7gvoq

Id

c722d8f2-f82d-4929-89b5-2ee5fe8f6d3a

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebr5izpifzey7244pmmhuvgaxvlfjmex4wvxolkavzmovlc5leupw

cryptowhizzard commented 1 year ago

Dear AohuanTec,

As notary I am doing due diligence on your LDN. I could not get retrieval to work. Can you please upload the car file of CID baga6ea4seaqhajxwpuzyaxssce7xjovisvclxovipduy2akfi54nisoiojxcoma ?

You can use our upload system at http://send.datasetcreators.com. Please select 7 days for the system to keep the file and post the link you received here so I (and other notaries) can download your content.

AohuanTec commented 1 year ago

@cryptowhizzard image It`s done last week

AohuanTec commented 1 year ago

checker:manualTrigger

filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^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> ...

Full report

Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.

cryptowhizzard commented 1 year ago

Retrieval seems working now.

http://www.datasetcreators.com/downloadedcarfiles/940-f01914993-f02195555-54258884-baga6ea4seaqe46wobgbc7yk7ingb3jtdf5fculvf4okbzlibcc76vhdrbakuuea