search

filecoin-project / filecoin-plus-large-datasets

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

[DataCap Application] F3 #925

Closed xxcisco closed 1 year ago

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

Headquartered in Singapore, F3 is a computing power NFT trading platform. It is committed to providing global users with more unique, more valuable, and long-term circulating computing power NFTs. With the concept of "openness, fairness and transparency", F3 is committed to becoming a The world's first computing power NFT trading platform that uses smart contracts to issue income.

Every NFT on the F3 platform is permanently anchored to the FIL cloud computing power. When users buy NFT, they can enjoy the continuous income of Filecoin computing power, which can completely break the current deadlock of low value support and low liquidity of NFT. The core value of NFT will be closely related to the fluctuation of FIL price. At the same time, NFT can be placed on opensea, X2Y2 and other trading platforms for circulation and trading.

After the launch of FVM, all NFT products on the F3 platform will be settled in FIL, making it the world's largest NFT trading platform based on FIL settlement. At the same time, we will open source our code and participate in hackathons.

F3's Twitter followers are as high as 28,000, and many of our Twitters have been liked and forwarded from Filecoin's official Twitter.

What is the primary source of funding for this project?

The founder of F3 owns a lot of BTC\ETH\FIL\usdt, etc., the economic strength is strong.

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

F3 is an emerging NFT trading platform that is independent. We hope that more NFT creators can join F3 and attract the fan economy from creators.

Use-case details

Describe the data being stored onto Filecoin

F3's development data/development log/development code, etc., F3's promotional videos, F3's Twitter, Medium and other social media content, F3's pictures/videos of major conferences or conferences.

Where was the data in this dataset sourced from?

The data comes from the F3 platform

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

https://drive.google.com/drive/folders/1I-rYUeOFQ7jiN93c8E8QdCLpy-QtbmzT
https://drive.google.com/drive/folders/1_NmdoCGdZdj8QPr6rZfaoYhZ8-fMLCgR
https://drive.google.com/drive/u/0/folders/14atygDT32Vmudj3rrdDgFY5ElxB6OPli
https://drive.google.com/drive/folders/1CJCkVUEygG3pPHM45oqO-SnecBUn1YiU
https://drive.google.com/drive/folders/17WFRF3WkRrbtmeGnQB2a2-AZ7Kqv6BOz
https://drive.google.com/drive/u/0/folders/183slc_i8HOPxnU1JnP8gBrermPoTMD5U

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

Confirm

What is the expected retrieval frequency for this data?

This is our backup data, expected to be retrieved every 12 months.

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

about 36 months

DataCap allocation plan

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

We plan to store data in Vietnam, Singapore, USA, etc.

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

We do not have a clear limit. We think that if it is small data, it will be transmitted online. If it is large data, consider offline hard disk transmission.

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 will look for SPs through slack and filfox. We believe that policies (the country where the SP is located), technology, etc. all affect our choice of SP. We tend to choose SPs in Singapore and the United States. We plan to search once a year, and we ask about their search capabilities when selecting SPs.

How will you be distributing deals across storage providers?

We will strictly abide by the rules of FIL+ to achieve decentralized storage. We promise that there will be at least 4 SP IDs, and each SP ID will not exceed 25%.

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, I do
large-datacap-requests[bot] commented 2 years 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.

xxcisco commented 2 years ago

497

raghavrmadya commented 2 years ago

Datacap Request Trigger

Total DataCap requested

2PiB

Expected weekly DataCap usage rate

60TiB

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

large-datacap-requests[bot] commented 2 years ago

DataCap Allocation requested

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

DataCap allocation requested

30TiB

stcloudlisa commented 2 years ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceakskcsitwkapow6zryjksyiypqeueqzmrtcvwwgwakwhbqtz5mca

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

30.00TiB

Signer Address

f1jvvltduw35u6inn5tr4nfualyd42bh3vjtylgci

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

Joss-Hua commented 2 years ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacedxqli374uictibbn2ml4loqbj4qo4t36dgise3zjmhztt4wj26xa

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

30.00TiB

Signer Address

f1tfg54zzscugttejv336vivknmsnzzmyudp3t7wi

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

BDE-io commented 2 years ago

@xxcisco Hi! Great to see you have gotten approval for DataCap. If you are looking for more storage providers to store these data or have any questions, please visit #bigdata-exchange on Filecoin Slack or reply here.

We have strong demand from a diverse group of SPs, who are actively looking to onboard more data.

large-datacap-requests[bot] commented 2 years ago

DataCap Allocation requested

Request number 2

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

DataCap allocation requested

60TiB

large-datacap-requests[bot] commented 2 years ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Last two approvers

Joss-Hua & 1LISA2

Rule to calculate the allocation request amount

100% of weekly dc amount requested

DataCap allocation requested

60TiB

Total DataCap granted for client so far

30TiB

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

1.97PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
607 5 30TiB 21.25 0B
psh0691 commented 2 years ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedszi4jf7kz4s34ol7pg67chqxwu65ht7k7qhbrpkhsba7bqb7hoc

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

60.00TiB

Signer Address

f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i

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

liyunzhi-666 commented 2 years ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceafwbdtdcb3pblehxszdq366cqfkkymn5lfewhzl7coomkzttk33s

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

60.00TiB

Signer Address

f1pszcrsciyixyuxxukkvtazcokexbn54amf7gvoq

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

large-datacap-requests[bot] commented 2 years ago

DataCap Allocation requested

Request number 3

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

DataCap allocation requested

120TiB

large-datacap-requests[bot] commented 2 years ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Last two approvers

liyunzhi-666 & psh0691

Rule to calculate the allocation request amount

200% of weekly dc amount requested

DataCap allocation requested

120TiB

Total DataCap granted for client so far

90TiB

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

1.91PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
1792 5 60TiB 20.81 2.46TiB
kernelogic commented 2 years ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacea5fhz66i34hqw3ogqrumrfygu7paxrbe4didzggojtocxxth3see

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

120.00TiB

Signer Address

f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa

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

cryptowhizzard commented 2 years ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceaioux4voa2nu7n2t2lbv5scivy3i4rv4iz3pr2gsdjmfwduqdizc

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

120.00TiB

Signer Address

f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa

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

large-datacap-requests[bot] commented 2 years ago

DataCap Allocation requested

Request number 4

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

DataCap allocation requested

240TiB

large-datacap-requests[bot] commented 2 years ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Last two approvers

cryptowhizzard & kernelogic

Rule to calculate the allocation request amount

400% of weekly dc amount requested

DataCap allocation requested

240TiB

Total DataCap granted for client so far

210TiB

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

1.79PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
4541 5 120TiB 20.88 22.71TiB
Joss-Hua commented 2 years ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceafjrwiil63lmvvwv5sjsxtjxvoor4tbn3z3k3ktva5k2n5a5klbi

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

240.00TiB

Signer Address

f1tfg54zzscugttejv336vivknmsnzzmyudp3t7wi

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

1ane-1 commented 2 years ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceamaxyooxbb5cx5hia5h37i2vcgsplf7k76a7p6ahpwj44htebh66

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

240.00TiB

Signer Address

f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri

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

raghavrmadya commented 2 years ago

The data samples have disappeared. Please pause future allocations until the client provides a justification and uploads samples

xxcisco commented 2 years ago

I accidentally deleted some folders when I was cleaning up my google drive space, and I have now restored them.

xxcisco commented 2 years ago

@raghavrmadya @Kevin-FF-USA can we have some updates here since we already restored?

large-datacap-requests[bot] commented 2 years ago

DataCap Allocation requested

Request number 5

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

DataCap allocation requested

480TiB

large-datacap-requests[bot] commented 2 years ago

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Last two approvers

1ane-1 & Joss-Hua

Rule to calculate the allocation request amount

800% of weekly dc amount requested

DataCap allocation requested

