[DataCap Application] Co-Produced Climate Data to Support California's Resilience Investments

jevticgallonsd1466 commented 1 year ago

Data Owner Name

Cal-Adapt Analytics Engine

What is your role related to the dataset

Storage provider filling out application on behalf of the data owner

Data Owner Country/Region

United States

Data Owner Industry

Environment

Website

https://analytics.cal-adapt.org/data/

Social Media

analytics@cal-adapt.org

Total amount of DataCap being requested

4PiB

Expected size of single dataset (one copy)

410TiB

Number of replicas to store

10

Weekly allocation of DataCap requested

300TiB

On-chain address for first allocation

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Data Type of Application

Public, Open Dataset (Research/Non-Profit)

Custom multisig

[ ] Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

We are topblocks team - https://www.topblocks.io

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

Downscaled future and historical climate projections for California and her environs in support of California's Fifth Climate Assessment

Where was the data currently stored in this dataset sourced from

AWS Cloud

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

No response

If you are a data preparer. What is your location (City and Country)

Use singularity to generate car.

Topblocks in Santa Clara, US

If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?

No response

If you are not preparing the data, who will prepare the data? (Provide name and business)

No response

Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution.

Does not yet store on Filecoin network.

Please share a sample of the data

aws s3 ls --no-sign-request --recursive --human-readable --summarize s3://cadcat/

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

[X] I confirm

If you chose not to confirm, what was the reason

No response

What is the expected retrieval frequency for this data

Sporadic

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

Less than 1 year

In which geographies do you plan on making storage deals

Greater China, Asia other than Greater China, North America

How will you be distributing your data to storage providers

HTTP or FTP server

How do you plan to choose storage providers

Slack, Big Data Exchange, Partners

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

|sp|ids|origin|
|--|--|--|
|topblocks|f02301,f03223,f0143858|f0240185|Santa Clara(US)|
|STRAITDEER PTE. LTD.|f02093396|Singapore|
||f02234424|Texas(US)|
||f02058333|Texas(US)|
||f01836766|GuangZhou(CN)|
|zkware|f02230375,f02230941,f02230939,f02230935|Hong Kong(CN)|

How do you plan to make deals to your storage providers

Boost client, Lotus client, Singularity

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

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

Thanks for your request!

Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!

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

Thanks for your request! Everything looks good. :ok_hand:

A Governance Team member will review the information provided and contact you back pretty soon.

Sunnyiscoming commented 1 year ago

Have you prepared enough token for sector pledge?
Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 4 or more storage provider operators or owners.You should list Miner ID, Business Entity, Location of sps you will cooperate with.
Could you send an email to filplus-app-review@fil.org with your official domain in order to confirm your identity? Email name should includes the issue id #2144.
Per the https://github.com/filecoin-project/notary-governance/issues/922 for Open, Public Dataset applicants, please complete the following Fil+ registration form to identify yourself as the applicant and also please add the contact information of the SP entities you are working with to store copies of the data.

This information will be reviewed by Fil+ Governance team to confirm validity and then the application will be triggered for notary review. Let us know if you have any questions.

jevticgallonsd1466 commented 1 year ago

Have you prepared enough token for sector pledge?

Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 4 or more storage provider operators or owners.You should list Miner ID, Business Entity, Location of sps you will cooperate with.

Could you send an email to filplus-app-review@fil.org with your official domain in order to confirm your identity? Email name should includes the issue id [DataCap Application] Co-Produced Climate Data to Support California's Resilience Investments #2144.

Per the Modification: Changes required to public open dataset application flow notary-governance#922 for Open, Public Dataset applicants, please complete the following Fil+ registration form to identify yourself as the applicant and also please add the contact information of the SP entities you are working with to store copies of the data.

This information will be reviewed by Fil+ Governance team to confirm validity and then the application will be triggered for notary review. Let us know if you have any questions.

@Sunnyiscoming

Yes
Email has been sent
Form has been submitted.

thinks

jevticgallonsd1466 commented 1 year ago

sp	ids	origin
topblocks	f02301,f03223,f0143858,f0240185	Santa Clara(US)
STRAITDEER PTE. LTD	f02093396	Singapore
michael	f02234424,f02058333	Texas(US)
zkware	f02230375,f02230941,f02230939,f02230935	Hong Kong(CN)
Huang	f01836766	GuangZhou(CN)
Aron	f01877184	Singapore
luna	f02252173	Tokyo(JP)
chenhanwei	f0109903	sichuang(CN)
lizhenjie	f02201915	sichuang(CN)

herrehesse commented 1 year ago

@jevticgallonsd1466, here are some findings based on the provided minerID list:

For f02230375, f02230941, f02230939, and f02230935, these IDs are concerning due to their subnet containing miners previously engaged in abusive CID sharing on LDNs.

Regarding f02234424 and f02058333, these IDs have participated in fully self-dealing application 1340.

As for f02301, f03223, f0143858, and f0240185, they have been associated with a significant amount of self-dealing across multiple applications.

If you're seeking support for your LDN, I strongly recommend exploring collaboration with other service providers who possess a more reputable track record.

woshidama323 commented 1 year ago

As for f02301, f03223, f0143858, and f0240185, they have been associated with a significant amount of self-dealing across multiple applications.

@raghavrmadya This is exactly what we were concerned about in 913.

This would be used to block all the businesses of ToBlocks by someone Wish you can help to clarify this, Thanks

jevticgallonsd1466 commented 1 year ago

Have you prepared enough token for sector pledge?

Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 4 or more storage provider operators or owners.You should list Miner ID, Business Entity, Location of sps you will cooperate with.

Could you send an email to filplus-app-review@fil.org with your official domain in order to confirm your identity? Email name should includes the issue id [DataCap Application] Co-Produced Climate Data to Support California's Resilience Investments #2144.

Per the Modification: Changes required to public open dataset application flow notary-governance#922 for Open, Public Dataset applicants, please complete the following Fil+ registration form to identify yourself as the applicant and also please add the contact information of the SP entities you are working with to store copies of the data.

This information will be reviewed by Fil+ Governance team to confirm validity and then the application will be triggered for notary review. Let us know if you have any questions.

@Sunnyiscoming

Yes

Email has been sent

Form has been submitted.

thinks

@Sunnyiscoming Please check email. @Filplus-govteam Please check form.

ghost commented 1 year ago

Confirming SPs received as listed here: https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2144#issuecomment-1678348987

@jevticgallonsd1466 a reminder that miner IDs should match actual deals and retrievals should be made available after initial allocations.

Sunnyiscoming commented 1 year ago

Datacap Request Trigger

Total DataCap requested

4PiB

Expected weekly DataCap usage rate

300TiB

Client address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

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

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

DataCap allocation requested

150TiB

Id

e8926416-f7de-4d3b-89bc-6365c8450742

jevticgallonsd1466 commented 1 year ago

Confirming SPs received as listed here: #2144 (comment)

@jevticgallonsd1466 a reminder that miner IDs should match actual deals and retrievals should be made available after initial allocations.

Thank you for your reminder

NiwanDao commented 1 year ago

I love to see AI-related datasets onboard to the FIlecoin network. Could you elaborate more on how your entity will use this dataset?

jevticgallonsd1466 commented 1 year ago

I love to see AI-related datasets onboard to the FIlecoin network. Could you elaborate more on how your entity will use this dataset?

@NiwanDao It can be used by any user for model training. thanks

NiwanDao commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacechal2x47zgm7i3fgapy4pzmfdcrotwvv2gwert4epfsxcjgczouu

Address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Datacap Allocated

150.00TiB

Signer Address

f1a2lia2cwwekeubwo4nppt4v4vebxs2frozarz3q

Id

e8926416-f7de-4d3b-89bc-6365c8450742

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

Aaron01230 commented 1 year ago

Since the client has completed KYC, listed the list of cooperative SPs, and the official member Sunnyiscoming has approved the application for this LDN, so I think there is nothing wrong with these SPs, and I am willing to support this round

a1991car commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecbrenjsikf5ss6hw3d5xfnydpxmdemujodbinjpkzadrleqkz4eu

Address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Datacap Allocated

150.00TiB

Signer Address

f1qnumecdypgrbaebtkdfjnwt5ndacadcuas3deiq

Id

e8926416-f7de-4d3b-89bc-6365c8450742

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

kevzak commented 1 year ago

checker:manualTrigger

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

DataCap Allocation requested

Request number 2

Multisig Notary address

f02049625

Client address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

DataCap allocation requested

300TiB

Id

4359d573-31d9-4a80-8d25-fc37fac97f51

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

Stats & Info for DataCap Allocation

Multisig Notary address

f02049625

Client address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Rule to calculate the allocation request amount

100% of weekly dc amount requested

DataCap allocation requested

300TiB

Total DataCap granted for client so far

150TiB

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

3.85PiB

Stats

Number of deals	Number of storage providers	Previous DC Allocated	Top provider	Remaining DC
0	0	150TiB	NaN	148.18TiB

spaceT9 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: 100.00%
Overall HTTP retrieval success rate: 0.00%
Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

⚠️ 1 storage providers sealed more than 70% of total datacap - f0143858: 100.00%

⚠️ All storage providers are located in the same region.

Deal Data Replication

⚠️ 100.00% of deals are for data replicated across less than 3 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.

kevzak commented 1 year ago

will be keeping an eye on these Storage Providers

sp | ids | origin -- | -- | -- topblocks | f02301,f03223,f0143858,f0240185 | Santa Clara(US) STRAITDEER PTE. LTD | f02093396 | Singapore michael | f02234424,f02058333 | Texas(US) zkware | f02230375,f02230941,f02230939,f02230935 | Hong Kong(CN) Huang | f01836766 | GuangZhou(CN) Aron | f01877184 | Singapore luna | f02252173 | Tokyo(JP) chenhanwei | f0109903 | sichuang(CN) lizhenjie | f02201915 | sichuang(CN)

jevticgallonsd1466 commented 1 year ago

will be keeping an eye on these Storage Providers

sp ids origin topblocks f02301,f03223,f0143858,f0240185 Santa Clara(US) STRAITDEER PTE. LTD f02093396 Singapore michael f02234424,f02058333 Texas(US) zkware f02230375,f02230941,f02230939,f02230935 Hong Kong(CN) Huang f01836766 GuangZhou(CN) Aron f01877184 Singapore luna f02252173 Tokyo(JP) chenhanwei f0109903 sichuang(CN) lizhenjie f02201915 sichuang(CN)

Add ： f02259777 belongs to STRAITDEER PTE. LTD，the region is also in Singapore f02368987 belongs to michael zheng f01888808 romania treal f02032191,f02808800 zhejiang(CN) luna f02252173 Tokyo guan f02808888 GuangZhou(CN) jastin f02816666 Huhehaote Hainan future cloud Technology Co., LTD f02519323 ningxia(CN) JinyiMa f02228866 Tokyo XuanWang f01315130 Chengdu(CN) XiongYing f02240216 Tokyo James f02201190 US

thanks

jevticgallonsd1466 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: 100.00%
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 Dashboard. Click here to view the Retrieval report.

joshua-ne commented 1 year ago

Everything looks good to me. Would be willing to support this round.

joshua-ne commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedf726kb4xhkuvz3ilmulcbqyuriaho47yfw4ppqmiqzy7q6tm2gk

Address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Datacap Allocated

300.00TiB

Signer Address

f1xzff5xup63o5sygr2swp4zvcajg54lotliimdty

Id

4359d573-31d9-4a80-8d25-fc37fac97f51

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

zcfil 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: 85.19%
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 Dashboard. Click here to view the Retrieval report.

zcfil commented 1 year ago

The bot report looks good.

zcfil commented 1 year ago

lotus client retrieve --provider=f0143858 bafybeie4cshn2mhjuxeivobuskfhhfpjn7uyzvfafrwsgmour2u64222vq 123tmp Recv 0 B, Paid 0 FIL, Open (New), 1ms [1694131646581372763|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 5ms [1694131646581372763|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 312ms [1694131646581372763|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 312ms [1694131646581372763|0] Recv 58 B, Paid 0 FIL, BlocksReceived (Ongoing), 361ms [1694131646581372763|58] Recv 113 B, Paid 0 FIL, BlocksReceived (Ongoing), 364ms [1694131646581372763|113] Recv 173 B, Paid 0 FIL, BlocksReceived (Ongoing), 367ms [1694131646581372763|173] Recv 235 B, Paid 0 FIL, BlocksReceived (Ongoing), 367ms [1694131646581372763|235] Recv 293 B, Paid 0 FIL, BlocksReceived (Ongoing), 367ms [1694131646581372763|293] Recv 409 B, Paid 0 FIL, BlocksReceived (Ongoing), 376ms [1694131646581372763|409] Recv 464 B, Paid 0 FIL, BlocksReceived (Ongoing), 380ms [1694131646581372763|464] Recv 522 B, Paid 0 FIL, BlocksReceived (Ongoing), 381ms [1694131646581372763|522] Recv 577 B, Paid 0 FIL, BlocksReceived (Ongoing), 381ms [1694131646581372763|577] Recv 684 B, Paid 0 FIL, BlocksReceived (Ongoing), 381ms [1694131646581372763|684] Recv 16.46 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 541ms [1694131646581372763|16857] Recv 16.91 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 591ms [1694131646581372763|17316] Recv 1.017 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.257s [1694131646581372763|1065892] Recv 2.017 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.85s [1694131646581372763|2114468] Recv 3.017 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.163s [1694131646581372763|3163044] Recv 4.017 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3.708s [1694131646581372763|4211620] Recv 5.017 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 4.023s [1694131646581372763|5260196] Recv 6.017 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 4.987s [1694131646581372763|6308772] Recv 7.017 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 5.424s [1694131646581372763|7357348] Recv 8.017 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 6.007s [1694131646581372763|8405924] Recv 8.221 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 6.146s [1694131646581372763|8620152] Recv 8.735 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 6.606s [1694131646581372763|9158930] Recv 8.735 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 6.608s [1694131646581372763|9159139] Recv 9.735 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 7.298s [1694131646581372763|10207715] Recv 10.73 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 7.989s [1694131646581372763|11256291] Recv 11.73 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 8.678s [1694131646581372763|12304867] Recv 12.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 9.208s [1694131646581372763|12610688] Recv 12.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 9.209s [1694131646581372763|12613848] Recv 13.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 9.883s [1694131646581372763|13662424] Recv 14.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 10.565s [1694131646581372763|14711000] Recv 15.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 11.206s [1694131646581372763|15759576] Recv 16.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 12.245s [1694131646581372763|16808152] Recv 17.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 12.912s [1694131646581372763|17856728] Recv 18.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 13.602s [1694131646581372763|18905304] Recv 19.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 14.224s [1694131646581372763|19953880] Recv 20.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 15.213s [1694131646581372763|21002456] Recv 21.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 15.88s [1694131646581372763|22051032] Recv 22.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 16.501s [1694131646581372763|23099608] Recv 23.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 17.031s [1694131646581372763|24148184] Recv 24.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.019s [1694131646581372763|25196760] Recv 25.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 18.617s [1694131646581372763|26245336] Recv 26.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 19.079s [1694131646581372763|27293912] Recv 27.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 19.556s [1694131646581372763|28342488] Recv 28.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 20.299s [1694131646581372763|29391064] Recv 29.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 20.803s [1694131646581372763|30439640] Recv 30.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 21.218s [1694131646581372763|31488216] Recv 31.03 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 21.607s [1694131646581372763|32536792]

The retrieval is normal and I'm willing to support this round

zcfil commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacebgwzvav2zxkbkr4mm4fdosxtewt3jvdvarizugzvvvggssqxeyiu

Address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Datacap Allocated

300.00TiB

Signer Address

f1cjzbiy5xd4ehera4wmbz63pd5ku4oo7g52cldga

Id

4359d573-31d9-4a80-8d25-fc37fac97f51

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

github-actions[bot] commented 11 months 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.

-- Commented by Stale Bot.

jevticgallonsd1466 commented 11 months ago

continue

jevticgallonsd1466 commented 11 months ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 56.52%
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 Dashboard. Click here to view the Retrieval report.

jevticgallonsd1466 commented 11 months ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 50.22%
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 Dashboard. Click here to view the Retrieval report.

AlanGreaterheat commented 11 months ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 49.39%
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 Dashboard. Click here to view the Retrieval report.

AlanGreaterheat commented 11 months ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedvmeguwx76xzufz2ynnditj6dj4e3nsiz2tq6c43lkf2umxvlp5a

Address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Datacap Allocated

300.00TiB

Signer Address

f1pnmzlxj7cfeo2v6oj5nco46hkg2l46wj7o4xxui

Id

4359d573-31d9-4a80-8d25-fc37fac97f51

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

NDLABS-Leo commented 11 months ago

Good review of reports and willingness to support.

NDLABS-Leo commented 11 months ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacebnhatnhclmbwz37pjutntzcpi4hlcebmccu4oixkhniuqlnxi3ji

Address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Datacap Allocated

300.00TiB

Signer Address

f1yayfsv6whu3rheviucvventj3y6t542xfpb47ei

Id

4359d573-31d9-4a80-8d25-fc37fac97f51

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

DaYouGroup commented 11 months ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Retrieval Statistics

Overall Graphsync retrieval success rate: 49.39%
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 Dashboard. Click here to view the Retrieval report.

DaYouGroup commented 11 months ago

The project looks relatively healthy and I am willing to support this round.

DaYouGroup commented 11 months ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacec2sjc7xruhvpvlvuyjebjmbouxf22xoov365ljgqgmccvmsp4v6a

Address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

Datacap Allocated

300.00TiB

Signer Address

f1nwjsd2mc6hu4qrwnmd6ukrfkuu4h5fhs7u3exii

Id

4359d573-31d9-4a80-8d25-fc37fac97f51

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

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

DataCap Allocation requested

Request number 4

Multisig Notary address

f02049625

Client address

f1grkjspx7oawlnqbba6irxf3ery24e3p565p4gzi

DataCap allocation requested

1.17PiB

Id

cf4dec5f-012e-4234-a267-bb05ec85b111

jevticgallonsd1466 commented 11 months ago

checker:manualTrigger

filecoin-project / filecoin-plus-large-datasets