[DataCap Application] <Asia Television Limited> - <Arts&Recreation>

[MayFBWY]

Data Owner Name

Asia Television Limited

Data Owner Country/Region

Hong Kong

Data Owner Industry

Arts & Recreation

Website

http://www.hkatv.com/

Social Media Handle

https://www.youtube.com/atvhongkong

Social Media Type

Slack

What is your role related to the dataset

Dataset Owner

Total amount of DataCap being requested

8PiB

Expected size of single dataset (one copy)

2PiB

Number of replicas to store

4

Weekly allocation of DataCap requested

2PiB

On-chain address for first allocation

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

Data Type of Application

Public, Open Commercial/Enterprise

Custom multisig

• [X] Use Custom Multisig

Identifier

No response

Share a brief history of your project and organization

Asia Television Limited (Chinese: 亞洲電視有限公司, also known as ATV) is a digital media and broadcasting company in Hong Kong. Established as the first television service in Hong Kong as Rediffusion Television (Chinese: 麗的電視/麗的呼聲) on 29 May 1957, it shifted to terrestrial television on 30 November 1973, and was renamed Asia Television on 24 September 1982. ATV operated two main over-the-air channels: the Cantonese-language ATV Home and the English-language ATV World.

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

Videos, films and other recordings created or belongs to Asia Television Limited.

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)

Hong Kong

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

Graphsplit

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.

No! We have not stored our dataset on Filecoin network yet.

Please share a sample of the data

http://www.hkatv.com/

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 to 1.5 years

In which geographies do you plan on making storage deals

Greater China, Asia other than Greater China, North America, Australia (continent)

How will you be distributing your data to storage providers

HTTP or FTP server, IPFS, Shipping hard drives, Others

How did you find your storage providers

Slack, Big Data Exchange, Partners, Others

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，f03229932，South Korea
2，f03179555， Singapore
3，f03179572, USA
4，f03178077， Tokyo, Japan

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

[datacap-bot[bot]]

Application is waiting for allocator review

[ipfsforcezuofu]

@MayFBWY

I can currently fulfill 2P of your request, which will be allocated in tranches of 150T, 250T, 500T, and 1100T. If this works for you, please send the application materials for your organization and SPs to my email at jiemezhang@gmail.com. Thank you for your understanding.

[MayFBWY]

@ipfsforcezuofu The shares of 150T and 250T are too small to be allocated to 5 SPs. Can we ask for the first share to be 500T? The size of the next share can be determined after you receive our performance report. I hope you can accept this arrangement. I have sent you the KYB and KYC information. Thank you very much!

[ipfsforcezuofu]

@MayFBWY Thank you for providing the information for your organization and SPs. Due to the sensitivity of your organization, I will only share the SPs' information for community review. The KYB and KYC processes have been completed. Please adjust your application to reflect 2P DC and update the geographical details for the SP located outside Asia. Thank you for your cooperation. f03151449：

f03229932：

f03179555：

f03178077：

f03179572 ：

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

10PiB

Expected weekly DataCap usage rate

2PiB

DataCap Amount - First Tranche

0B

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

DataCap allocation requested

0B

Id

43584c84-2416-46ce-885b-bdade0523f95

[datacap-bot[bot]]

Application is ready to sign

[datacap-bot[bot]]

Last pending allocation reverted for an application f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa.

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

10PiB

Expected weekly DataCap usage rate

2PiB

DataCap Amount - First Tranche

0B

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

DataCap allocation requested

0B

Id

f63a1ce7-7339-4664-adb5-ac0b6d079a14

[datacap-bot[bot]]

Application is ready to sign

[datacap-bot[bot]]

Last pending allocation reverted for an application f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa.

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

10PiB

Expected weekly DataCap usage rate

2PiB

DataCap Amount - First Tranche

0B

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

DataCap allocation requested

0B

Id

42e77e69-31f2-4e2d-87c4-247a4ee863b8

[datacap-bot[bot]]

Application is ready to sign

[datacap-bot[bot]]

Last pending allocation reverted for an application f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa.

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

10PiB

Expected weekly DataCap usage rate

2PiB

DataCap Amount - First Tranche

0B

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

DataCap allocation requested

0B

Id

d2c1de30-749e-4544-8e49-0d108152d4d9

[datacap-bot[bot]]

Application is ready to sign

[datacap-bot[bot]]

Last pending allocation reverted for an application f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa.

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

10PiB

Expected weekly DataCap usage rate

2PiB

DataCap Amount - First Tranche

0B

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

DataCap allocation requested

0B

Id

d52145fd-5cf9-4c45-ad85-45c4c05480d1