480TiB

Total DataCap granted for client so far

450TiB

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

1.56PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
14325 5 240TiB 20.03 2.34TiB
Tom-OriginStorage commented 2 years ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedvicfcoy7zgsfodzxwp7v25pju3x5rp4oa4rzh27owuhbqr5bg2o

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

480.00TiB

Signer Address

f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga

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

newwebgroup commented 2 years ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebytbu4wxrgholqfey6oceadmp3u5j2r2x3us5ytcnm6g3defspzy

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

480.00TiB

Signer Address

f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq

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

filplus-checker commented 1 year ago

DataCap and CID Checker Report[^1]

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.

⚠️ 20.24% of total deal sealed by f01914123 are duplicate data.

⚠️ 20.19% of total deal sealed by f01915546 are duplicate data.

Provider Location Total Deals Sealed Percentage Unique Data Duplicate Deals
f01914123new Paripark, Seoul, KR 89.69 TiB 20.03% 71.53 TiB 20.24%
f01915546new El Colorado, Querétaro, MX 89.63 TiB 20.02% 71.53 TiB 20.19%
f01927252new Dādri, Uttar Pradesh, IN 89.53 TiB 20.00% 75.50 TiB 15.67%
f01928022new Melbourne, Victoria, AU 89.47 TiB 19.99% 75.50 TiB 15.61%
f01926792new Frankfurt am Main, Hesse, DE 89.34 TiB 19.96% 71.50 TiB 19.97%

Provider Distribution

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
3.97 TiB 7.94 TiB 2 1.77%
32.00 GiB 224.00 GiB 4 0.05%
71.50 TiB 439.50 TiB 5 98.18%

Replication Distribution

Deal Data Shared with other Clients

The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.

✔️ No CID sharing has been observed.

[^1]: To manually trigger this report, add a comment with text checker:manualTrigger

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

DataCap Allocation requested

Request number 6

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

DataCap allocation requested

480TiB

Id

97e566a2-230f-4b93-9670-5af436be30cd

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

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Last two approvers

newwebgroup & llifezou

Rule to calculate the allocation request amount

800% of weekly dc amount requested

DataCap allocation requested

480TiB

Total DataCap granted for client so far

930TiB

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

1.09PiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
25836 11 480TiB 16.94 113.05TiB
filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

✔️ Storage provider distribution looks healthy.

Provider Location Total Deals Sealed Percentage Unique Data Duplicate Deals
f01807707 Shenzhen, Guangdong, CN
China Telecom (Group)		 121.12 TiB 15.16% 121.12 TiB 0.00%
f01914123new Seoul, Seoul, KR
The Constant Company, LLC		 136.50 TiB 17.09% 118.19 TiB 13.42%
f01926792new Frankfurt am Main, Hesse, DE
The Constant Company, LLC		 136.00 TiB 17.03% 118.00 TiB 13.24%
f01927252new Delhi, Delhi, IN
The Constant Company, LLC		 135.47 TiB 16.96% 121.28 TiB 10.47%
f01915546new El Colorado, Querétaro, MX
The Constant Company, LLC		 135.41 TiB 16.95% 117.19 TiB 13.45%
f01928022new Melbourne, Victoria, AU
The Constant Company, LLC		 134.31 TiB 16.81% 120.19 TiB 10.52%

Provider Distribution

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
121.12 TiB 121.12 TiB 1 15.16%
4.63 TiB 9.25 TiB 2 1.16%
32.00 GiB 96.00 GiB 3 0.01%
2.00 TiB 8.09 TiB 4 1.01%
115.50 TiB 660.25 TiB 5 82.65%

Replication Distribution

Deal Data Shared with other Clients

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

psh0691 commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceb5g5pj6u5n4vu4rxrthgp5p3gl7czy66lccq6hzyjyep5p5hp5uw

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

480.00TiB

Signer Address

f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i

Id

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

psh0691 commented 1 year ago

