filecoin-project / filecoin-plus-large-datasets

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

[DataCap Application] - CognoCloud #388

Open jessie8o8 opened 2 years ago

jessie8o8 commented 2 years ago

Large Dataset Notary Application

To apply for DataCap to onboard your dataset to Filecoin, please fill out the following.

Core Information

Please respond to the questions below by replacing the text saying "Please answer here". Include as much detail as you can in your answer.

Project details

Share a brief history of your project and organization. Cloud services company offering iaas and dramas for our customers. We wish to have an archived backup copy of the data

What is the primary source of funding for this project? N/A

What other projects/ecosystem stakeholders is this project associated with? Moose Mining and other reputable North American SPs

Use-case details

Describe the data being stored onto Filecoin VMDKs, VHDs, files, etc of our customers

Where was the data in this dataset sourced from? Our servers and storage in Toronto

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

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). Data will be encrypted

What is the expected retrieval frequency for this data? Very rare

For how long do you plan to keep this dataset stored on Filecoin? As long as possible for longer term archiving

DataCap allocation plan

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

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

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. Moose Mining and other reputable North American SPs

How will you be distributing deals across storage providers? There is going to be an offline data transfer process where files are hosted online and other storage providers can download them.

Do you have the resources/funding to start making deals as soon as you receive DataCap? Yes

What support from the community would help you onboard onto Filecoin? ESPA Community

cryptowhizzard commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacedrjgtgs5j765hhp7lmp7mpsoqsr3zlstuis377z3nq4ukom6ldq2

Address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

Datacap Allocated

200.00TiB

Signer Address

f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa

Id

1c692f70-fa44-4241-85bf-5e7cded046dd

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

cryptowhizzard commented 1 year ago

Per comments of @jamerduhgamer

I am supportive of this LDN, obviously, since Moose is an ESPA participant.

s0nik42 commented 1 year ago

good to me

s0nik42 commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaced6sbrlvmbnusm55izpq4jok3dbf7ushnoqzor6d7qglpu3sasrqw

Address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

Datacap Allocated

200.00TiB

Signer Address

f1wxhnytjmklj2czezaqcfl7eb4nkgmaxysnegwii

Id

1c692f70-fa44-4241-85bf-5e7cded046dd

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

MarshLin88 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

⚠️ 1 storage providers sealed more than 50% of total datacap - f01872494: 87.27%

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

Deal Data Replication

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

MarshLin88 commented 1 year ago

Bad report as before. Tagging @cryptowhizzard @s0nik42 with no DD and abusive signing!

kenzz45 commented 1 year ago

This application has raised T&T flags based on the non-compliant reports and notary signatures suspected of collusion. Notaries kindly assess the updated report prior to singing further tranches.

kevzak commented 1 year ago

I was not familiar with this application, it was pre-E-Fil+ process days.

Looks like the applicant gathered information about the cloud provider and confirmed it's plan to store data for clients. No issues there.

Two comments from me:

I don't see details about the actual data. What types of client data are being onboarded? It says: VMDKs, VHDs, files, etc of our customers. That's not specific enough IMO. Just want to confirm it's not material that is not supportable here.

Also, I see only one SP entity listed and actively storing. I might have missed comments above about that but the plan should include a clear list of SPs involved meeting distribution guidelines unless otherwise described.

Stanton15 commented 1 year ago

Awesome application! Had a talk with PikNik and the client, very supportive of these types of LDNs bringing real customers to Filecoin. Keep up the good work, you got my support.

No actual data owner info, No SP introduction, Serious deviation from the weekly schedule, Zero HTTP retrieval success rate, Same region, bad report...

@herrehesse How can you come to such a ridiculous conclusion?

@mjroddy Signing with no due diligence! Warning!!

Requesting a pauze on this application.

AGREE!

cryptowhizzard 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

⚠️ 1 storage providers sealed more than 50% of total datacap - f01872494: 67.59%

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

Deal Data Replication

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

cryptowhizzard commented 1 year ago

Looking good, please continue.

Sunyaoyaomk commented 1 year ago

image

cryptowhizzard commented 1 year ago

https://github.com/filecoin-project/notary-governance/issues/946

Scherm­afbeelding 2023-08-01 om 09 16 05

This dispute was already closed and your gaslighting tactics won't help.

Sunyaoyaomk commented 1 year ago

Comment from DC seller, we are inclined to ignore.

jamerduhgamer commented 1 year ago

Hi @Kevin-PiKNiK, I just asked Moose Mining to respond to the outstanding questions about the Cogno Cloud client data!

Here is the list of SPs that will be storing the dataset and as a reminder that it is a requirement for this data to stay within the United States and Canada.

I have also asked @jessie8o8 to complete the KYC process.

data-programs commented 1 year ago
KYC

This user’s identity has been verified through filplus.storage

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!

jamerduhgamer commented 1 year ago

Can we get this application re-opened? We are still looking for additional SPs to seal this dataset. Another SP just started sealing last week.