[datacap-bot[bot]]

Application is ready to sign

[datacap-bot[bot]]

Last pending allocation reverted for an application f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa.

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

10PiB

Expected weekly DataCap usage rate

2PiB

DataCap Amount - First Tranche

0B

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

DataCap allocation requested

0B

Id

531cb4ef-2a96-452c-aa5a-0ddd8ebde2a0

[datacap-bot[bot]]

Application is ready to sign

[datacap-bot[bot]]

Last pending allocation reverted for an application f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa.

[datacap-bot[bot]]

Datacap Request Trigger

Total DataCap requested

10PiB

Expected weekly DataCap usage rate

2PiB

DataCap Amount - First Tranche

500TiB

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

[datacap-bot[bot]]

DataCap Allocation requested

Multisig Notary address

Client address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

DataCap allocation requested

500TiB

Id

16d7265d-b91c-4924-933c-3cbf5443100a

[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

bafy2bzacecwfitxvonincxms3da4baste7jgzymvwgne62d5xbkj642v4b7hk

Address

f3sy5j6z3pv5cnknaph23dyoxqfstiy2ujsi4ssql5nbz22dopjo4f6olohhxfuo2nqk5q5nsp4y24c4yd3ysa

Datacap Allocated

500TiB

Signer Address

f1x4nh2yvv2o2wwr4f7l7ocuenz7trdv7z5oqlgni

Id

16d7265d-b91c-4924-933c-3cbf5443100a

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

[datacap-bot[bot]]

Application is Granted

[MayFBWY]

@ipfsforcezuofu Our company just held an internal meeting and decided that 4 copies of data storage are sufficient, so I will remove one SP: f03151449. I will change my application information. I am sorry for the trouble. I wish you a happy work!

[datacap-bot[bot]]

Issue has been modified. Changes below:

(OLD vs NEW)

Total Requested Amount: 8PiB vs 10PiB Replicas: 4 vs 5 Please list the provider IDs and location of the storage providers you will be working with: 1，f03229932，South Korea 2，f03179555， Singapore 3，f03179572, USA 4，f03178077， Tokyo, Japan vs 1，f03151449， Shenzhen 2，f03229932，South Korea 3，f03179555， Singapore 4，f03179572, USA 5，f03178077， Tokyo, Japan State: ChangesRequested vs Granted

[ipfsforcezuofu]

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

[ipfsforcezuofu]

checker:manualTrigger

[datacap-bot[bot]]

DataCap and CID Checker Report Summary[^1]

Storage Provider Distribution

⚠️ 3 storage providers sealed too much duplicate data - f03179555: 22.61%, f03229932: 21.93%, f03179572: 21.67%

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

[datacap-bot[bot]]

Issue information change request has been approved.

[ipfsforcezuofu]

@MayFBWY

Could you review the compliance report and explain issues including the high duplicate deal rate, the blank retrieval rate for SP f03229932 and the omission of one SP that was initially planned?

[datacap-bot[bot]]

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

[MayFBWY]

@ipfsforcezuofu

1. We are very confused about the duplicate transaction problem of the compliance report. This time, we distributed 4 copies of 100T data to 4 SPs respectively. First, we repeatedly checked the original data files and confirmed that there were no duplications. Then we checked the order files to the SPs and also checked that there were no duplications. I don’t understand where the problem is. Can you verify it on the chain to see where the duplication is? (The picture is a part of our data file. I can email you the original 100T file for your reference)

2. As for the blank search rate of SP f03229932, we have communicated with the SP, and they will check the network and hardware conditions and adjust them as soon as possible;

3. We missed an SP in the original plan. We have explained this before. Maybe you have forgotten this part of information;

In addition, in the next batch, SP: f03178077 means that their storage hardware is fully packaged, so we will terminate the cooperation. We will continue to seek SPs with better reputations to join. If you have any questions, please feel free to contact me. Thank you very much!

[MayFBWY]

Good afternoon: Attached are the original files and order files of our 100T and 4 nodes. Please help me check them. Thank you very much!

At 2024-11-04 14:50:10, "Jimmy Zhang" @.***> wrote:

@MayFBWY

Could you review the compliance report and explain issues including the high duplicate deal rate, the blank retrieval rate for SP f03229932 and the omission of one SP that was initially planned?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[ipfsforcezuofu]

@MayFBWY Thank you for your clarification. I am satisfied with the explanations for questions 2 and 3. Regarding the high duplicate rate, we double-checked the claim file generated from the blockchain and found no duplicate data either. We believe it might be related to a similar reporting issue as indicated in this report.