You have verified that no CID shares have been observed and are being distributed to more than five nodes.

kernelogic commented 1 year ago

I was able to perform retrieval on the SP of this LDN. image

kernelogic commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecw7vx75qteykahuggh7cs5huibfycoqugotopy5mpyjwbbtjvvdo

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

480.00TiB

Signer Address

f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa

Id

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

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

DataCap Allocation requested

Request number 7

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

DataCap allocation requested

480TiB

Id

1333d66f-58ff-4788-99b7-1416766519bb

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

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Last two approvers

kernelogic & psh0691

Rule to calculate the allocation request amount

800% of weekly dc amount requested

DataCap allocation requested

480TiB

Total DataCap granted for client so far

1.37PiB

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

638TiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
38770 11 480TiB 17.92 58.28TiB
filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

✔️ Storage provider distribution looks healthy.

Provider Location Total Deals Sealed Percentage Unique Data Duplicate Deals
f01807707 Shenzhen, Guangdong, CN
China Telecom (Group)		 126.54 TiB 9.93% 126.54 TiB 0.00%
f01914123new Paripark, Seoul, KR
The Constant Company, LLC		 230.42 TiB 18.09% 207.02 TiB 10.16%
f01926792new Frankfurt am Main, Hesse, DE
The Constant Company, LLC		 230.08 TiB 18.06% 206.98 TiB 10.04%
f01927252new Dādri, Uttar Pradesh, IN
The Constant Company, LLC		 229.48 TiB 18.01% 210.20 TiB 8.40%
f01915546new El Colorado, Querétaro, MX
The Constant Company, LLC		 229.33 TiB 18.00% 206.02 TiB 10.17%
f01928022new Melbourne, Victoria, AU
The Constant Company, LLC		 228.23 TiB 17.91% 209.02 TiB 8.42%

Provider Distribution

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
126.54 TiB 126.54 TiB 1 9.93%
4.63 TiB 9.25 TiB 2 0.73%
1.81 TiB 7.34 TiB 4 0.58%
204.55 TiB 1.10 PiB 5 88.77%

Replication Distribution

Deal Data Shared with other Clients

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

stcloudlisa commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceb53isuqrohog7sh7mzjzf66s22apu774ifqsstmcpkewdulvwm4g

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

480.00TiB

Signer Address

f1jvvltduw35u6inn5tr4nfualyd42bh3vjtylgci

Id

1333d66f-58ff-4788-99b7-1416766519bb

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

stcloudlisa commented 1 year ago

Reason for signing:

  1. F3 has demonstrated at the notary conference around September 2022, which is a Filecoin-based dapp
  2. F3 can support retrieval
1ane-1 commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaced7cyxpqjdm2slw3cwzq7x6wxkntsegsh6u6ocp4rsllylq5zh5rq

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

480.00TiB

Signer Address

f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri

Id

1333d66f-58ff-4788-99b7-1416766519bb

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

1ane-1 commented 1 year ago

CID report looks ok,and i will follow this issue, hope you can have a good performance.

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

DataCap Allocation requested

Request number 8

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

DataCap allocation requested

158TiB

Id

295586e8-b455-464a-bd80-65798e81d2ad

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

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Last two approvers

1ane-1 & 1LISA2

Rule to calculate the allocation request amount

800% of weekly dc amount requested

DataCap allocation requested

158TiB

Total DataCap granted for client so far

1.37PiB

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

638TiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
42875 11 480TiB 18.12 15.16TiB
filplus-checker-app[bot] commented 1 year ago

DataCap and CID Checker Report[^1]

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

If this is the first time a provider takes verified deal, it will be marked as new.

For most of the datacap application, below restrictions should apply.

✔️ Storage provider distribution looks healthy.

Provider Location Total Deals Sealed Percentage Unique Data Duplicate Deals
f01807707 Shenzhen, Guangdong, CN
China Telecom (Group)		 126.54 TiB 9.17% 126.54 TiB 0.00%
f01926792new Frankfurt am Main, Hesse, DE
The Constant Company, LLC		 253.45 TiB 18.37% 230.36 TiB 9.11%
f01915546new El Colorado, Querétaro, MX
The Constant Company, LLC		 251.61 TiB 18.23% 228.30 TiB 9.27%
f01914123new Paripark, Seoul, KR
The Constant Company, LLC		 250.95 TiB 18.19% 227.55 TiB 9.33%
f01927252new Dādri, Uttar Pradesh, IN
The Constant Company, LLC		 249.30 TiB 18.07% 230.02 TiB 7.73%
f01928022new Melbourne, Victoria, AU
The Constant Company, LLC		 248.11 TiB 17.98% 228.89 TiB 7.75%

Provider Distribution

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

✔️ Data replication looks healthy.

Unique Data Size Total Deals Made Number of Providers Deal Percentage
126.57 TiB 126.57 TiB 1 9.17%
5.00 TiB 10.00 TiB 2 0.72%
1.84 TiB 5.53 TiB 3 0.40%
7.88 TiB 31.59 TiB 4 2.29%
219.61 TiB 1.18 PiB 5 87.41%

Replication Distribution

Deal Data Shared with other Clients

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

BlockMakeronline commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacecdaw345puat7vimy3t7a7e4qndujkjlpfn7f73vvohkdzmfwuoik

Address

f1jvsdgfwf3mo2knxwl6jlqm5oupufykd2ati6liq

Datacap Allocated

158.00TiB

Signer Address

f1o3twrcpwjtpcd4q36lpq4qmy2qfbgtyy5h6tsty

Id

295586e8-b455-464a-bd80-65798e81d2ad

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

lvschouwen commented 1 year ago

@xxcisco Could you please work with the following of your SPs to make retrieval possible?

MinerID f01915546 - Cancelling retrieval requests;

# lotus state get-deal 11956452
{
  "Proposal": {
    "PieceCID": {
      "/": "baga6ea4seaqgp37ewn3suzxxfowsk2hkzkzfdj3hcvxk7xknxvtmjhr5fgkv4pq"
    },
    "PieceSize": 34359738368,
    "VerifiedDeal": true,
    "Client": "f01917191",
    "Provider": "f01915546",
    "Label": "bafykbzacebzty4fuxftgc5cj3ot7nwpblwkuovlktfg4mc64kr7i5vc5addf4",
    "StartEpoch": 2229432,
    "EndEpoch": 3755832,
    "StoragePricePerEpoch": "0",
    "ProviderCollateral": "8614570313697177",
    "ClientCollateral": "0"
  },
  "State": {
    "SectorStartEpoch": 2216176,
    "LastUpdatedEpoch": 2579172,
    "SlashEpoch": -1,
    "VerifiedClaim": 0
  }
}
# lotus client retrieve --provider f01915546 bafykbzacebzty4fuxftgc5cj3ot7nwpblwkuovlktfg4mc64kr7i5vc5addf4 baga6ea4seaqgp37ewn3suzxxfowsk2hkzkzfdj3hcvxk7xknxvtmjhr5fgkv4pq.car
Recv 0 B, Paid 0 FIL, Open (New), 0s [1674922066658078709|0]
Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 2ms [1674922066658078709|0]
Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 425ms [1674922066658078709|0]
Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 425ms [1674922066658078709|0]
Recv 0 B, Paid 0 FIL, ProviderCancelled (Cancelling), 10.138s [1674922066658078709|0]
Recv 0 B, Paid 0 FIL, CancelComplete (Cancelled), 10.139s [1674922066658078709|0]
ERROR: Retrieval Proposal Cancelled: Provider cancelled retrieval

