Closed maxvint closed 1 year ago
Thanks for your request!
Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
Total DataCap requested
5PiB
Expected weekly DataCap usage rate
200TiB
Client address
f1k7o76avapwoap5tce5ywbktwlgnroqktfg2sjii
f02049625
f1k7o76avapwoap5tce5ywbktwlgnroqktfg2sjii
100TiB
59b426ef-d2a9-4c68-bccd-3a8a3c31c8d5
I have a few questions about DC allocation.
@psh0691
We have about 9PiB archived of the full blockchain data stored on AWS S3 which contains most of the EVM compatible chains, this is the screenshot of AWS S3 buckets.
We have contacted 4 SPs to store these data, we hope to find more.
We plan to store Filecoin chain data in the future, which is still under development.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedujheoa2evgpaohrnrgzqbsdi52jjrmwz5uot2rhw5kfrqdgliyq
Address
f1k7o76avapwoap5tce5ywbktwlgnroqktfg2sjii
Datacap Allocated
100.00TiB
Signer Address
f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i
Id
59b426ef-d2a9-4c68-bccd-3a8a3c31c8d5
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedujheoa2evgpaohrnrgzqbsdi52jjrmwz5uot2rhw5kfrqdgliyq
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceaxj6moz2qab7oq25jgdpsvu6ystzya3z5kdcxk4sha2f3jda3zsk
Address
f1k7o76avapwoap5tce5ywbktwlgnroqktfg2sjii
Datacap Allocated
100.00TiB
Signer Address
f1yqydpmqb5en262jpottko2kd65msajax7fi4rmq
Id
59b426ef-d2a9-4c68-bccd-3a8a3c31c8d5
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaxj6moz2qab7oq25jgdpsvu6ystzya3z5kdcxk4sha2f3jda3zsk
checker:manualTrigger
There is no previous allocation for this issue.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Hello @yuwenhui
I see deals on chain, however all deals come back as slashed. Can you tell me what has been going on here?
lotus state get-deal 22262474 ERROR: deal 22262474 not found - deal may not have completed sealing before deal proposal start epoch, or deal may have been slashed
For example.
Hello @yuwenhui
I see deals on chain, however all deals come back as slashed. Can you tell me what has been going on here?
lotus state get-deal 22262474 ERROR: deal 22262474 not found - deal may not have completed sealing before deal proposal start epoch, or deal may have been slashed
For example.
Hello @cryptowhizzard
Firstly, lotus state get-deal 22262474 ERROR: deal 22262474 not found
, that's because the deal 22262474 did't completed sealing. You can try lotus state get-deal 22262474
again and it will display the deal state correctly.
{
"Proposal": {
"PieceCID": {
"/": "baga6ea4seaqco33ozurglwm3if4flyfckj4pebpbagz3djkaim7r2ejfroq5kly"
},
"PieceSize": 34359738368,
"VerifiedDeal": true,
"Client": "f01942130",
"Provider": "f02012032",
"Label": "uAXASIKu5te5vPh-PQEHEjLlXyaRRsg-Rq-LYzeWPFOXKjP4_",
"StartEpoch": 2543804,
"EndEpoch": 3582997,
"StoragePricePerEpoch": "0",
"ProviderCollateral": "9675929767997153",
"ClientCollateral": "0"
},
"State": {
"SectorStartEpoch": 2517743,
"LastUpdatedEpoch": -1,
"SlashEpoch": -1,
"VerifiedClaim": 4744821
}
}
However, there was another problem after we confirmed with the SP f02012032, the deal state is StorageDealError, and has an the follow error:
error awaiting deal pre-commit: failed to set up called handler: on head changed error: called check error (h: 2516862): failed to check deal activity: failed to look up deal on chain: looking for publish deal message bafy2bzacebi44wtyxethxffuojvwfhq4fhl5cn65p6nsw5tffmoxljvxgycxw: not found
That's may be an unresolved bug of lotus market, our SP will use boost to import storage deals later.
Hello @yuwenhui
Boost has been around for a long time now and working perfectly. "later" is not the right word. If you want to continue with this LDN the data needs to be retrievable and you need to find SP's that are on boost currently or who are not but have good retrieval in place ( i know there are multiple )
@cryptowhizzard Okey, "later" means we will stop sent deals to these SPs until they can be retrievable. If they could not be retrievable, I will ask you for help in finding more SPs who have good retrieval in place.
checker:manualTrigger
Ji Xia Technology Hong Kong Limited
f1k7o76avapwoap5tce5ywbktwlgnroqktfg2sjii
1
Fenbushi-Filecoin1
psh0691
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
Since this is the 2nd allocation, the following restrictions have been relaxed:
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01991416 | Hong Kong, Central and Western, HKChina Unicom Global |
24.00 TiB | 31.67% | 24.00 TiB | 0.00% |
f02006691 | Hong Kong, Central and Western, HKChina Unicom Global |
24.00 TiB | 31.67% | 24.00 TiB | 0.00% |
f02012032new |
Hong Kong, Central and Western, HKChina Unicom Global |
23.78 TiB | 31.38% | 23.78 TiB | 0.00% |
f01824405 | Hangzhou, Zhejiang, CNSichuan Chuanxn IDC |
4.00 TiB | 5.28% | 4.00 TiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
Since this is the 2nd allocation, the following restrictions have been relaxed:
⚠️ 100.00% of deals are for data replicated across less than 2 storage providers.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
75.78 TiB | 75.78 TiB | 1 | 100.00% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.[^3]
⚠️ CID sharing has been observed.
Other Client | Application | Total Deals Affected | Unique CIDs | Approvers |
---|---|---|---|---|
f1gwuigefejd5jkbtg4uznx45toaie5olh2cgm3dq | FeigeData | 224.00 GiB | 7 | 1 Fenbushi-Filecoin1 kernelogic1 liyunzhi-6661 psh0691 |
[^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> ...
@yuwenhui Can you give me more information about the current SP's you are storing with? Their business name, region and city?
Hi, please explain the abnormal information. CID sharing has been observed.
Hi, please explain the abnormal information. CID sharing has been observed.
Hello @Sunnyiscoming Thanks for your check on our LDN application.
We have contacted our SP and tried to work on the issue of CID sharing you mentioned. Currently we got the feedback that they made some technical mistake when they import the deals of these two datasets. We have communicated many times with SP to check their process of deal storage. And they promise that this will not happen again.
We also hope the community continue giving supervision and suggestions to help us store data on the Filecoin network more efficiently and smoothly.
Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032-22203246: Error: retrieval query for miner f02012032 failed: failed to dial 12D3KooWLBMSggvqs69icS3srwKpZTtaZAS484aQ2XsDchcAUwV2: Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032-22203246: [/ip4/162.219.38.94/tcp/18762] failed to negotiate stream multiplexer: EOF Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032-22289736: Error: retrieval query for miner f02012032 failed: failed to dial 12D3KooWLBMSggvqs69icS3srwKpZTtaZAS484aQ2XsDchcAUwV2: Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032-22289736: [/ip4/162.219.38.94/tcp/18762] failed to negotiate stream multiplexer: read tcp4 212.6.53.183:34775->162.219.38.94:18762: read: connection reset by peer Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032-22201556: Error: retrieval query for miner f02012032 failed: failed to dial 12D3KooWLBMSggvqs69icS3srwKpZTtaZAS484aQ2XsDchcAUwV2: Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032-22201556: [/ip4/162.219.38.94/tcp/18762] failed to negotiate stream multiplexer: read tcp4 212.6.53.183:44425->162.219.38.94:18762: read: connection reset by peer Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032: Error: retrieval query for miner f02012032 failed: failed to dial 12D3KooWLBMSggvqs69icS3srwKpZTtaZAS484aQ2XsDchcAUwV2: Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032: [/ip4/162.219.38.94/tcp/18762] failed to negotiate stream multiplexer: read tcp4 212.6.53.183:33321->162.219.38.94:18762: read: connection reset by peer Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032: Error: retrieval query for miner f02012032 failed: failed to dial 12D3KooWLBMSggvqs69icS3srwKpZTtaZAS484aQ2XsDchcAUwV2: Feb 15 15:25:30 proposals dealscanner-f01942130-f02012032: * [/ip4/162.219.38.94/tcp/18762] failed to negotiate stream multiplexer: read tcp4 212.6.53.183:41663->162.219.38.94:18762: read: connection reset by peer
The retrieval function is still not working.
https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1127#issuecomment-1429294202
@yuwenhui Can you give me more information about the current SP's you are storing with? Their business name, region and city?
Hello, @herrehesse Thanks for your check on my LDN application. Current SP's information as following:
f01824405 ChengDu, CN - RY f01991416 HongKong, CN - RIKIMARU f02012032 HongKong, CN - RIKIMARU f02006691 HongKong, CN - NIHICHE f02014107 Seoul, KR - HMT
Good morning. Retrieval is still not working. Can you have this fixed please?
Good morning. Retrieval is still not working. Can you have this fixed please?
@cryptowhizzard Hello, the retrieval problem has been fixed, now it is works well, please take a look.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 2 storage providers.
⚠️ CID sharing has been observed. (Top 3)
[^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> ...
Click here to view the full report.
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.
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!
This user’s identity has been verified through filplus.storage
Large Dataset Notary Application
To apply for DataCap to onboard your dataset to Filecoin, please fill out the following.
Core Information
Please respond to the questions below by replacing the text saying "Please answer here". Include as much detail as you can in your answer.
Project details
Share a brief history of your project and organization.
What is the primary source of funding for this project?
What other projects/ecosystem stakeholders is this project associated with?
Use-case details
Describe the data being stored onto Filecoin
Where was the data in this dataset sourced from?
Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this.
Confirm that this is a public dataset that can be retrieved by anyone on the Network (i.e., no specific permissions or access rights are required to view the data).
What is the expected retrieval frequency for this data?
For how long do you plan to keep this dataset stored on Filecoin?
DataCap allocation plan
In which geographies (countries, regions) do you plan on making storage deals?
How will you be distributing your data to storage providers? Is there an offline data transfer process?
How do you plan on choosing the storage providers with whom you will be making deals? This should include a plan to ensure the data is retrievable in the future both by you and others.
How will you be distributing deals across storage providers?
Do you have the resources/funding to start making deals as soon as you receive DataCap? What support from the community would help you onboard onto Filecoin?