[DataCap Application] <LaughStorage> - <Sloan Digital Sky Survey>

[26dos]

Version

1

DataCap Applicant

001

Project ID

001

Data Owner Name

LaughStorage

Data Owner Country/Region

China

Data Owner Industry

Not-for-Profit

Website

https://www.sdss.org/

Social Media Handle

-

Social Media Type

Slack

What is your role related to the dataset

Data Preparer

Total amount of DataCap being requested

5PiB

Expected size of single dataset (one copy)

750TiB

Number of replicas to store

7

Weekly allocation of DataCap requested

1PiB

On-chain address for first allocation

f1kixvj72gdqnskqy4pj2ucuqbjedt3sqebt3w3sa

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

I joined the filecoin network in 2021, and made the cc package of fil at the very beginning.  In 2022, we did a part of cc to dc conversion, and now we have a planned continuous development of data storage. In 2023, I established a technical service company  <Laughstorage> to make in-depth investment in the distributed storage track.

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

The Sloan Digital Sky Survey (SDSS) is one of the most ambitious and influential surveys in the history of astronomy. 
The SDSS project has established in 2000, five periods, 18 times data released. The 19th DR will be in 2024. 
As for now, there are about 750TB volume of data can be accessed.  5.5 million directories, 400 million files. 
DR1-DR7: SDSS-I, 2000-2005; SDSS-II, 2005-2008), it obtained deep, multi-color images covering more than a quarter of the sky and created 3-dimensional maps containing more than 930,000 galaxies and more than 120,000 quasars.
DR8: contains all images from the SDSS telescope - the largest color image of the sky ever made. It also includes measurements for nearly 500 million stars and galaxies, and spectra of nearly two million. 
DR9 contains the first release of BOSS spectroscopy to the public as well as several significant updates to the cumulative SDSS archive
DR10 contains the first release of APOGEE infrared Galactic spectroscopy as well as cumulative updates to the BOSS optical extragalactic spectroscopy archive
The SDSS began regular survey operations in 2000, after a decade of design and construction.  It has progressed through several phases, SDSS-I (2000-2005), SDSS-II (2005-2008), SDSS-III (2008-2014), and SDSS-IV (2014-2020).  Each of these phases has involved multiple surveys with interlocking science goals.  The three surveys that comprise SDSS-IV are eBOSS (including SPIDERS and TDSS), APOGEE-2, and MaNGA (including MaStar),
The SDSS-V Pioneering Panoptic Spectroscopy program started observing in October 2020, and consists of three surveys, known in SDSS-V terminology as mapper programs.

Milky Way Mapper is a multi-object spectroscopic survey to obtain near-infrared and/or optical spectra of more than 4 million stars throughout the Milky Way and Local Group
Local Volume Mapper is an optical, integral-field spectroscopic survey that will target the Milky Way, Small and Large Magellanic Clouds, and other Local Volume galaxies
Black Hole Mapper is a multi-object spectroscopic survey that emphasizes optical spectra (often also with multiple epochs of spectroscopy) for more than 300,000 quasars

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

If you are a data preparer. What is your location (Country/Region)

China

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

After processing the data I download, I will transfer through online.

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.

AFAK NO

Please share a sample of the data

http://classic.sdss.org/dr7/
http://sdss3.org/
https://www.sdss4.org/dr17/data_access/volume/
https://dr17.sdss.org/sas/dr17/apogee/spectro/aspcap/
https://dr17.sdss.org/sas/dr17/apogee/spectro/speclib/

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

Yearly

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

1.5 to 2 years

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, IPFS

How did you find your storage providers

Slack, Big Data Exchange, Partners

If you answered "Others" in the previous question, what is the tool or platform you used

No response

Please list the provider IDs and location of the storage providers you will be working with.

1.f02980903  South Korea (Republic of Korea)
2.f02948413  china
3.f02224274  hk
4.f03035686  nanchang

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

[datacap-bot[bot]]

Application is waiting for allocator review

[psh0691]

Hi @26dos Thank you for applying for DC allocation.

1. Why did you choose me when there are a lot of alloters in China?

2. Which company has a Korean account? How did you find out? I want to know because I am in Korea and can introduce more Korean SPs.

3. What is your nickname on social media Slack?

4. Did you apply for DC to the previous LDN? If so, please link.

5. Have you ever received DC with the same data before?

[26dos]

Hi, @psh0691 Thank you for your reply.

Regarding the first point, I would like to explain to you the situation in China, most of the active alloters in China their quota has been used up, there are still some inactive alloters that can't be contacted, and your allotment supports the public dataset, it's an excellent alloter.

Second point, their company name is FiveByte, we are slack contact more, currently we have at least 4+ nodes in different regions, if you can introduce us is better.

Third point, slack: LaughStorage

Fourth point, we haven't applied in ALLOCATION mode, only in notary mode. https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2232

Fifth point, yes, part of it was acquired in notary mode, but the project was not completed.

[psh0691]

First of all, I will support the first round. After that, we will report and support the deployment status and compliance with FIL+ regulations.

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

1PiB

DataCap Amount - First Tranche

50TiB

Client address

f1kixvj72gdqnskqy4pj2ucuqbjedt3sqebt3w3sa

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f1kixvj72gdqnskqy4pj2ucuqbjedt3sqebt3w3sa

DataCap allocation requested

50TiB

Id

6ba0f07e-3f6b-4fd3-85b8-d08edd15c69a

[datacap-bot[bot]]

Application is ready to sign

[datacap-bot[bot]]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaceddqsj75gy7c6tatyeasg336t3yiaplh225ntr2oippu7sackt6hw

Address

f1kixvj72gdqnskqy4pj2ucuqbjedt3sqebt3w3sa

Datacap Allocated

50TiB

Signer Address

f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i

Id

6ba0f07e-3f6b-4fd3-85b8-d08edd15c69a

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

[datacap-bot[bot]]

Application is Granted

[26dos]

@psh0691 Thanks for your support, by the way, the project has started and the first distribution will start from these nodes: f02980903 - South Korea f03151449 - shenzhen f03151456 - china f03157883 - china f02826253 - Singaporean

[datacap-bot[bot]]

Client used 75% of the allocated DataCap. Consider allocating next tranche.

[ssnks1]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

⚠️ 100.00% of Storage Providers have retrieval success rate equal to zero.

⚠️ The average retrieval success rate is 0.00%

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

⚠️ CID sharing has been observed. (Top 3)

• 96.00 GiB - f1gtwubtwewlc4a57kv3kr3jk2nevop5h4bagnmea - ANECollege

