[DataCap Application] Shenzhen Liberty City Culture Media Co., Ltd.

[001can]

Data Owner Name

Shenzhen Liberty City Culture Media Co., Ltd.

Data Owner Country/Region

China

Data Owner Industry

Information, Media & Telecommunications

Website

http://www.whballoon.com/

Social Media

http://www.whballoon.com/

Total amount of DataCap being requested

5PiB

Weekly allocation of DataCap requested

500TiB

On-chain address for first allocation

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Custom multisig

• [ ] Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

Liberty City Culture Media Co., Ltd. is a cultural product provider with market insight as the starting point, value communication as the core, and unique creativity as the main competitiveness.
Focusing on video shooting and production, it covers brand commercials, product commercials, corporate promotional videos and other types.

Is this project associated with other projects/ecosystem stakeholders?

No

If answered yes, what are the other projects/ecosystem stakeholders

No response

Describe the data being stored onto Filecoin

Various types of original materials such as brand commercials, product commercials, corporate promotional videos, etc.

Where was the data currently stored in this dataset sourced from

My Own Storage Infra

If you answered "Other" in the previous question, enter the details here

No response

How do you plan to prepare the dataset

IPFS, lotus

If you answered "other/custom tool" in the previous question, enter the details here

No response

Please share a sample of the data

https://www.aliyundrive.com/s/SnnuBDbrnYA
https://www.aliyundrive.com/s/9UD9jQN56c9
https://www.aliyundrive.com/s/T2xdLn9NsK5

Confirm that this is a public dataset that can be retrieved by anyone on the Network

• [X] I confirm

If you chose not to confirm, what was the reason

No response

What is the expected retrieval frequency for this data

Yearly

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

More than 3 years

In which geographies do you plan on making storage deals

Greater China, Asia other than Greater China

How will you be distributing your data to storage providers

HTTP or FTP server, Shipping hard drives

How do you plan to choose storage providers

Slack

If you answered "Others" in the previous question, what is the tool or platform you plan to use

No response

If you already have a list of storage providers to work with, fill out their names and provider IDs below

No response

How do you plan to make deals to your storage providers

Lotus client

If you answered "Others/custom tool" in the previous question, enter the details here

No response

Can you confirm that you will follow the Fil+ guideline

Yes

[zcfil]

Hi @001can I looked at the new data sample.

How will you allocate this data, which cities do you plan to store data in, and which data storage vendors do you currently have with you.

I look forward to hearing from you.

[001can]

Of course, most of the data is stored on the original server, here are some screenshots.

[001can]

Hi @001can I looked at the new data sample.

How will you allocate this data, which cities do you plan to store data in, and which data storage vendors do you currently have with you.

I look forward to hearing from you.

We want to store more than 5 copies. Plan to store data in Greater China, Asia other than Greater China We have a list of SPs we have contacted here: f01859603 f01938671 f01900537 f01928022 f01927554 f02036170

[a1991car]

Can you email filplus-app-review@fil.org using your official domain name to confirm your identity?Email name should contain Issue ID #1495.

[001can]

Hi, we just send the email to filplus-app-review@fil.org, plz check. Thanks you, have a nice day.

[a1991car]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacecm4nu3bs3ivh7gdy7h57phm237xfq2u5ypb7jhfasa22hqxbvqhg

Address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Datacap Allocated

250.00TiB

Signer Address

f1qnumecdypgrbaebtkdfjnwt5ndacadcuas3deiq

Id

503b4627-102e-4591-a204-4c44a0ed4c5a

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

[zcfil]

@galen-mcandrew @raghavrmadya @Kevin-FF-USA Because my hardware wallet has not been updated to the multi signature address f02049625 for a long time, my signature using the lotus command did not trigger the following robot message reply. I mentioned it to RG before, but it still hasn't been resolved. I'm confused

Request Approve

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacealntbwrtsd2vvcuwlhiz7cg4jyx2azn2hz3smdsdcrmppdz2o73s

Address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Datacap Allocated

250.00TiB

Signer Address

f17xummecmkqgjhm4fesktesaieumn7ugarwucwty

Id

none

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

[maxvint]

checker:manualTrigger

[filplus-checker-app[bot]]

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.

[woshidama323]

checker:manualTrigger

[filplus-checker-app[bot]]

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.

[woshidama323]

Looks good

[woshidama323]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedwdemoqbj5nmgfq4ta4u6zwoshqcrw6vszzvzghljkmxrpgf4glm

Address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Datacap Allocated

250.00TiB

Signer Address

f12tk3adljauwnd3hjbigpfxb7b7gdlj63p6afwtq

Id

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

[maxvint]

Data distribution looks good, and check all the boxes, retrieval also works very well, willing to support.

[maxvint]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacec3fmp63bxgncp5te3ebqrt2odaoxrh7j23hoocfgbe4vozl7eje6

Address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Datacap Allocated

250.00TiB

Signer Address

f1ui5iy4mmkxjbw7752omiwp2ols2fzv4thrayagi