# lotus state get-deal 11941360
{
  "Proposal": {
    "PieceCID": {
      "/": "baga6ea4seaqeb6dugpbxowmoqh7krprbflzsqjacp3dyunhhotj6cyzze7e36ni"
    },
    "PieceSize": 34359738368,
    "VerifiedDeal": true,
    "Client": "f01917191",
    "Provider": "f01915546",
    "Label": "bafykbzacedis2rm7yzs5lrxupe2cecjf466ttvnvvcthttsybzmnfehyvhgaq",
    "StartEpoch": 2229109,
    "EndEpoch": 3755509,
    "StoragePricePerEpoch": "0",
    "ProviderCollateral": "8612229583733234",
    "ClientCollateral": "0"
  },
  "State": {
    "SectorStartEpoch": 2215470,
    "LastUpdatedEpoch": 2578480,
    "SlashEpoch": -1,
    "VerifiedClaim": 0
  }
}
# lotus client retrieve --provider f01915546 bafykbzacedis2rm7yzs5lrxupe2cecjf466ttvnvvcthttsybzmnfehyvhgaq baga6ea4seaqeb6dugpbxowmoqh7krprbflzsqjacp3dyunhhotj6cyzze7e36ni.car
Recv 0 B, Paid 0 FIL, Open (New), 0s [1674922066658078710|0]
Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 2ms [1674922066658078710|0]
Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 421ms [1674922066658078710|0]
Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 421ms [1674922066658078710|0]
Recv 0 B, Paid 0 FIL, ProviderCancelled (Cancelling), 14.599s [1674922066658078710|0]
Recv 0 B, Paid 0 FIL, CancelComplete (Cancelled), 14.6s [1674922066658078710|0]
ERROR: Retrieval Proposal Cancelled: Provider cancelled retrieval

MinerID f01927252 - Unreachable