[^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.

[psh0691]

@26dos

1. The data you deployed has a 0% scan success rate across all SPs.

2. In addition, the DC and CID assigned from other assignors were shared.

We need clarification on this.

[26dos]

@26dos I'm sorry I was about to make a clarification on that, we spent some time checking on that. On the first question: The f02980903 is using the market wrapper, so their retrieval rate is not available on spark, because currently spark can only look up the boost wrapper, but if we manually retrieve it, he can retrieve it f03151449andf03151456 are two new nodes, you can see their ‘new’ tags on the browser, so we need to wait for them to be officially included in spark, I believe that soon they will have the retrieval rate shown in spark. f03157883 this node, is also a new node, at present is also not included in the spark, at present is also trying to find the assistance of the spark team!

About the second question: The duplicate cid found so far appeared on node f03151449, as they are a new node and have different customers, a small amount of data was mixed in the process of data preparation, what is found so far is three sectors. Luckily this data is not very large.

[26dos]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

⚠️ 25.00% of Storage Providers have retrieval success rate equal to zero.

⚠️ 75.00% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

⚠️ CID sharing has been observed. (Top 3)

• 3.75 TiB - f1gtwubtwewlc4a57kv3kr3jk2nevop5h4bagnmea - ANECollege

[^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.

[26dos]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

⚠️ 25.00% of Storage Providers have retrieval success rate equal to zero.

⚠️ 75.00% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

⚠️ CID sharing has been observed. (Top 3)

• 3.75 TiB - f1gtwubtwewlc4a57kv3kr3jk2nevop5h4bagnmea - ANECollege

[^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.

[26dos]

Hi, @psh0691 After the spark team's database update, the retrieval rate can be displayed normally now, and because it's a new node, their retrieval rate will continue to improve, we hope you can continue to support our project!

[psh0691]

@26dos Thank you. I hope you continue your good deployment in the second round.

[datacap-bot[bot]]

Application is in Refill

[datacap-bot[bot]]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacecfjnwuzqwinoypaegsxwh7kwgtcxe33umtnn5s46ewwcoavtrpou

Address

f1kixvj72gdqnskqy4pj2ucuqbjedt3sqebt3w3sa

Datacap Allocated

100TiB

Signer Address

f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i

Id

40b762f5-bbc8-4f03-b820-489fc49b5aae

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

[datacap-bot[bot]]

Application is Granted

[datacap-bot[bot]]

Client used 75% of the allocated DataCap. Consider allocating next tranche.

[26dos]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

⚠️ 20.00% of Storage Providers have retrieval success rate equal to zero.

⚠️ 80.00% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

⚠️ CID sharing has been observed. (Top 3)

• 3.75 TiB - f1gtwubtwewlc4a57kv3kr3jk2nevop5h4bagnmea - ANECollege

[^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.

[26dos]

Hello , @psh0691 As you can see from the bot's report, the retrieval rates of the nodes have been normal, in addition f02980903 can't use spark for the time being because it hasn't yet adjusted the encapsulation technology, we've suspended the cooperation, and we'll continue to cooperate only when it supports spark retrieval.

In addition, the problem of data sharing has not occurred again, the process is now basically mature, the back will be more and more smooth!

[psh0691]

@26dos Thank you. It support the next round.

[datacap-bot[bot]]

Application is in Refill

[datacap-bot[bot]]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzaced4kg2ttoyo37r5h7xgdiinpdn6poouqvzu4ua5igyoyv5hgce6sa

Address

f1kixvj72gdqnskqy4pj2ucuqbjedt3sqebt3w3sa

Datacap Allocated

200TiB

Signer Address

f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i

Id

301be277-ebfe-40e8-b46f-cff70e8c4d36

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

[datacap-bot[bot]]

Application is Granted

[26dos]

@psh0691 Thank you, and if there is anything we can do to help during the project, please let me know.

[26dos]

Early disclosure of new nodes： f02825282 HK GENIUS SOURCES LTD.

[datacap-bot[bot]]

Client used 75% of the allocated DataCap. Consider allocating next tranche.

[26dos]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

⚠️ 20.00% of Storage Providers have retrieval success rate equal to zero.

⚠️ 80.00% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

⚠️ CID sharing has been observed. (Top 3)

• 3.75 TiB - f03137626 - ANECollege

[^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.

[26dos]

Retrieving the status log, as I said above, is normal except for f02980903

[26dos]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 1 storage providers sealed too much duplicate data - f02826253: 22.07%

⚠️ 16.67% of Storage Providers have retrieval success rate equal to zero.

⚠️ 100.00% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients[^3]

⚠️ CID sharing has been observed. (Top 3)

• 3.75 TiB - f03137626 - ANECollege

[^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.

[26dos]

duplicate data - f02826253: 22.07%

Duplicate data is theoretically no more than 20 per cent, this is more than the data backup quota and will be displayed normally in the next round

[26dos]

Hi, @psh0691 Looking forward to your reply.

[datacap-bot[bot]]

Application is in Refill

[datacap-bot[bot]]

Request Approved

Your Datacap Allocation Request has been approved by the Notary

Message sent to Filecoin Network

bafy2bzacedde62tcjnhlgofpnbojbqbqyn3lathvtf5v3hyier2aiovsxrrsy

Address

f1kixvj72gdqnskqy4pj2ucuqbjedt3sqebt3w3sa

Datacap Allocated

500TiB

Signer Address

f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i

Id

a2e3334f-8bb4-4948-b5b4-5e43b70c5fac

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

[datacap-bot[bot]]

Application is Granted

[26dos]

@psh0691 Hello, we are about to start new data storage. Here are the storage provider nodes we are collaborating with. f03179555 SG f03179570 SG f02826253 SG f02825282 HK

[psh0691]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 2 storage providers sealed too much duplicate data - f02828269: 43.52%, f02826253: 43.05%

⚠️ 10.00% of Storage Providers have retrieval success rate equal to zero.

⚠️ 60.00% of Storage Providers have retrieval success rate less than 75%.

Deal Data Replication

⚠️ 42.46% 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)

• 3.75 TiB - f03137626 - ANECollege

[^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.

[26dos]

2 storage providers sealed too much duplicate data - f02828269: 43.52%, f02826253: 43.05%

@psh0691 Hello, the bot report issue is caused by a known bug. There has been a record of this bug being submitted by the community previously.

https://github.com/fidlabs/allocator-tooling/issues/73

[psh0691]

Other applications will be refilled, but this application will not be refilled. I'll try again next time.