[DataCap Application] <The Second Life> - <3D-printed new2>

[AlterEgogo]

Version

1

DataCap Applicant

The Second Life new2

Project ID

007

Data Owner Name

The Second Life new2

Data Owner Country/Region

China

Data Owner Industry

IT & Technology Services

Website

https://mp.weixin.qq.com/s/IMtL_m4sQAxqCmNWlw28Gw

Social Media Handle

https://mp.weixin.qq.com/s/IMtL_m4sQAxqCmNWlw28Gw

Social Media Type

Slack

What is your role related to the dataset

Dataset Owner

Total amount of DataCap being requested

5PiB

Expected size of single dataset (one copy)

500TiB

Number of replicas to store

10

Weekly allocation of DataCap requested

1PiB

On-chain address for first allocation

f15tuvkdu3hp5g4y6ufrjttseppvqvfodinn2u23q

Data Type of Application

Private Commercial/Enterprise

Custom multisig

• [ ] Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

The Second Life Universe Block is a digital hipster block with 3D printing and digital twins as the underlying technology, and a collection of 3D-printed real-life artefacts, 3D-printed coffee, and meta-universe experiences. Embrace the future, private ordering, self-realisation, and one-click construction of the second life of real human beings.

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

For each 3D printed model, we need to take high-precision photos of the 360-degree panorama. The production photos for one model are up to tens of thousands of photos, and we will model the model in 3D. We need to store these photos, models and other data

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?

We currently store our data on our own work computers, and on servers in the server room. In the case of data from the computers we will transfer it over the network, and in the case of data from the server we can do hard drive mailing

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.

We have not previously stored on an IPFS network and the cost of storing on an IPFS network will make it much cheaper for us to do business.SP's information is something we are currently in contact with on an ongoing basis, and I will disclose it below in the request form.

Please share a sample of the data

You can check out the WeChat video number, the name of the account is "第二人生3D真人手办".

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

• [ ] I confirm

If you chose not to confirm, what was the reason

Because the data stored is corporate data, it has a certain level of confidentiality

What is the expected retrieval frequency for this data

Never

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

2 to 3 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, 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.

f03079511 HK；
f02327534 US；
f02894855 China；
f02826234 SG

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

[NDLABS-Leo]

There is a system bug in issues that prevents signatures.

Please check the review log: https://github.com/NDLABS-Leo/Allocator-Pathway-Enterprise-data/issues/10

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

1PiB

DataCap Amount - First Tranche

500TiB

Client address

f15tuvkdu3hp5g4y6ufrjttseppvqvfodinn2u23q

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f15tuvkdu3hp5g4y6ufrjttseppvqvfodinn2u23q

DataCap allocation requested

500TiB

Id

2e672124-4e5e-4b26-98e4-3e9268c5c312

