[DataCap Application] <Blocklike> - <Enterprise media data>

[rileymoody]

Version

1

DataCap Applicant

003

Project ID

003

Data Owner Name

Blocklike

Data Owner Country/Region

China

Data Owner Industry

Information, Media & Telecommunications

Website

https://airdrop.blocklike.com/

Social Media Handle

blocklikecom

Social Media Type

Twitter

What is your role related to the dataset

Dataset Owner

Total amount of DataCap being requested

5PiB

Expected size of single dataset (one copy)

650TiB

Number of replicas to store

8

Weekly allocation of DataCap requested

1PiB

On-chain address for first allocation

f16rxdzqzbuk5elgcbyujrndq4h7jzwaovfamxcma

Data Type of Application

Public, Open Commercial/Enterprise

Custom multisig

• [ ] Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

Starbase is a WEB3.0-focused accelerator. Through our global innovation cooperation network, we can provide sufficient support for the three core requirements of "application scenarios", "financial assets" and "user growth".

Starbase is formed by the merger of VC, a crypto investment institution, and Blocklike, a WEB3.0 media. Since 2018, we have been contributing to the creation of a global data collaboration network with more than 300 ecological partners from over 20 countries and regions. These partners include infrastructure, industry funds, and developer and creator communities. We promote innovation in the global WEB3.0 technology and application through investment, acceleration, and incubation.

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 data we are planning to store mainly consists of media materials, including images, videos, documents, and other related content. Additionally, there are materials related to event organization.

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?

1.Data Organization and Classification: We will categorize all media materials, such as images, videos, and documents. Each type of data will be divided into appropriate batches to facilitate subsequent uploading and management.
2.Data Format and Compression: To ensure efficient data transmission and storage, we will perform appropriate format conversion and compression on the media data. Video files will be compressed using common formats such as MP4, images will use formats like JPEG or PNG, and documents will remain in standard formats such as PDF or DOCX.
3.Data Encryption and Verification: To ensure data security, we will encrypt the data before uploading using standard encryption techniques like AES. At the same time, we will generate a hash value of the data to verify the integrity and consistency of the data after it is uploaded.
4.Upload Tools: In terms of upload tools, we plan to use commonly used tools in the Filecoin ecosystem, such as Estuary or Lotus, to ensure the data is uploaded to the Filecoin network. We will choose appropriate tools for batch uploads based on the scale and type of data.
5.Node Selection: To ensure high availability and retrieval efficiency, we will collaborate with storage providers (SPs) that meet the Filecoin Plus requirements. This will ensure that data is stored on multiple geographically distributed nodes with sufficient backup mechanisms.

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.

This dataset has not been stored on the Filecoin network before. This time, we intend to store the dataset on the Filecoin network for the following reasons:

1.Data Backup and Security: The Filecoin network provides a decentralized storage solution, ensuring that data is stored across multiple geographic locations, which enhances data security and redundancy. Through this distributed storage model, we want to ensure that our media assets are preserved long-term and protected from the risk of data loss due to single points of failure.
2.Retrieval Efficiency and Accessibility: The Filecoin Plus program and its SP nodes offer efficient data retrieval services, which is crucial for a media company like ours. We aim to ensure that users around the world can access these media assets quickly and securely.

Please share a sample of the data

https://x.com/blocklikecom
https://blocklikecom.medium.com/

You can see that the content on these platforms is the data we need to store.

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

Monthly

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, Africa, 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.

f03081958 - Changsha
f03178144 - Tokyo
f03214937 - US
f03179570 - SG
f03151456 - SZ

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