search

filecoin-project / filecoin-plus-large-datasets

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

[DataCap Application] <EF> - <Language> #2094

Closed Lind111 closed 10 months ago

Lind111 commented 1 year ago

Data Owner Name

EF

What is your role related to the dataset

Dataset Owner

Data Owner Country/Region

China

Data Owner Industry

Education & Training

Website

https://www.hzxsef.com/

Social Media

https://www.hzxsef.com/

Total amount of DataCap being requested

15PiB

Expected size of single dataset (one copy)

2.2P

Number of replicas to store

7

Weekly allocation of DataCap requested

1PiB

On-chain address for first allocation

f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq

Data Type of Application

Public, Open Dataset (Research/Non-Profit)

Custom multisig

Identifier

No response

Share a brief history of your project and organization

At EF, we believe that when people from different countries and cultures understand each other, the world will become a better place. Since its establishment in 1965, EF has helped millions of people appreciate new landscapes, experience new cultures, and gain new insights about the world and oneself.

Is this project associated with other projects/ecosystem stakeholders?

No

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

No response

Describe the data being stored onto Filecoin

Learning courses - focusing on language training, studying abroad, cultural exchange, and academic research

Where was the data currently stored in this dataset sourced from

My Own Storage Infra

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

No response

How do you plan to prepare the dataset

singularity

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

No response

Please share a sample of the data

https://pan.baidu.com/s/16ZAGftTX2LukZQxnUqBBBQ?pwd=7zy3

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

If you chose not to confirm, what was the reason

No response

What is the expected retrieval frequency for this data

Monthly

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

More than 3 years

In which geographies do you plan on making storage deals

Greater China, Asia other than Greater China, North America, Europe

How will you be distributing your data to storage providers

HTTP or FTP server, Shipping hard drives

How do you plan to choose storage providers

Slack

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

No response

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

Still in contact

How do you plan to make deals to your storage providers

Boost client, Lotus client

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

No response

Can you confirm that you will follow the Fil+ guideline

Yes

Lind111 commented 1 year ago

Deal Data Replication ⚠️ 30.46% of deals are for data replicated across less than 4 storage providers.

I've found this issue, due to some SPs being new to the co-op, it causes the back copies to not be distributed evenly, will be improved at a later date!

Lind111 commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

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

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

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

Normalnoise commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

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

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

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

Destore2023 commented 1 year ago

Deal Data Replication ⚠️ 30.46% of deals are for data replicated across less than 4 storage providers.

I've found this issue, due to some SPs being new to the co-op, it causes the back copies to not be distributed evenly, will be improved at a later date!

Thanks, @Lind111 reach me via Slack and explain the question regarding to the data replication.

Based on the retrieval status below, I would like to support the datacap allocation:

lotus state get-deal 54339616
{
  "Proposal": {
    "PieceCID": {
      "/": "baga6ea4seaqe3eujbuku6pmtgxx5odz433cmgchpl2ubf7wnr2a5au4szocwily"
    },
    "PieceSize": 34359738368,
    "VerifiedDeal": true,
    "Client": "f02366250",
    "Provider": "f01128206",
    "Label": "bafybeif7yw2ztktokjqaynruvobrnrfzarolfrkexoqguxdi4uksvw4kgy",
    "StartEpoch": 3224452,
    "EndEpoch": 4750852,
    "StoragePricePerEpoch": "0",
    "ProviderCollateral": "9470258406378259",
    "ClientCollateral": "0"
  },
  "State": {
    "SectorStartEpoch": 3205197,
    "LastUpdatedEpoch": -1,
    "SlashEpoch": -1,
    "VerifiedClaim": 36650785
  }
}
lotus client  retrieve --miner f01128206 bafybeif7yw2ztktokjqaynruvobrnrfzarolfrkexoqguxdi4uksvw4kgy 2094
Recv 0 B, Paid 0 FIL, Open (New), 1ms [1694131646581372760|0]
Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 7ms [1694131646581372760|0]
Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 109ms [1694131646581372760|0]
Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 109ms [1694131646581372760|0]
Recv 23.92 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 225ms [1694131646581372760|24497]
Recv 27.11 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 226ms [1694131646581372760|27757]
Recv 1.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 781ms [1694131646581372760|1076333]
Recv 2.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 897ms [1694131646581372760|2124909]
Recv 3.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1.56s [1694131646581372760|3173485]
Recv 4.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.002s [1694131646581372760|4222061]
Recv 5.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.301s [1694131646581372760|5270637]
Recv 6.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.172s [1694131646581372760|6319213]
Recv 7.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.488s [1694131646581372760|7367789]
Recv 8.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.901s [1694131646581372760|8416365]
Recv 9.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 4.311s [1694131646581372760|9464941]
Recv 10.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 4.718s [1694131646581372760|10513517]
Recv 11.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 5.115s [1694131646581372760|11562093]
Recv 12.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 5.677s [1694131646581372760|12610669]
Recv 13.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 6.064s [1694131646581372760|13659245]
Recv 14.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 6.914s [1694131646581372760|14707821]
Recv 15.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 7.486s [1694131646581372760|15756397]
Recv 16.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 8.069s [1694131646581372760|16804973]
Recv 17.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 8.546s [1694131646581372760|17853549]
Recv 18.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 9.128s [1694131646581372760|18902125]
Recv 19.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 9.606s [1694131646581372760|19950701]
Recv 20.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 10.179s [1694131646581372760|20999277]
Recv 21.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 10.657s [1694131646581372760|22047853]
Recv 22.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 11.229s [1694131646581372760|23096429]
Recv 23.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 11.707s [1694131646581372760|24145005]
Recv 24.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 12.285s [1694131646581372760|25193581]
Recv 25.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 12.763s [1694131646581372760|26242157]
Recv 26.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 13.25s [1694131646581372760|27290733]
Recv 27.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 13.641s [1694131646581372760|28339309]
Recv 28.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 14.214s [1694131646581372760|29387885]
Recv 29.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 14.604s [1694131646581372760|30436461]
Recv 30.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 15.178s [1694131646581372760|31485037]
Recv 31.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 15.66s [1694131646581372760|32533613]
Recv 32.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 16.328s [1694131646581372760|33582189]
Recv 33.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 16.806s [1694131646581372760|34630765]
Recv 34.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.376s [1694131646581372760|35679341]
Recv 35.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.763s [1694131646581372760|36727917]
Recv 36.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.331s [1694131646581372760|37776493]
Recv 37.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.717s [1694131646581372760|38825069]
Recv 38.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 19.284s [1694131646581372760|39873645]
Recv 39.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 19.669s [1694131646581372760|40922221]
Recv 40.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 20.378s [1694131646581372760|41970797]
Recv 41.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 21.312s [1694131646581372760|43019373]
Recv 42.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 23.688s [1694131646581372760|44067949]
Recv 43.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 25.915s [1694131646581372760|45116525]
Recv 44.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 27.591s [1694131646581372760|46165101]
Recv 45.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 28.965s [1694131646581372760|47213677]
Recv 46.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 30.201s [1694131646581372760|48262253]
Recv 47.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 31.06s [1694131646581372760|49310829]
Recv 48.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 31.819s [1694131646581372760|50359405]
Recv 49.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 32.297s [1694131646581372760|51407981]
Recv 50.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 32.77s [1694131646581372760|52456557]
Recv 51.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 33.152s [1694131646581372760|53505133]
Recv 52.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 33.537s [1694131646581372760|54553709]
Recv 53.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 33.969s [1694131646581372760|55602285]
Recv 54.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 34.561s [1694131646581372760|56650861]
Recv 55.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 35.274s [1694131646581372760|57699437]
Recv 56.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 36s [1694131646581372760|58748013]
Recv 57.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 36.682s [1694131646581372760|59796589]
Recv 58.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 37.339s [1694131646581372760|60845165]
Recv 59.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 37.987s [1694131646581372760|61893741]

``

Normalnoise commented 1 year ago

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

There is a little more than 30%. It is acceptable for me, willing to support next round

Lind111 commented 1 year ago

Deal Data Replication ⚠️ 30.46% of deals are for data replicated across less than 4 storage providers. I've found this issue, due to some SPs being new to the co-op, it causes the back copies to not be distributed evenly, will be improved at a later date!

Thanks, @Lind111 reach me via Slack and explain the question regarding to the data replication.

Based on the retrieval status below, I would like to support the datacap allocation:

lotus state get-deal 54339616
{
  "Proposal": {
    "PieceCID": {
      "/": "baga6ea4seaqe3eujbuku6pmtgxx5odz433cmgchpl2ubf7wnr2a5au4szocwily"
    },
    "PieceSize": 34359738368,
    "VerifiedDeal": true,
    "Client": "f02366250",
    "Provider": "f01128206",
    "Label": "bafybeif7yw2ztktokjqaynruvobrnrfzarolfrkexoqguxdi4uksvw4kgy",
    "StartEpoch": 3224452,
    "EndEpoch": 4750852,
    "StoragePricePerEpoch": "0",
    "ProviderCollateral": "9470258406378259",
    "ClientCollateral": "0"
  },
  "State": {
    "SectorStartEpoch": 3205197,
    "LastUpdatedEpoch": -1,
    "SlashEpoch": -1,
    "VerifiedClaim": 36650785
  }
}
lotus client  retrieve --miner f01128206 bafybeif7yw2ztktokjqaynruvobrnrfzarolfrkexoqguxdi4uksvw4kgy 2094
Recv 0 B, Paid 0 FIL, Open (New), 1ms [1694131646581372760|0]
Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 7ms [1694131646581372760|0]
Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 109ms [1694131646581372760|0]
Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 109ms [1694131646581372760|0]
Recv 23.92 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 225ms [1694131646581372760|24497]
Recv 27.11 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 226ms [1694131646581372760|27757]
Recv 1.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 781ms [1694131646581372760|1076333]
Recv 2.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 897ms [1694131646581372760|2124909]
Recv 3.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1.56s [1694131646581372760|3173485]
Recv 4.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.002s [1694131646581372760|4222061]
Recv 5.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.301s [1694131646581372760|5270637]
Recv 6.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.172s [1694131646581372760|6319213]
Recv 7.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.488s [1694131646581372760|7367789]
Recv 8.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.901s [1694131646581372760|8416365]
Recv 9.026 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 4.311s [1694131646581372760|9464941]
Recv 10.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 4.718s [1694131646581372760|10513517]
Recv 11.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 5.115s [1694131646581372760|11562093]
Recv 12.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 5.677s [1694131646581372760|12610669]
Recv 13.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 6.064s [1694131646581372760|13659245]
Recv 14.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 6.914s [1694131646581372760|14707821]
Recv 15.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 7.486s [1694131646581372760|15756397]
Recv 16.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 8.069s [1694131646581372760|16804973]
Recv 17.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 8.546s [1694131646581372760|17853549]
Recv 18.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 9.128s [1694131646581372760|18902125]
Recv 19.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 9.606s [1694131646581372760|19950701]
Recv 20.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 10.179s [1694131646581372760|20999277]
Recv 21.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 10.657s [1694131646581372760|22047853]
Recv 22.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 11.229s [1694131646581372760|23096429]
Recv 23.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 11.707s [1694131646581372760|24145005]
Recv 24.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 12.285s [1694131646581372760|25193581]
Recv 25.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 12.763s [1694131646581372760|26242157]
Recv 26.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 13.25s [1694131646581372760|27290733]
Recv 27.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 13.641s [1694131646581372760|28339309]
Recv 28.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 14.214s [1694131646581372760|29387885]
Recv 29.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 14.604s [1694131646581372760|30436461]
Recv 30.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 15.178s [1694131646581372760|31485037]
Recv 31.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 15.66s [1694131646581372760|32533613]
Recv 32.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 16.328s [1694131646581372760|33582189]
Recv 33.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 16.806s [1694131646581372760|34630765]
Recv 34.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.376s [1694131646581372760|35679341]
Recv 35.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.763s [1694131646581372760|36727917]
Recv 36.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.331s [1694131646581372760|37776493]
Recv 37.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.717s [1694131646581372760|38825069]
Recv 38.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 19.284s [1694131646581372760|39873645]
Recv 39.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 19.669s [1694131646581372760|40922221]
Recv 40.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 20.378s [1694131646581372760|41970797]
Recv 41.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 21.312s [1694131646581372760|43019373]
Recv 42.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 23.688s [1694131646581372760|44067949]
Recv 43.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 25.915s [1694131646581372760|45116525]
Recv 44.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 27.591s [1694131646581372760|46165101]
Recv 45.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 28.965s [1694131646581372760|47213677]
Recv 46.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 30.201s [1694131646581372760|48262253]
Recv 47.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 31.06s [1694131646581372760|49310829]
Recv 48.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 31.819s [1694131646581372760|50359405]
Recv 49.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 32.297s [1694131646581372760|51407981]
Recv 50.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 32.77s [1694131646581372760|52456557]
Recv 51.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 33.152s [1694131646581372760|53505133]
Recv 52.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 33.537s [1694131646581372760|54553709]
Recv 53.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 33.969s [1694131646581372760|55602285]
Recv 54.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 34.561s [1694131646581372760|56650861]
Recv 55.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 35.274s [1694131646581372760|57699437]
Recv 56.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 36s [1694131646581372760|58748013]
Recv 57.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 36.682s [1694131646581372760|59796589]
Recv 58.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 37.339s [1694131646581372760|60845165]
Recv 59.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 37.987s [1694131646581372760|61893741]

``

@Destore2023 Please leave a slack account and I'll contact you right away!

Normalnoise commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedojtcxeohci3fdc4c6audebs5rc3a7ftz3cjmfslgbgqyevuydze

Address

f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq

Datacap Allocated

2.00PiB

Signer Address

f1c5non5yf35avgcpsqvxu4yj54yyvxorwyjochqq

Id

4b485b25-e61d-48bc-8e99-181a478a1061

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

Destore2023 commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzaceczbuikca2xa4nvtnvztig6ulsk7r4fbguu3z6m3crldmackexxqi

Address

f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq

Datacap Allocated

2.00PiB

Signer Address

f1yh6q3nmsg7i2sys7f7dexcuajgoweudcqj2chfi

Id

4b485b25-e61d-48bc-8e99-181a478a1061

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

Lind111 commented 1 year ago

There seems to be a bug.

Lind111 commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

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

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

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

zcfil commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

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

Deal Data Shared with other Clients[^3]

✔️ No CID sharing has been observed.

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

[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger

[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...

Full report

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

zcfil commented 1 year ago

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

There is a little more than 30%. It is acceptable for me, willing to support next round

Deal Data Replication ⚠️ 32.79% of deals are for data replicated across less than 4 storage providers.

@Lind111 It seems to be growing all the time. Can you explain?

zcfil commented 1 year ago

image Speed looks good.

Lind111 commented 1 year ago

31.16% of deals are for data replicated across less than 4 storage providers. There is a little more than 30%. It is acceptable for me, willing to support next round

Deal Data Replication ⚠️ 32.79% of deals are for data replicated across less than 4 storage providers.

@Lind111 It seems to be growing all the time. Can you explain?

@zcfil I've found this issue, due to some SPs being new to the co-op, it causes the back copies to not be distributed evenly, will be improved at a later date!

zcfil commented 1 year ago

企业微信截图_16946588126619 image image

Since this is round 4, I retrieved a car file in its entirety and checked it for consistency with the contents of the application, so I'm happy to sign off on this round，But please take note of the bot report and hopefully improve it in the future

zcfil commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceb2q43p5sfcosr4r7w6odaonakljbdwr54tt5jw23lelix5oz775o

Address

f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq

Datacap Allocated

2.00PiB

Signer Address

f1cjzbiy5xd4ehera4wmbz63pd5ku4oo7g52cldga

Id

4b485b25-e61d-48bc-8e99-181a478a1061

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

Lind111 commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

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

Deal Data Shared with other Clients[^3]

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

Full report

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

Lind111 commented 1 year ago

Deal Data Shared with other Clients2 ⚠️ CID sharing has been observed. (Top 3)

2.25 TiB - f1xvsgtyg7ymo6giksv6qb6gxrr6xsfhjjjyylfey - https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2100

This problem is being investigated.

Lind111 commented 1 year ago

Deal Data Shared with other Clients2 ⚠️ CID sharing has been observed. (Top 3)

2.25 TiB - f1xvsgtyg7ymo6giksv6qb6gxrr6xsfhjjjyylfey - #2100

This problem is being investigated.

The reason has been found Because we have the same cooperation with the domestic SPs :f01836766, we also use the same method in his local generation of car files, because the SP sent me the information contains a duplicate belongs to the #2100 car file, so send the same order, resulting in this problem! image image

Lind111 commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

Lind111 commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

Lind111 commented 12 months ago

checker:manualTrigger

filplus-checker-app[bot] commented 12 months ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

Lind111 commented 12 months ago

checker:manualTrigger

filplus-checker-app[bot] commented 12 months ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

Lind111 commented 12 months ago

checker:manualTrigger

filplus-checker-app[bot] commented 12 months ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

Lind111 commented 12 months ago

checker:manualTrigger

filplus-checker-app[bot] commented 12 months ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

large-datacap-requests[bot] commented 12 months ago

DataCap Allocation requested

Request number 5

Multisig Notary address

f02049625

Client address

f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq

DataCap allocation requested

2PiB

Id

acd6ce7f-f8cb-4946-bed2-d294e3fb6619

Lind111 commented 12 months ago

checker:manualTrigger

filplus-checker-app[bot] commented 12 months ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

Lind111 commented 11 months ago

checker:manualTrigger

filplus-checker-app[bot] commented 11 months ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

nj-steve commented 11 months ago

checker:manualTrigger

nj-steve commented 11 months ago

checker:manualTrigger

filplus-checker-app[bot] commented 11 months ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

igoovo commented 11 months ago

checker:manualTrigger

filplus-checker-app[bot] commented 11 months ago

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

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

Full report

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

igoovo commented 11 months ago

The client contacted me through Slack. Overall Graphsync retrieval success rate: 75.82% From the perspective of SP retrieval rate, overall it is very good. There are two SPs with a retrieval rate of 0, please contact the corresponding SPs to make improvements.

image

Regarding CID sharing, I saw some explanations above, but I still don't quite understand. Please explain again. What are your plans for improvement in the future? https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2094#issuecomment-1720950394

nj-steve commented 11 months ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebdg4zjcxvwjekze2twdrogouyfdweo2ptk7vdjyfscfvk5aipdrs

Address

f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq

Datacap Allocated

2.00PiB

Signer Address

f1xx6555qijma7igpnjspyvdunc4vfxkawnpqy5ii

Id

acd6ce7f-f8cb-4946-bed2-d294e3fb6619

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

nj-steve commented 11 months ago

The reports look so nice.It has a CID sharing warning.The client has explained it was the cause of SP and an unexpected situation.

Lind111 commented 11 months ago

The client contacted me through Slack. Overall Graphsync retrieval success rate: 75.82% From the perspective of SP retrieval rate, overall it is very good. There are two SPs with a retrieval rate of 0, please contact the corresponding SPs to make improvements. image

Have contacted the appropriate SP to make a check, thank you for the reminder!

Regarding CID sharing, I saw some explanations above, but I still don't quite understand. Please explain again. What are your plans for improvement in the future? #2094 (comment)

The source of the problem has been identified and will be eliminated in the future, thank you for your review!