Id

503b4627-102e-4591-a204-4c44a0ed4c5a

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

[large-datacap-requests[bot]]

DataCap Allocation requested

Request number 3

Multisig Notary address

f02049625

Client address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

DataCap allocation requested

1000.0TiB

Id

81c43253-575d-4262-b6b7-c1aef75c7744

[large-datacap-requests[bot]]

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Rule to calculate the allocation request amount

200% of weekly dc amount requested

DataCap allocation requested

1000.0TiB

Total DataCap granted for client so far

227373.7YiB

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

-2.74B

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
12927	5	250TiB	50.48	70.81TiB

[sxxfuture-official]

checker:manualTrigger

[filplus-checker-app[bot]]

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.

[sxxfuture-official]

CID-Checker shows everything well and the data retrieve testing result as follows:

@001can Next round sealing, you should add more SPs into this project, 3 SP will not enougth .

[sxxfuture-official]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedmhkmlebrdwk54vzrctmhivizfsfzvbh4dhbifnnrvil6qwu2vno

Address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Datacap Allocated

1000.00TiB

Signer Address

f1foiomqlmoshpuxm6aie4xysffqezkjnokgwcecq

Id

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

[newwebgroup]

checker:manualTrigger

[filplus-checker-app[bot]]

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.

[newwebgroup]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceb3riuhaky4qq265iuwx5kn5yjs4d7qnjfhp7ms36j5ujp5is3okq

Address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Datacap Allocated

1000.00TiB

Signer Address

f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq

Id

81c43253-575d-4262-b6b7-c1aef75c7744

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

[github-actions[bot]]

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.

[001can]

please keep it open

[cryptowhizzard]

Hello,

It seems that some of your SP's went offline. Can you bring them online again to enable retrieval?

cat 1495-f02100670-f01738789-43761618-baga6ea4seaqdi5dywmr2wrsieo3ywsy2eqf4o46zqzbuifnyas7d4fn3mqmmafy.log 2023-07-26T22:53:49.472+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01738789\",\"MinerPeer\":{\"Address\":\"f01738789\",\"ID\":\"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq\",\"PieceCID\":null}}"} 2023-07-26T22:53:49.473+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-26T22:55:57.625+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01738789\",\"MinerPeer\":{\"Address\":\"f01738789\",\"ID\":\"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq\",\"PieceCID\":null}}"} 2023-07-26T22:55:57.626+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-26T22:58:06.147+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01738789\",\"MinerPeer\":{\"Address\":\"f01738789\",\"ID\":\"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq\",\"PieceCID\":null}}"} 2023-07-26T22:58:06.147+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-26T23:00:30.827+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01738789\",\"MinerPeer\":{\"Address\":\"f01738789\",\"ID\":\"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq\",\"PieceCID\":null}}"} 2023-07-26T23:00:30.828+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-26T23:02:25.962+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n * [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01738789\",\"MinerPeer\":{\"Address\":\"f01738789\",\"ID\":\"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq\",\"PieceCID\":null}}"} 2023-07-26T23:02:25.962+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"'

[large-datacap-requests[bot]]

DataCap Allocation requested

Request number 4

Multisig Notary address

f02049625

Client address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

DataCap allocation requested

1.95PiB

Id

dfa8fc7e-d016-40d7-a2b0-b263f1d6788a

[large-datacap-requests[bot]]

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Rule to calculate the allocation request amount

400% of weekly dc amount requested

DataCap allocation requested

1.95PiB

Total DataCap granted for client so far

909494701772928450560.0YiB

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

909494701772928450560.0YiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
39526	11	1000.0TiB	16.51	264TiB

[001can]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

• Overall Graphsync retrieval success rate: 25.77%
• Overall HTTP retrieval success rate: 0.00%
• Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

⚠️ 56.02% of deals are for data replicated across less than 4 storage providers.

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.

[001can]

Hello,

It seems that some of your SP's went offline. Can you bring them online again to enable retrieval?