{
  "Proposal": {
    "PieceCID": {
      "/": "baga6ea4seaqlnlrfuy6ve6auexhlwvgge3m7cfti4mgbfqn37zhxco4qtvewmey"
    },
    "PieceSize": 34359738368,
    "VerifiedDeal": true,
    "Client": "f01917191",
    "Provider": "f01927252",
    "Label": "bafykbzacebz6w53ssf3twnspp6f5ss2h7dljhau6pk2xuqhkbpuctmp5xnzwq",
    "StartEpoch": 2295431,
    "EndEpoch": 3821831,
    "StoragePricePerEpoch": "0",
    "ProviderCollateral": "9030366397000123",
    "ClientCollateral": "0"
  },
  "State": {
    "SectorStartEpoch": 2281761,
    "LastUpdatedEpoch": 2578308,
    "SlashEpoch": -1,
    "VerifiedClaim": 0
  }
}
# lotus client retrieve --provider f01926792 bafykbzaceahgae55a6lxf22ioj7pja43ubmz3wj7ommwckjprwhycigv4ezq6 baga6ea4seaqfg343rrvgw6yarfkdrf4z326j6jumil7shivy637ryxxymz7egjq.car
Recv 0 B, Paid 0 FIL, Open (New), 0s [1674922066658078708 ^C
root@R31-Core01:~# lotus client retrieve --provider f01927252 bafykbzacebz6w53ssf3twnspp6f5ss2h7dljhau6pk2xuqhkbpuctmp5xnzwq baga6ea4seaqlnlrfuy6ve6auexhlwvgge3m7cfti4mgbfqn37zhxco4qtvewmey.car
2023-02-06T15:46:48.604+0100    WARN    rpc go-jsonrpc@v0.1.8/client.go:548 unmarshaling failed {"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf:\\n  * [/ip4/139.84.166.87/tcp/24001] dial tcp4 139.84.166.87:24001: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\\u003cnil\\u003e\",\"UnsealPrice\":\"\\u003cnil\\u003e\",\"PricePerByte\":\"\\u003cnil\\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01927252\",\"MinerPeer\":{\"Address\":\"f01927252\",\"ID\":\"12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf\",\"PieceCID\":null}}"}
2023-02-06T15:46:48.604+0100    INFO    retry   retry/retry.go:17   Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"'
2023-02-06T15:48:19.188+0100    WARN    rpc go-jsonrpc@v0.1.8/client.go:548 unmarshaling failed {"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf:\\n  * [/ip4/139.84.166.87/tcp/24001] dial tcp4 139.84.166.87:24001: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\\u003cnil\\u003e\",\"UnsealPrice\":\"\\u003cnil\\u003e\",\"PricePerByte\":\"\\u003cnil\\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01927252\",\"MinerPeer\":{\"Address\":\"f01927252\",\"ID\":\"12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf\",\"PieceCID\":null}}"}
2023-02-06T15:48:19.188+0100    INFO    retry   retry/retry.go:17   Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"'

MinerID f01928022 - Cancelling retrieval requests;

# lotus state get-deal 11912549
{
  "Proposal": {
    "PieceCID": {
      "/": "baga6ea4seaqj3za5sixhu5rbltjh54b2a26vemiyvmpqdmgvbcpj4yxggcsq2oa"
    },
    "PieceSize": 34359738368,
    "VerifiedDeal": true,
    "Client": "f01917191",
    "Provider": "f01928022",
    "Label": "bafykbzaceaaju2rtgvkut3ozrd74kabmwqukwa4mgf4wywl77iptwenihojdm",
    "StartEpoch": 2228377,
    "EndEpoch": 3754777,
    "StoragePricePerEpoch": "0",
    "ProviderCollateral": "8609842554379632",
    "ClientCollateral": "0"
  },
  "State": {
    "SectorStartEpoch": 2214858,
    "LastUpdatedEpoch": 2578469,
    "SlashEpoch": -1,
    "VerifiedClaim": 0
  }
}
# lotus client retrieve --provider f01928022 bafykbzaceaaju2rtgvkut3ozrd74kabmwqukwa4mgf4wywl77iptwenihojdm baga6ea4seaqj3za5sixhu5rbltjh54b2a26vemiyvmpqdmgvbcpj4yxggcsq2oa.car
Recv 0 B, Paid 0 FIL, Open (New), 0s [1674922066658078711|0]
Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 2ms [1674922066658078711|0]
Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 811ms [1674922066658078711|0]
Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 812ms [1674922066658078711|0]
Recv 0 B, Paid 0 FIL, ProviderCancelled (Cancelling), 7.361s [1674922066658078711|0]
Recv 0 B, Paid 0 FIL, CancelComplete (Cancelled), 7.361s [1674922066658078711|0]
ERROR: Retrieval Proposal Cancelled: Provider cancelled retrieval

MinerID f01914123 - Cancelling retrieval request;

# lotus state get-deal 11911722
{
  "Proposal": {
    "PieceCID": {
      "/": "baga6ea4seaqjumdku2dza7rhz3expwxoljwmmlwnl6g3pbfwuhklfbosklbosfy"
    },
    "PieceSize": 34359738368,
    "VerifiedDeal": true,
    "Client": "f01917191",
    "Provider": "f01914123",
    "Label": "bafykbzacebtg2lmgqap5bsog4jgdbz4i4g3j2l32j4gcqix2ewkpwqtzjzdfu",
    "StartEpoch": 2228314,
    "EndEpoch": 3754714,
    "StoragePricePerEpoch": "0",
    "ProviderCollateral": "8609275213761451",
    "ClientCollateral": "0"
  },
  "State": {
    "SectorStartEpoch": 2214772,
    "LastUpdatedEpoch": 2577642,
    "SlashEpoch": -1,
    "VerifiedClaim": 0
  }
}
# lotus client retrieve --provider f01914123 bafykbzacebtg2lmgqap5bsog4jgdbz4i4g3j2l32j4gcqix2ewkpwqtzjzdfu baga6ea4seaqjumdku2dza7rhz3expwxoljwmmlwnl6g3pbfwuhklfbosklbosfy.car
Recv 0 B, Paid 0 FIL, Open (New), 0s [1674922066658078712|0]
Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 2ms [1674922066658078712|0]
Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 367ms [1674922066658078712|0]
Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 367ms [1674922066658078712|0]
Recv 0 B, Paid 0 FIL, ProviderCancelled (Cancelling), 24.013s [1674922066658078712|0]
Recv 0 B, Paid 0 FIL, CancelComplete (Cancelled), 24.013s [1674922066658078712|0]
ERROR: Retrieval Proposal Cancelled: Provider cancelled retrieval

I am able to download from MinerID f01926792 but is goes terrible slow, slower then expected from a miner located in Frankfurt ... but its slowly coming in 😄

xxcisco commented 1 year ago

SP stored unsealed files in cold storage, but some failures occurred, causing some unsealed files to be lost. SP tried to repair the problem through sealed files but was not successful. I hope the official can provide a repair tool or there is another way to recover.

cryptowhizzard commented 1 year ago

Hi @xxcisco

Can you confirm that all above SP's do not support fast retrieval of your sectors?

If so i can put them in my block list to prevent other data preparers getting stuck with the same issues until resolved.

xxcisco commented 1 year ago

Thank you for your kindness. We have already made contact with SP and our current packaging can now be retrieved. SP promises that all future packaging will be retrievable as well. Thank you again.

cryptowhizzard commented 1 year ago

Hi

It seems that the retrieval is still not working.

Feb 15 02:26:41 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:26:41.660+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf:\n [/ip4/139.84.166.87/tcp/24001] dial tcp4 139.84.166.87:24001: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01927252\",\"MinerPeer\":{\"Address\":\"f01927252\",\"ID\":\"12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf\",\"PieceCID\":null}}"} Feb 15 02:26:41 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:26:41.660+0100#011INFO#011retry#011retry/retry.go:17#011Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 15 02:27:19 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:27:19.997+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf:\n [/ip4/139.84.166.87/tcp/24001] dial backoff\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01927252\",\"MinerPeer\":{\"Address\":\"f01927252\",\"ID\":\"12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf\",\"PieceCID\":null}}"} Feb 15 02:27:19 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:27:19.997+0100#011INFO#011retry#011retry/retry.go:17#011Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 15 02:29:42 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:29:42.720+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf:\n [/ip4/139.84.166.87/tcp/24001] dial tcp4 139.84.166.87:24001: i/o timeout\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01927252\",\"MinerPeer\":{\"Address\":\"f01927252\",\"ID\":\"12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf\",\"PieceCID\":null}}"} Feb 15 02:29:42 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:29:42.720+0100#011INFO#011retry#011retry/retry.go:17#011Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 15 02:32:02 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:32:02.435+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf:\n [/ip4/139.84.166.87/tcp/24001] dial tcp4 139.84.166.87:24001: connect: no route to host\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01927252\",\"MinerPeer\":{\"Address\":\"f01927252\",\"ID\":\"12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf\",\"PieceCID\":null}}"} Feb 15 02:32:02 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:32:02.435+0100#011INFO#011retry#011retry/retry.go:17#011Retrying after error:RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 15 02:34:33 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:34:33.666+0100#011WARN#011rpc#011go-jsonrpc@v0.1.9/client.go:560#011unmarshaling failed#011{"message": "{\"Err\":\"exhausted 5 attempts but failed to open stream, err: failed to dial 12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf:\n * [/ip4/139.84.166.87/tcp/24001] dial tcp4 139.84.166.87:24001: connect: no route to host\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01927252\",\"MinerPeer\":{\"Address\":\"f01927252\",\"ID\":\"12D3KooWBsxoo9dZoBoe6SLmV3HYFKebMucBLJ4TJjRxsoqE9dJf\",\"PieceCID\":null}}"} Feb 15 02:34:33 proposals dealscanner-f01917191-f01927252-24237962: 2023-02-15T02:34:33.666+0100#011ERROR#011retry#011retry/retry.go:29#011Failed after 5 attempts, last error: RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 15 02:34:33 proposals dealscanner-f01917191-f01927252-24237962: ERROR: RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"' Feb 15 02:34:33 proposals dealscanner-f01917191-f01927252-24237962: