[DataCap Allocation] - Public Welfare Project about popular science of Pregnancy and Birth

medixccc commented 2 years ago

Core Information

Organization Name: Chengdu medix Technology Co., Ltd
Website / Social Media: http://www.yunbaober.com
Total amount of DataCap being requested (between 500 TiB and 5 PiB): 5PiB
Weekly allocation of DataCap requested (usually between 1-100TiB): 300TiB
On-chain address for first allocation: f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq
Region: Greater China Region

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.

Project introduction
This is a commomweal  popular science project about maternity knowledge.
In 2021, entrusted by government，Chengdu medix Technology Co., Ltd cooperated with West China women's and children's Hospital in establishing this public welfare project. Based on the principle of authoritative, professional content and easily understandable form, we have produced a large number of popular science videos about pregnancy, childbirth and education at low cost, and popularized them to pregnant women through various broadcast channels for free.
According to the our project plan, these videos will be translated into Minority Languages for spreading across distressed area in China,South Asia, Southeast Asia and Africa.The purpose is to disseminate more professional and scientific knowledge of pregnancy and birth for free, and improve the awareness of local residents on pregnancy preparation, pregnancy care, pregnancy diseases and postnatal care. In the follow-up, we will continuously launch more knowledge categories and more widely used videos according to the demand feedback from the promotion process.
We divide the promotion into three pharse : China → Southeast Asia → Africa.
Phrase one:By means of short video platform resources, offline promotion, public welfare cooperation and other communication methods, translate these videos into Tibetan, Hui, Qiang, Yi, Mongolian and other Minority languages in Western China, and promote to local residents for gratis wacthing.
Phrase two:Translate these video resources into native languages and promote them to Bhutan, Nepal, Myanmar, Pakistan, Laos and other Southeast Asian regions.
Phrase three:Translate these video resources into native languages and promote them to Zambia, Tanzania, Ethiopia and other African countries.
Organization introduction
West China women's and children's Hospital（https://en.motherchildren.com/en_about_introduction） build in 1896,which is a specialized hospital integrating medical treatment, education, medical research, health prevention and talent training. The hospital has the most authoritative and professional medical team resources in Western China and enjoys a high medical reputatio. All the vedio commentators of this project come from this hospital.
Our company (Chengdu medix Technology Co., Ltd) ， the actual operation subject of the public welfare project，already have established cooperative relationship with this hospital by developing maternity platform(http://www.yunbaober.com).Our company is authorized to record, store and promote the video data of the project.

What is the primary source of funding for this project?

This is a public welfare project, and the funds for shooting, translation and promotion are solely undertaken by Chengdu medix Technology Co., Ltd.

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

None.

Use-case details

Describe the data being stored onto Filecoin

We want store the data in the form of video (multi-language) that involves scientific pregnant preparation, precautions and medical examinationde tails of pregnancy, pregnant symptoms, postpartum health care, and postpartum pelvic floor recovery，ect.
The video data is still being gradually improved and translated and expected to generate at least 5-10p of data every year.
Because of the limited funds for public welfare project, we expect to find safe, reliable, low-cost or even zero cost storage methods.

Where was the data in this dataset sourced from?

It is jointly produced by West China women's and children's Hospital  and Chengdu medix Technology Co., Ltd and authorized to the latter.
Website：https://www.motherchildren.com/video_tip/

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

The data sample：
https://pan.baidu.com/s/1HXB1vrIAAuYN8MGo9_creQ code: smn9 
https://pan.baidu.com/s/1AgDAbkBDvxPB6aUwnyW0Kg code: heys 
https://pan.baidu.com/s/1qcdsX3MytsNRX7n5PaFMog code: fafi

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

Of course. We'd like to provide a pulic and retrievable database.

What is the expected retrieval frequency for this data?

Every three months presently.  But the frequency will increase with the development of this project.

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

Permanently.

DataCap allocation plan

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

According to the progress, we will priority choose the local SP, firstly the greater china,next Southeast Asia,then Africa.

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

Data transfer via http, ftp protocol and hard drive copy(off-chain).

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.

Our public welfare project will preferentially select local SP storage data consistent with the current promotion progress. Besides location, the following requirements are also made: do sp have real data storage experience? Is it capable of regular offline access and online maintenance? Do sp have the determination and ability to store real data for a long time? Finally, it is also necessary to ensure that the users can use the data name or CID to effectively retrieve the project data. We will strictly review and select SP that meets the above requirements to cooperate with us.

How will you be distributing deals across storage providers?

We will select multiple sorage providers in the current operating region and distribute the orders to the selected SPs fairly.

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 have enough funds to support seal.

medixccc commented 1 year ago

Hi，This is our current package of 5 nodes. We have always strictly adhered to the official rule that each node does not exceed 25% of the total DC.

PluskitOfficial commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedszoznppf73iuz2lk7j5zeap7xeqoqssreq5mje6isfg6igdqx5m

Address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

Datacap Allocated

1.17PiB

Signer Address

f1tgnlhtcmhwipfm7thsftxhn5k52velyjlazpvka

Id

114d4761-4dd6-4fa7-8b0e-b17c8c8af458

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

cryptowhizzard commented 1 year ago

Hi,

I was attempting to see what data is stored here but got an error on retrieval.

lotus state get-deal 20335117 { "Proposal": { "PieceCID": { "/": "baga6ea4seaqdgobms6ap4xequxfkfakjq23yt7bsdbu3kbkcntb6aosjxgig2dy" }, "PieceSize": 68719476736, "VerifiedDeal": true, "Client": "f01916544", "Provider": "f01943910", "Label": "uAXCg5AIgfrCtNDxrwxOatjWs-71dzFyfpWm491hdBtdkJD1lY8c", "StartEpoch": 2477241, "EndEpoch": 4007453, "StoragePricePerEpoch": "0", "ProviderCollateral": "17956326706453231", "ClientCollateral": "0" }, "State": { "SectorStartEpoch": 2467842, "LastUpdatedEpoch": 2479117, "SlashEpoch": -1, "VerifiedClaim": 2850591 } }

lotus client retrieve --provider f01943910 uAXCg5AIgfrCtNDxrwxOatjWs-71dzFyfpWm491hdBtdkJD1lY8c 20335117 Recv 0 B, Paid 0 FIL, Open (New), 0s [1672734725541976284|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3ms [1672734725541976284|0] Recv 0 B, Paid 0 FIL, DealRejected (RetryLegacy), 733ms [1672734725541976284|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptanceLegacy), 749ms [1672734725541976284|0] Recv 0 B, Paid 0 FIL, DealRejected (Rejecting), 1.641s [1672734725541976284|0] Recv 0 B, Paid 0 FIL, BlockstoreFinalized (Rejected), 1.642s [1672734725541976284|0] ERROR: Retrieval Proposal Rejected: deal rejected: Possible attempt to put comments in qw() list at /data/vulcan/bin/retrievalfilter.pl line 15. Possible attempt to separate words with commas at /data/vulcan/bin/retrievalfilter.pl line 15. Deals from peer 12D3KooWAhG3BRy2RhVgMbvBNyq5z61JwFYHcmEXopGm5pw54QdW are not welcome

medixccc commented 1 year ago

Hi，@cryptowhizzard ，Thank you for the heads up. We have contacted the SPs who we cooperate with,they found their problem and solved it. Please test the retrieval again. Very appreciate for monitoring our data storage situation.

medixccc commented 1 year ago

Below is a screenshot of SP test retrieval results for your reference.At present, the retrieval is normal, but the retrieval waiting time is relatively long.

NiwanDao commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecm3ijcbl3fy662mzjqdsmazbfvbnn5qph7olvzqx42quyxkkfr6m

Address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

Datacap Allocated

1.17PiB

Signer Address

f1a2lia2cwwekeubwo4nppt4v4vebxs2frozarz3q

Id

114d4761-4dd6-4fa7-8b0e-b17c8c8af458

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

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

DataCap Allocation requested

Request number 5

Multisig Notary address

f01858410

Client address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

DataCap allocation requested

2.34PiB

Id

43072f31-4a5f-4e27-9ea6-13169ca85965

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

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

Last two approvers

xingjitansuo & PluskitOfficial

Rule to calculate the allocation request amount

800% of weekly dc amount requested

DataCap allocation requested

2.34PiB

Total DataCap granted for client so far

1.02PiB

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

3.97PiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
16197	5	1.17PiB	23.73	29.25TiB

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

DataCap and CID Checker Report[^1]

Organization: Chengdu medix Technology Co., Ltd
Client: f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq
Approvers

1BlockMakeronline
2GaryGJG
1newwebgroup
2PluskitOfficial
2xingjitansuo

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 should not exceed 30% of total datacap.
Storage provider should not be storing duplicate data for more than 20%.
Storage provider should have published its public IP address.
All storage providers should be located in different regions.

✔️ Storage provider distribution looks healthy.

Provider	Location	Total Deals Sealed	Percentage	Unique Data	Duplicate Deals
f01943910`new`	Boardman, Oregon, US `Amazon.com, Inc.`	241.03 TiB	23.88%	241.03 TiB	0.00%
f01943941`new`	Singapore, Singapore, SG `Amazon.com, Inc.`	197.94 TiB	19.61%	197.94 TiB	0.00%
f01986300`new`	Sydney, New South Wales, AU `Amazon.com, Inc.`	193.16 TiB	19.14%	193.16 TiB	0.00%
f01945296`new`	Tokyo, Tokyo, JP `Amazon.com, Inc.`	182.19 TiB	18.05%	181.69 TiB	0.27%
f01980952`new`	Chengdu, Sichuan, CN `China Mobile Communications Group Co., Ltd.`	195.09 TiB	19.33%	195.09 TiB	0.00%

Provider Distribution

Deal Data Replication

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

No more than 30% of unique data are stored with less than 4 providers.

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

Unique Data Size	Total Deals Made	Number of Providers	Deal Percentage
1000.16 TiB	1000.66 TiB	1	99.13%
4.38 TiB	8.75 TiB	2	0.87%

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

cryptowhizzard commented 1 year ago

Seems still a bit problematic here:

lotus client retrieve --provider f01943910 uAXCg5AIgfrCtNDxrwxOatjWs-71dzFyfpWm491hdBtdkJD1lY8c 20335117

2023-01-04T11:08:40.261+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 12D3KooWRFHHy3XunzTJig6QtgBHQzQZpfAoD5aF1K6Wjq81sF1F:\n * [/ip4/54.189.87.98/tcp/21390] failed to negotiate security protocol: context deadline exceeded\",\"Root\":null,\"Piece\":null,\"Size\":0,\"MinPrice\":\"\u003cnil\u003e\",\"UnsealPrice\":\"\u003cnil\u003e\",\"PricePerByte\":\"\u003cnil\u003e\",\"PaymentInterval\":0,\"PaymentIntervalIncrease\":0,\"Miner\":\"f01943910\",\"MinerPeer\":{\"Address\":\"f01943910\",\"ID\":\"12D3KooWRFHHy3XunzTJig6QtgBHQzQZpfAoD5aF1K6Wjq81sF1F\",\"PieceCID\":null}}"} ERROR: RPC client error: unmarshaling result: failed to parse big string: '"\u003cnil\u003e"'

BDEio commented 1 year ago

@medixccc Hi! Congratulations on your DataCap approval！ BDE is a verified deals auction house helping you to get paid storing your data with reliable storage providers. If you need any help, please get in touch.

medixccc commented 1 year ago

The previous download failure has been modified according to our requirements after we communicated with SP. Now it can be downloaded successfully,You can check it .The following are our test results for your reference.

GaryGJG commented 1 year ago

@medixccc What is your plan to resolve this problem? ⚠️ 100.00% of deals are for data replicated across less than 4 storage providers.

medixccc commented 1 year ago

@GaryGJG,Thank you for your question We had limited knowledge of the sealing rules before the official data checking tool came out. So we split the data into 5 non-duplicate copies or transferred it to the 5 sp's we contacted. After being alerted by the tool, we fully learned the sealing rules again and rechecked the data and immediately re-copied the complete data to the sp. The copy/transfer of the complete data became extremely slow due to the large amount of data. As a result, for some time before, our sp didn't had the opportunity to make the correction of the previous deviation. In the subsequent sealing, you will be able to see that these sp will repeatedly store data that has already been stored by other sp.

BlockMakeronline commented 1 year ago

@medixccc I'm willing to sign for you, but please store in strict accordance with the regulations in the future.

cryptowhizzard commented 1 year ago

@BlockMakeronline

I would like to test retrievals and see a data allocation plan how the data in the new tranche is stored. Can you arrange before signing?

cryptowhizzard commented 1 year ago

@medixccc

Can you confirm that you work with multiple storage providers and not one organisation having multiple machines?

cryptowhizzard commented 1 year ago

Hello,

It seems that there is some progress now. That is great. The thing that is missing is that the data should be readily retrievable according to the FIl+ guidelines. In this case it is not. I have beed waiting for 2 hours, nothing starts. It means that the SP did not store the unsealed sectors and that is not how it supposed to be. In this way it is almost impossible to do decent due diligence to check if that data stored is really the data that the client indicated to store.

cat /root/Dropbox/clientdealscannerdone/f01916544.csv.log /usr/local/bin/lotus state get-deal 17895092 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIg_zoY-eI9Q7wWKj5BkPfgB6SOGEdFsCx7-HKC3wPDxzo /usr/local/bin/lotus state get-deal 17895311 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIg-S-zMY1BGmcp5OvIMdzuqiNk72H65eWOBXpXJdjxySM /usr/local/bin/lotus state get-deal 17261162 /usr/local/bin/lotus client retrieve --provider f01945296 uAXCg5AIgbTL2WNMme18YwyVoAefLoPz-lN_EjSU51SYS_KltDi4 /usr/local/bin/lotus state get-deal 17261889 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIgV82zO5A3yOQI4LWDipnMwFeRtzdB6SiHW7TKOizPkVE Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556100|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 10ms [1673908265200556100|0] /usr/local/bin/lotus state get-deal 17319912 /usr/local/bin/lotus client retrieve --provider f01945296 uAXCg5AIgN2S1HWCK82VIp6tg5L0A77u1-bkyLswGcveso4VJ4KE Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556101|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 11ms [1673908265200556101|0] /usr/local/bin/lotus state get-deal 17320159 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIg0r6CpMVVDCYDQg2rVzcucGXJWnUBwqqJpC1ytXQ_jqI /usr/local/bin/lotus state get-deal 17368016 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIg4xmrVOGk6ymEkKKcJ2MVeoXKxbMorMPHTrDH84YZVPs Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556102|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 11ms [1673908265200556102|0] /usr/local/bin/lotus state get-deal 17370079 /usr/local/bin/lotus client retrieve --provider f01945296 uAXCg5AIgECBaf0_d2NeZTc1UJ2e6BPKMnytrN32-LZG6TSgPXwY /usr/local/bin/lotus state get-deal 17424569 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIg1XruK1s5gQtIYhA8YYuhwHtErGe3GjDO5LjWMtVKphk Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556103|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 11ms [1673908265200556103|0] /usr/local/bin/lotus state get-deal 17425707 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIg_LIGcmYk2zQ0AKspOqVUdedlDJCl8plpg9Pob17nUAk Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556104|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 14ms [1673908265200556104|0] /usr/local/bin/lotus state get-deal 17472858 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIg2lRdgbtJ2HaJ7smIhGq0gahEVuZb4FuCS300_T5eLNw Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556105|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 10ms [1673908265200556105|0] /usr/local/bin/lotus state get-deal 17472906 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIgBQPXFHTKpykDjbmkecTO4JjP7aE1YLGU5Sws4dNzScM Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556106|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 14ms [1673908265200556106|0] /usr/local/bin/lotus state get-deal 17513694 /usr/local/bin/lotus client retrieve --provider f01945296 uAXCg5AIgEkF5z-nK8lfaKFzkdadzTFLs4OH--GOhEKwJESG1HtA Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556107|0] ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: could not locate piece: pieceCid:baga6ea4seaqbijxbd3vluon7oovut4q4pm3gykvwsmp423sybmmud7svccge4ji deals is empty

Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 11ms [1673908265200556107|0] /usr/local/bin/lotus state get-deal 17513953 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIgxboju0qo0tK_eXYiAO9pGXmOfgiyw4SEjr8TfD1XunM Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556108|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 11ms [1673908265200556108|0] /usr/local/bin/lotus state get-deal 17689283 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIgT6Zb8ZZEe4UMlyYKMGIGYIjPuAn14pnjKT6-pF7_cIU Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556109|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 11ms [1673908265200556109|0] /usr/local/bin/lotus state get-deal 17689372 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIg__Ocs0TyRdas0wVfoXBvDnBDNNxh7spUH2OuaWb0Lhk Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556110|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 11ms [1673908265200556110|0] /usr/local/bin/lotus state get-deal 17721064 /usr/local/bin/lotus client retrieve --provider f01943910 uAXCg5AIgwt_BQgWQuzkffiwkHI9x4AuFKzxQWFNrOa39tIbEKPA Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556111|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 12ms [1673908265200556111|0] Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556112|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 11ms [1673908265200556112|0] Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556113|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 14ms [1673908265200556113|0] Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556114|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 12ms [1673908265200556114|0] Recv 0 B, Paid 0 FIL, Open (New), 0s [1673908265200556115|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 12ms [1673908265200556115|0]

cryptowhizzard commented 1 year ago

Hello,

I have done due diligence on this one. The outcome of this is that everything is stored with one SP ( Organization )

@BlockMakeronline i suggest you abstain from signing on this one.

The evidence can be easily tracked on chain:

For f01980952 for example:

lotus net connect f01980952 | f01980952 -> {12D3KooWKdAMZDnt5T3L8itWs1BhZ19JbpX68Cup9BxntaHNB1u7: [/ip4/183.222.164.239/tcp/21390]} | ERROR: failed to parse multiaddr "f01980952": must begin with /

When you repeat the steps for :

https://filfox.info/en/address/f01945296

You can see in the last messages of the worker that there were to ChangeMultiaddrs message:

The first one was bafy2bzacebjzgzdl2stbor5xdaior66nmqxaniqyc5yfbvmptbn4szwbzuscs

The changeMultiaddress was : BLfepO0GU44=

Converting it to HEX on https://base64.guru/converter/decode/hex gives -> 04 b7 de a4 ed 06 538e

Converting this back gives to HEX ( https://www.rapidtables.com/convert/number/hex-to-decimal.html )

04: ipv (protocol code) b7: 183 de: 222 a4: 164 ed: 237

06: tcp 53ea: 21390

Voilla! _ > 183.222.164.237/tcp/21390

It means that this miner was set in the same /24 as f01980952 ( 183.222.164.239/tcp/21390 )

For the remaining we can see that all the devices are running on the same port. (21390 )

And that this network of SP's is brought to us by Fintech / FIN NFT / FIN Dao.

Schermafbeelding 2023-01-20 om 13 50 58

medixccc commented 1 year ago

Hi,@cryptowhizzard After receiving the question, we commissioned a team of third-party data analysts to help us get the on-chain sealed distribution of our application. It is shown in the figure. 202301 Since we realized that we did not fully grasp the seal ing rules, we have adjusted the sealing and our data has been gradually and repeatedly distributed on different sp nodes. We guarantee that when our project is completed, we will be able to strictly meet the data distribution rules required by the community. And we joined the filecoin network because we hope we can decentralize the storage to help us save these medical science videos, so that we can promote it to the places that maybe needed it in the future. After this storage is completed, we will submit a new application to help us store medical image data as well as analyze, teaching, and research some representative medical image data for the course. Therefore, we ask our sp to apply for new nodes specifically for our application to store our data, and use a unified port to facilitate our future use and scheduling. And as we requested, our sp all used port 21390 to open to the public. What's more, we have learned some Fil+ rules through the community before we started sealing. We believe that starting from node packaging, we have to meet the requirement of storing a project in more than 4 sps. Therefore, we requested that the sp we contacted needed to wait until we found enough sps before we started the sealing. Now it seems that this approach is a bit redundant. But it resulted in our first three nodes (f01943910/f01945296/f01980952), seting up the sealing almost on the same day, causing this misunderstanding. At last, as you requested, we fully confirm that we are not looking for the same organization to sealing nodes on different machines.

medixccc commented 1 year ago

Hi, we have responsed all of the previous notary's questions. Also, through our daily monitoring of the SPs' sealing work, everything is in the line, including data retrieval. We have now run out of our allocation and to ensure the sealing is working properly, we are requesting more DC allocation, please let us know if you need us to provide due diligence information. In addition, in the process of our request for review, the notary said that they could not find our application in their backstage. Please help us to verify this and inform us the lastest processing progress. @simonkim0515

cryptowhizzard commented 1 year ago

Hello!

I tried retrieval again ... it still get's stuck.

cat /var/log/syslog | grep f01916544 Feb 2 13:00:52 proposals filplus: client= f01916544 Feb 2 13:00:52 proposals filplus: client= f01916544 Feb 2 13:00:52 proposals filplus: client= f01916544 Feb 2 13:00:52 proposals filplus: client= f01916544 Feb 2 13:00:52 proposals filplus: client= f01916544 Feb 2 14:06:03 proposals filplus: client= f01916544 Feb 2 14:06:03 proposals filplus: client= f01916544 Feb 2 14:06:03 proposals filplus: client= f01916544 Feb 2 14:06:03 proposals filplus: client= f01916544 Feb 2 14:06:03 proposals filplus: client= f01916544 Feb 3 11:56:01 proposals dealscanner: we found file client-f01916544.csv Feb 3 11:56:01 proposals dealscanner: We are processing file client-f01916544.csv Feb 3 11:56:01 proposals dealscanner: File + Path /root/Dropbox/dealscanner/client-f01916544.csv Feb 3 11:57:01 proposals dealscanner-f01916544-f01945296: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471405|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01945296: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3ms [1675293168511471405|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01943941: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471406|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01943941: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 5ms [1675293168511471406|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01945296: Recv 0 B, Paid 0 FIL, Open (New), 2ms [1675293168511471407|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01945296: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 5ms [1675293168511471407|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01943910: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471408|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01943910: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3ms [1675293168511471408|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01943941: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471409|0] Feb 3 11:57:01 proposals dealscanner-f01916544-f01943941: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3ms [1675293168511471409|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943910: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471410|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943910: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 4ms [1675293168511471410|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01945296: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 386ms [1675293168511471405|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01945296: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 387ms [1675293168511471405|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943941: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 557ms [1675293168511471406|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943941: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 558ms [1675293168511471406|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01945296: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 581ms [1675293168511471407|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01945296: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 582ms [1675293168511471407|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943941: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 557ms [1675293168511471409|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943941: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 557ms [1675293168511471409|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943910: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 741ms [1675293168511471408|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943910: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 742ms [1675293168511471408|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943910: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 741ms [1675293168511471410|0] Feb 3 11:57:02 proposals dealscanner-f01916544-f01943910: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 741ms [1675293168511471410|0] Feb 3 11:57:03 proposals dealscanner-f01916544-f01980952: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471411|0] Feb 3 11:57:03 proposals dealscanner-f01916544-f01980952: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471412|0] Feb 3 11:57:03 proposals dealscanner-f01916544-f01980952: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 6ms [1675293168511471411|0] Feb 3 11:57:03 proposals dealscanner-f01916544-f01980952: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 6ms [1675293168511471412|0] Feb 3 11:57:04 proposals dealscanner-f01916544-f01980952: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 402ms [1675293168511471411|0] Feb 3 11:57:04 proposals dealscanner-f01916544-f01980952: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 403ms [1675293168511471411|0] Feb 3 11:57:04 proposals dealscanner-f01916544-f01980952: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 420ms [1675293168511471412|0] Feb 3 11:57:04 proposals dealscanner-f01916544-f01980952: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 421ms [1675293168511471412|0] Feb 3 11:58:05 proposals dealscanner-f01916544-f01986300: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471413|0] Feb 3 11:58:05 proposals dealscanner-f01916544-f01986300: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3ms [1675293168511471413|0] Feb 3 11:58:05 proposals dealscanner-f01916544-f01986300: Recv 0 B, Paid 0 FIL, Open (New), 0s [1675293168511471414|0] Feb 3 11:58:05 proposals dealscanner-f01916544-f01986300: Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 4ms [1675293168511471414|0] Feb 3 11:58:06 proposals dealscanner-f01916544-f01986300: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 828ms [1675293168511471413|0] Feb 3 11:58:06 proposals dealscanner-f01916544-f01986300: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 829ms [1675293168511471413|0] Feb 3 11:58:06 proposals dealscanner-f01916544-f01986300: Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 804ms [1675293168511471414|0] Feb 3 11:58:06 proposals dealscanner-f01916544-f01986300: Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 804ms [1675293168511471414|0]

Did you store the unsealed sectors?

medixccc commented 1 year ago

checker:manualTrigger

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

⚠️ 99.93% 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 full report.

BlockMakeronline commented 1 year ago

Do you have a detailed plan for cooperating with storage providers later?

medixccc commented 1 year ago

Hello @BlockMakeronline Thanks for asking. Our next data storage region will mainly consider Hong Kong and Vietnam. At present, we have reached an agreement with SPs, and they are preparing for shipping machines and network wiring. The new data store will be based on backups of previously stored data. To achieve the goal of multi-copy storage. We can know from the latest CID report that everything is going well at present. As for the Deal Data Replication , refer to the following screenshots, and it can be seen that the data has been gradually repeatedly distributed on different SP nodes. After the storage of the project is completed, the data distribution rules required by the community will definitely be met. 20230302

BlockMakeronline commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceb2tncqwavwhrgemezagv3qt4vyskoqngfxswtajgmnqh4sle652i

Address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

Datacap Allocated

2.34PiB

Signer Address

f1o3twrcpwjtpcd4q36lpq4qmy2qfbgtyy5h6tsty

Id

43072f31-4a5f-4e27-9ea6-13169ca85965

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

cryptowhizzard commented 1 year ago

@BlockMakeronline

Tagging this application for future reference. Retrieval does not work here so this should not have been proposed until fixed.

MRJAVAZHAO commented 1 year ago

20230306132001

MRJAVAZHAO commented 1 year ago

We have done the data retrieval. Everything looks good.

MRJAVAZHAO commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecyvul2cf2a3incmedcktv3xchymhtu4ezjewr363lhxyw7yxekwq

Address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

Datacap Allocated

2.34PiB

Signer Address

f14gme3f52prtyzk6pblogrdd6b6ivp4swc6qmesi

Id

43072f31-4a5f-4e27-9ea6-13169ca85965

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

medixccc commented 1 year ago

The new SP has been recently confirmed, and packaging work will be started as soon as possible.

medixccc commented 1 year ago

checker:manualTrigger

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

⚠️ 69.90% 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 full report.

medixccc commented 1 year ago

Data encapsulation is normal.

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

DataCap Allocation requested

Request number 8

Multisig Notary address

f02049625

Client address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

DataCap allocation requested

475.69TiB

Id

cebad3bd-7668-4dea-93c5-d792ad52d565

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

Stats & Info for DataCap Allocation

Multisig Notary address

f01858410

Client address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

Rule to calculate the allocation request amount

400% of weekly dc amount requested

DataCap allocation requested

475.69TiB

Total DataCap granted for client so far

2.1792948246002197e+74YiB

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

2.1792948246002197e+74YiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
63179	11	2.34PiB	14.77	642.73TiB

OpenGate01 commented 1 year ago

Everything looks good.

OpenGate01 commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaced43wij6ibenu6g7e2a2hzwsq3bcbxznxjpmgyogbqaorjpwrc6oo

Address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

Datacap Allocated

475.69TiB

Signer Address

f1im4hmtbfzqnx7ir74kdaiu4ynjhgqh3sdi2snla

Id

cebad3bd-7668-4dea-93c5-d792ad52d565

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

cryptowhizzard commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 3.60%
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

✔️ 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.

cryptowhizzard commented 1 year ago

@OpenGate01

This application does not look good. Retrieval is less then a few percent and not supported. Until this is fixed this application should not be granted datacap

METAVERSEDATAMINING commented 1 year ago

Upon receiving the applicant's slack request, I attempted retrieval, which functioned normally and data backup also showed significant improvement.

@medixccc,Please pay attention to the new retrieval requirements. Although it has just been initiated without standards, we hope to see improvements. You need to work with your SPs to refine the new retrieval methods. If there are any technical doubts, please raise them on the SLACK channel. I will give you an opportunity to improve.

METAVERSEDATAMINING commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebfyqbmzg3jfqtnlu6jhua4ctc2hjfm3zgjmvdfri2fgc4vbm6cgu

Address

f3xes6nmavi42kahmw35wadaffvozlrlckjgeattzflpehwin6jiyixapmglku4s6iropmjpxdip2umo7ehrwq

Datacap Allocated

475.69TiB

Signer Address

f17idrnfnxl2mbgcgr57a6z2c6lj2qx56gvm3336i

Id

cebad3bd-7668-4dea-93c5-d792ad52d565

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

medixccc commented 1 year ago

Update:A-OK

medixccc commented 1 year ago

Update

cryptowhizzard commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 4.11%
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

⚠️ 31.96% 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 report.

github-actions[bot] commented 1 year ago

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.

github-actions[bot] commented 1 year ago

This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you!

filecoin-project / filecoin-plus-large-datasets