[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

bafy2bzaceao3fwdlqzyetjho74ucsua7g2xokrfha7oe4ocq74s6fc3bqqary

Address

f15tuvkdu3hp5g4y6ufrjttseppvqvfodinn2u23q

Datacap Allocated

500TiB

Signer Address

f1yayfsv6whu3rheviucvventj3y6t542xfpb47ei

Id

2e672124-4e5e-4b26-98e4-3e9268c5c312

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

[datacap-bot[bot]]

Application is Granted

[NDLABS-Leo]

Since the bugs have been taken care of, I signed it. Please check the review log: https://github.com/NDLABS-Leo/Allocator-Pathway-Enterprise-data/issues/10

[NDLABS-Leo]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report[^1]

No active deals found for this client.

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

[AlterEgogo]

Nodal disclosure of co-operation：

f02827151 Guangdong f02827694 Guangdong f01926635 Sichuan f02980903 KR f01999119 Sichuan

[NDLABS-Leo]

[NDLABS-Leo]

Node connectivity testing complete

[NDLABS-Leo]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

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

⚠️ The average retrieval success rate is 9.22%

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.

[NDLABS-Leo]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

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

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

⚠️ The average retrieval success rate is 13.14%

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.

[NDLABS-Leo]

@AlterEgogo Currently, these two nodes appear to be unable to perform retrieval based on the report. Is there a solution for this？

[AlterEgogo]

@NDLABS-Leo 7151and0903. They have all used the Louts technical pathway and are currently unable to perform retrieval via Spark. We have paused our collaboration with them. Please review the following nodes, as we will select them for the next round of collaboration: f02826815. Hong Kong f02828269. Guangzhou f02826253. Singapore f02825282. Hong Kong

[NDLABS-Leo]

f02826815 | 152.32.253.7

f02828269 | 202.105.141.166

f02826253 | 118.194.234.162

f02825282 | 39.109.85.3

[NDLABS-Leo]

@AlterEgogo The address review is fine, and the retrieval rate is normal. We hope to maintain this.

[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

bafy2bzaceav7ogbh5d22qskgxzrg7enjb3lrtww3dp6aiio2cii76ynydnwow

Address

f15tuvkdu3hp5g4y6ufrjttseppvqvfodinn2u23q

Datacap Allocated

1PiB

Signer Address

f1yayfsv6whu3rheviucvventj3y6t542xfpb47ei

Id

8ed8e9a6-4191-4fa0-a331-c40e24f4486c

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

[datacap-bot[bot]]

Application is Granted

[NDLABS-Leo]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 2 storage providers sealed too much duplicate data - f02828269: 27.37%, f02825282: 27.17%

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

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

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.

[NDLABS-Leo]

@AlterEgogo Hello, I noticed that most of the nodes have satisfactory retrieval rates; however, there are a few nodes with a retrieval rate of 0. Could you please explain the reasons behind this issue and let us know if there are any plans or solutions to improve it?

The nodes that need improvement are as follows:

[NDLABS-Leo]

2 storage providers sealed too much duplicate data - f02828269: 27.37%, f02825282: 27.17%

Note: This issue is a common problem and is due to a bug in the bot, which has existed in the community for a long time. It will not be considered in this review.

[AlterEgogo]

@NDLABS-Leo Yes, before selecting new SPs, we require them to meet a certain retrieval rate. Regarding the nodes with lower retrieval rates that you mentioned, some of them are experiencing network issues and are currently being adjusted. Additionally, node 0903 will not be used for data storage in the future. We hope you can allow us to continue our project, as this would be very helpful for us.

[NDLABS-Leo]

@AlterEgogo Do you have plans to introduce new SPs?

[AlterEgogo]

@NDLABS-Leo For the high-quality SPs we currently collaborate with, we plan to continue retaining them. At this time, we do not intend to introduce new SPs. However, should we establish partnerships with new SPs in the future, I will disclose this information in the Issues section as soon as possible. Thank you.

[NDLABS-Leo]

@AlterEgogo Understood, please continue using the DataCap responsibly.

[AlterEgogo]

@NDLABS-Leo Understood, thank you, sir.

[datacap-bot[bot]]

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

[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

bafy2bzacec4l7wt3fjldfdbtpyzcfzlhe47lovbmmbul53nje7gdxnzak2e7k

Address

f15tuvkdu3hp5g4y6ufrjttseppvqvfodinn2u23q

Datacap Allocated

1PiB

Signer Address

f1yayfsv6whu3rheviucvventj3y6t542xfpb47ei

Id

77102793-ba65-4ed8-8b05-9512af2604b1

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

[datacap-bot[bot]]

Application is Granted

[AlterEgogo]

New sp：f02826007 base Singapore

[datacap-bot[bot]]

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

[NDLABS-Leo]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 2 storage providers sealed too much duplicate data - f02828269: 27.37%, f02825282: 27.17%

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

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

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.

[NDLABS-Leo]

@AlterEgogo Hello, for the better progress of the project, we hope you can disclose more information regarding data preparation. Additionally, if you have updated SP nodes, please update them in real time according to your cooperation with SPs. Thank you.