cat 1495-f02100670-f01738789-43761618-baga6ea4seaqdi5dywmr2wrsieo3ywsy2eqf4o46zqzbuifnyas7d4fn3mqmmafy.log 2023-07-26T22:53:49.472+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused","Root":null,"Piece":null,"Size":0,"MinPrice":"\u003cnil\u003e","UnsealPrice":"\u003cnil\u003e","PricePerByte":"\u003cnil\u003e","PaymentInterval":0,"PaymentIntervalIncrease":0,"Miner":"f01738789","MinerPeer":{"Address":"f01738789","ID":"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq","PieceCID":null}}"} 2023-07-26T22:53:49.473+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-26T22:55:57.625+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused","Root":null,"Piece":null,"Size":0,"MinPrice":"\u003cnil\u003e","UnsealPrice":"\u003cnil\u003e","PricePerByte":"\u003cnil\u003e","PaymentInterval":0,"PaymentIntervalIncrease":0,"Miner":"f01738789","MinerPeer":{"Address":"f01738789","ID":"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq","PieceCID":null}}"} 2023-07-26T22:55:57.626+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-26T22:58:06.147+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused","Root":null,"Piece":null,"Size":0,"MinPrice":"\u003cnil\u003e","UnsealPrice":"\u003cnil\u003e","PricePerByte":"\u003cnil\u003e","PaymentInterval":0,"PaymentIntervalIncrease":0,"Miner":"f01738789","MinerPeer":{"Address":"f01738789","ID":"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq","PieceCID":null}}"} 2023-07-26T22:58:06.147+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-26T23:00:30.827+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused","Root":null,"Piece":null,"Size":0,"MinPrice":"\u003cnil\u003e","UnsealPrice":"\u003cnil\u003e","PricePerByte":"\u003cnil\u003e","PaymentInterval":0,"PaymentIntervalIncrease":0,"Miner":"f01738789","MinerPeer":{"Address":"f01738789","ID":"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq","PieceCID":null}}"} 2023-07-26T23:00:30.828+0200 INFO retry retry/retry.go:17 Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' 2023-07-26T23:02:25.962+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 12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq:\n * [/ip4/160.86.241.170/tcp/18140] dial tcp4 160.86.241.170:18140: connect: connection refused","Root":null,"Piece":null,"Size":0,"MinPrice":"\u003cnil\u003e","UnsealPrice":"\u003cnil\u003e","PricePerByte":"\u003cnil\u003e","PaymentInterval":0,"PaymentIntervalIncrease":0,"Miner":"f01738789","MinerPeer":{"Address":"f01738789","ID":"12D3KooWHPD3nMavfuVZsn7de9FNBGCfottBQLFMEqpJxoewTScq","PieceCID":null}}"} 2023-07-26T23:02:25.962+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"'

Thank you very much for your attention. In response to your doubts, my reply is as follows

1. The CID checker report shows that our retrieval rate is normal
2. Is it possible that there is a network problem on your side?

[ipollo00]

Since the last tranche now is 3 months ago, even though the report has a warning on data replication, the number of backups has significantly increased, which is acceptable to me. However, Strongly suggest your sps can widely accept HTTP retrieval. I will keep following up on this form.

[ipollo00]

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaced5jp7mp7jotbh7i4u4yandfvokwoissu4k6haveqxe74msmy6pac

Address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Datacap Allocated

1.95PiB

Signer Address

f1n5wlrrhoxpkgwij25xrtt7w7g2k3fhbthmdn6ri

Id

dfa8fc7e-d016-40d7-a2b0-b263f1d6788a

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

[METAVERSEDATAMINING]

Data can be retrieved.

56.02% of deals are for data replicated across less than 4 storage providers.

@001can This round of data backup needs to be significantly improved.I'll sign this round

[METAVERSEDATAMINING]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecuxpmepoq46u477wghckku726wim6ulwzjhlcv3mhxd4ijd77t5a

Address

f1mrqexd4z6oxrvzeuthlf4n2jf6m64abonhhchya

Datacap Allocated

1.95PiB

Signer Address

f17idrnfnxl2mbgcgr57a6z2c6lj2qx56gvm3336i

Id

dfa8fc7e-d016-40d7-a2b0-b263f1d6788a

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

[001can]

checker:manualTrigger

[filplus-checker-app[bot]]

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

• Overall Graphsync retrieval success rate: 23.41%
• Overall HTTP retrieval success rate: 0.00%
• Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

⚠️ 52.72% of deals are for data replicated across less than 4 storage providers.

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]

I have downloaded some of the data available and unpacked here:

http://www.datasetcreators.com/downloadedcarfiles/1495-f02100670-f01261218-49563095-baga6ea4seaqhx2aqnrlpuchiz3xsqjhhjcvpzbhvw7rpqgpph5u2a4gkuisrmay

Seems to me you are not storing the data that you were telling us you were going to store.

[Carohere]

@001can Could you confirm this file? http://www.datasetcreators.com/downloadedcarfiles/1495-f02100670-f01261218-49563095-baga6ea4seaqhx2aqnrlpuchiz3xsqjhhjcvpzbhvw7rpqgpph5u2a4gkuisrmay

[raghavrmadya]

https://www.notion.so/filecoin/Applicant-not-storing-the-data-promised-4defffb5a564422494af9f68463e8a57?pvs=4

[001can]

Our technical team is contacting SP to inquire about the specific situation, please give us a little time, and we will find out the situation as soon as possible.

[001can]

@cryptowhizzard @Carohere @raghavrmadya Sorry for the late reply The stored data is mainly distributed to different SPs by transporting hard disks. Currently, we have found that employees with SPs are lazy, so they replaced the data. They did not store according to the original plan. The employees with problems have left and we are communicating with SPs. How to deal with it and see if there is a way to fix it.

[raghavrmadya]

As client has confirmed non-compliance with the Fil+ guidelines, all DC must be removed from this client's wallet.

The involved SP IDs have been blacklisted as client has flagged negligent behavior on the part of the SPs.