Current SP List is as follows:

raghavrmadya commented 1 year ago

Re-opening on the request of the client

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

DataCap Allocation requested

Request number 4

Multisig Notary address

f01924203

Client address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

DataCap allocation requested

400TiB

Id

a381d17b-6253-4357-87b7-75d10e977f05

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

Stats & Info for DataCap Allocation

Multisig Notary address

f01924203

Client address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

Rule to calculate the allocation request amount

400% of weekly dc amount requested

DataCap allocation requested

400TiB

Total DataCap granted for client so far

18189894035458574336.0YiB

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

18189894035458574336.0YiB

Stats

Number of deals Number of storage providers Previous DC Allocated Top provider Remaining DC
9619 3 200TiB 57.7 50.20TiB
cryptowhizzard commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacebojtrjukbz37e3iorwkwpr4mz4enhfqifef2vkptm57pucl3skjs

Address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

Datacap Allocated

400.00TiB

Signer Address

f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa

Id

a381d17b-6253-4357-87b7-75d10e977f05

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

Fenbushi-Filecoin 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

⚠️ 1 storage providers sealed more than 30% of total datacap - f01872494: 64.83%

Deal Data Replication

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

Fenbushi-Filecoin commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacedye3z4msizkiwcnthwzc5vezj5bufglzvh24mnhih7i5qlvzedca

Address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

Datacap Allocated

400.00TiB

Signer Address

f1yqydpmqb5en262jpottko2kd65msajax7fi4rmq

Id

a381d17b-6253-4357-87b7-75d10e977f05

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

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.

-- Commented by Stale Bot.

jamerduhgamer commented 1 year ago

Comment to keep LDN open. Sealing has been on-going.

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.

-- Commented by Stale Bot.

jamerduhgamer commented 1 year ago

Comment to keep LDN open. Sealing has been on-going.

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

DataCap Allocation requested

Request number 5

Multisig Notary address

f01924203

Client address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

DataCap allocation requested

400TiB

Id

20a1b518-8318-4551-85b0-cfa652ac4de7

PluskitOfficial commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 2 storage providers sealed more than 30% of total datacap - f02229460: 33.09%, f01872494: 48.72%

⚠️ 1 storage providers sealed too much duplicate data - f02229460: 21.42%

Deal Data Replication

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

jamerduhgamer commented 1 year ago

We have 3 SPs currently sealing the dataset which is why 2 of them have more than 30% of the datacap. Still looking for 1 more SP and we should be good on the 100% of deals being sealed on less than 4 SPs as well.

s0nik42 commented 1 year ago

Request Proposed

Your Datacap Allocation Request has been proposed by the Notary

Message sent to Filecoin Network

bafy2bzacebybw7a2qbnbht7yn6phtfbb77fl32oqac56gbtfgulsurhxaine6

Address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

Datacap Allocated

400.00TiB

Signer Address

f1wxhnytjmklj2czezaqcfl7eb4nkgmaxysnegwii

Id

20a1b518-8318-4551-85b0-cfa652ac4de7

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

cryptowhizzard commented 1 year ago

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacedzk4s6hav3led3fbbjnprmxy4vdh2344p22ez3t4lrdqlkff4n26

Address

f1e577krmeli4iuclarvl37pbxtthv66ceuuk4hii

Datacap Allocated

400.00TiB

Signer Address

f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa

Id

20a1b518-8318-4551-85b0-cfa652ac4de7

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

Stanton15 commented 1 year ago

When can we remove this bad notary @cryptowhizzard who has been signing continuously on the same issue. This is not his first time abuse has been exposed.

Is it already allowed to sign without giving any comment? @s0nik42

cryptowhizzard commented 1 year ago

When can we remove this bad notary @cryptowhizzard who has been signing continuously on the same issue. This is not his first time abuse has been exposed.

Is it already allowed to sign without giving any comment? @s0nik42

I’m signing on PikNik. Can you please raise your IQ above room temperature here?

Stanton15 commented 1 year ago

@cryptowhizzard If your mouth is so DIRTY, I suggest washing it before coming over to reply.

Sunnyiscoming commented 1 year ago

Hello, @jessie8o8 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 allowed to move forward for additional notary review.

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.

-- Commented by Stale Bot.

jamerduhgamer commented 1 year ago

Comment to keep open

jessie8o8 commented 1 year ago

Hi @Sunnyiscoming, the form is complete and submitted.

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.

-- Commented by Stale Bot.

jamerduhgamer commented 1 year ago

Comment to keep LDN open.

herrehesse commented 1 year ago

checker:manualTrigger

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

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 2 storage providers sealed more than 30% of total datacap - f02229460: 51.66%, f01872494: 35.94%

⚠️ 1 storage providers sealed too much duplicate data - f02229460: 23.65%

Deal Data Replication

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

herrehesse commented 1 year ago

Screenshot 2023-11-29 at 09 55 19

@jamerduhgamer can you explain the reason why this LDN is not stored according to the rules of FIL+ ?