Skip to content

[DataCap Refresh] <4th> Review of <Media Platform Data - MetaEra> #413

@metaeraworkops

Description

@metaeraworkops

What type of Audit did you opt into? Choose from dropdown

Enterprise Data

What is your JSON hash (starts with 'rec')

recbeZT0dD7VqvcMm

Link to your allocator operations description

metaeraworkops/MediaPlatformData#11

Compliance Report

https://datacapstats.io/allocators/f03014641/reports/702865ef-e674-4ac5-a4b7-d28a1bcb65b8

Previous Reviews

Client Allocation Table

Client name DC granted
Edward - ABGA 3 PiB
Mody - Blocklike 0 PiB
CathySun - Knowehere 0 PiB

Client-specific Breakdown

Client 1

I. Edward - ABGA

  • DC requested: 6 PiB
  • DC granted so far: 3 PiB

II. Dataset Completion
(Provide deal(s) containing sample(s) of data)
https://medium.com/@ABGAasia

III. SP Match
(Does the list of SPs provided match the list in the CID report?)
YES, Match

IV. Replica Count
Promised vs delivered:
7 vs 7

V. SP Retrieval Performance

SP ID % retrieval Meets >75%?
ID f03385456 58.6 NO
ID f03402285 46.63 NO
ID f03385462 7.4 NO
ID f03402308 22.39 NO
ID f03402347 3.08 NO
ID f03402379 2.05 NO
ID f03321512 0 NO

Client 2

I. CathySun- Knowwhere Media

  • DC requested: 10PiB
  • DC granted so far: 0 PiB

Status: The client has completed the KYC process using the official tool. (metaeraworkops/MediaPlatformData#5 (comment))
They are contacting SPs that can upload data simultaneously, and my requirement for them is at least four nodes to start.

II. Dataset Completion
(Provide deal(s) containing sample(s) of data)

III. SP Match
(Does the list of SPs provided match the list in the CID report?)

IV. Replica Count
Promised vs delivered:

V. SP Retrieval Performance

SP ID % retrieval Meets >75%?
f05678 91% YES

I. Mody - Blocklike

  • DC requested: 5 PiB
  • DC granted so far: 0 PiB

Status
This media company has cooperated with us in the industry a long time ago, so we know them well. When my channel did not have sufficient dc, I also recommended them to apply for other channels.
Because my previous account was cancelled, their past application records disappeared, but I will disclose the KYC certification process again in the application form.

Notes from the Allocator

This is a new account. In January, we underwent internal personnel changes, and the former colleague responsible for this business left the company. As a result, the associated account was deactivated. On January 16, I submitted a new application to the official team to replace the previous GitHub account. This channel was restored for use on February 28, taking a total of 43 days. Here is the link: filecoin-project/Allocator-Registry#373 (comment)

The last allocation top-up for this channel occurred at the end of December:
#262, with an additional 5 PiB granted.
3rd Review
Outcome: 5 PiB
Since this issue was submitted under the previous account, it is no longer accessible after the account was deactivated. However, the response records should still be available in Kevin’s email.

Between the last allocation top-up and the deactivation of the previous account, we signed only one approval—granting 1 PiB to Blocklike on January 10.
P.S. I have asked Blocklike to resubmit their application, and their requested quota has been adjusted to account for the previously granted allocation.

Issues or discrepancies reported?

Through this link: (https://datacapstats.io/allocators/f03014641), you can see that my channel has processed five allocation applications so far, covering four different clients. The details are as follows:
1. CaptaiNLP – The first client. Due to allocation review issues and their collaboration node situation, no further allocations were made after July 2024, and the application was closed.
2. Hepta – The second client. Similar to the first, this was during the early stages of the allocator model. After August 2024, they did not continue requesting allocations, and we closed the application.
3. ABGA – The third client, also the early-stage application of Edward. The new application continues the previous allocation, and we maintain good communication. Their sealing performance has been excellent.
4. Blocklike – The fourth client, also Mody - Blocklike’s first application. At that time, we approved 2.7 PiB for them. The new application is now in the process of being handled.

Steps to minimize unfair or risky practices

During the client verification phase, we will leverage our media industry resources to verify and introduce new clients for storage. New clients will also be required to use the official KYC tool to authenticate the legitimacy of their accounts.
For their sealing activities, we will require them to disclose all updates in advance and closely monitor their check reports. If any inconsistencies or illogical issues arise, we will mandate adjustments or suspension and provide corresponding evidence.

Value to the Filecoin ecosystem

We plan to lead by example by uploading our own company’s data to the network, encouraging more media companies to adopt Filecoin for storage and achieving a stronger promotional impact. We are also reaching out to trusted storage platforms to facilitate this initiative, which is one of our short-term plans. More details will be announced in the future.

Confirm you maintained your application standards for all client allocations

Yes

Do you understand that a diligence review will follow and require updates to this issue?

Yes

Metadata

Metadata

Assignees

Labels

Awaiting Response from AllocatorIf there is a question that was raised in the issue that requires comment before moving forward.RefreshApplications received from existing Allocators for a refresh of DataCap allowance

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions