[Allocator Application] <Xman Team>< Xman Allocator> PR #160

[martapiekarska]

Allocator Application

Application Number

rec4wyj4g7HLMux57

Organization Name

Xman Team

Organization On-chain Identity

f1rto7zthkzfazt7baq6kpls4mozpmh2m7oxehcqy

Allocator Pathway Name

Xman Allocator

Github PR Number

160

Region of Operation

Greater China Region,Asia minus GCR

GitHub ID

Finonaa

On-chain address

I would like the governance team to create a multisig for me

Type of Allocator

RFA

Filecoin Community Agreement

As a member in the Filecoin Community, I acknowledge that I must adhere to the Community Code of Conduct, as well other End User License Agreements for accessing various tools and services, such as GitHub and Slack. Additionally, I will adhere to all local & regional laws & regulations that may relate to my role as a business partner, organization, notary, allocator, or other operating entity
Acknowledge

Type of Allocator and RFA List

RFA: Automated - GitHub

Allocator Description

Contributions to EcosystemBuild better data onboarding pathway,Data Stewardship: Curate and provide high-quality datasets to be stored on the Filecoin network, enhancing the overall value and utility of the network.

Monetization and Fee structure

Client staking,SP fees,Client fees.

Target Clients

Web3 developers,Commercial/Enterprise,Nonprofit organizations,Open/Public,Individuals

Client Diligence Check

3rd party Know your business (KYB) service,3rd party Know your customer (KYC) service,Manual verification

Description of client diligence

Our pathway verifies clients and establishes initial trust through a multi-step approach:
Verification Mechanism: We utilize a comprehensive verification process that includes identity verification, background checks, and validation of business credentials for enterprise clients.
Mitigating Sybil Attacks: To prevent sybil attacks, we implement rate limits and deterministic checks in our automated verification system. This ensures that each entity is verified based on unique, identifiable criteria before datacap allocation.
Authenticity Verification: For enterprise or paying clients, we validate data ownership claims through documentation review, including contracts and digital signatures. This ensures the authenticity and legitimacy of the data stored on Filecoin.
Audit Trail: We maintain detailed records and evidence of our client diligence process. This includes providing auditable proof to the Governance Team, demonstrating compliance with regulatory requirements and best practices in data security and privacy.
This approach ensures robust client verification and trust establishment, safeguarding against potential security risks and ensuring integrity within the Filecoin ecosystem.

Type of data

Public, open, and retrievable

Description of Data Diligence

How to Execute Data Due Diligence to Verify Clients:
First, prior to collaboration, we will verify client identities through domain email, KYC, and KYB processes. After establishing cooperation, we will fully utilize the check-bot’s functionality to review check data before each round of signing. We will mainly observe whether the SP's disclosures align with actual cooperation, whether there is CID sharing, the proportion of DC obtained by the SP, and the level of support for Spark. If any doubts arise, we will suspend signing until the client provides a reasonable explanation. If the client fails to resolve the issues, we will cease support for them.
Second, we have a dedicated legal compliance team responsible for monitoring and ensuring that our data processing activities comply with local and regional legal requirements. Additionally, we have established clear data protection policies and implemented appropriate technical and organizational measures to ensure the confidentiality, integrity, and availability of data. We also conduct regular risk assessments and compliance reviews to ensure our data processing activities meet local and regional legal standards.
Types of Data Sampling and Tools Used to Confirm Data Consistency:
We employ random sampling methods to regularly check and verify the data provided by clients. For instance, before each round of signing, we will download 10 sectors, decompress the data, and compare it with the source data provided by the client. We also use professional data audit tools, such as integrity checks, to confirm that the data is consistent with the initial declarations.

Data Preparation

Singularity,Go-CAR,Other existing ecosystem tooling

Replicas required, verified by CID checker

5+

Distribution required

Equal distribution of deals across regions

Number of Storage Providers required

5+

Retrieval Requirements

Public data highly retrievable over Spark.

Allocation Tranche Schedule TypeManual or other allocation schedule.

Initial Maximum for Each Client: Clients in the initial stages may be subject to restrictions on the overall cap to ensure fair distribution and prevent misuse. This initial cap can gradually increase as the client's participation and reputation grow in the network.
Dynamic Adjustment of Overall Cap: With improvements in a client's performance and reputation within the Filecoin network, the overall cap can be dynamically adjusted. This encourages clients to contribute valuable data and actively engage in the Filecoin ecosystem.
Allocator Always Follows a ""Limited Trust Over Time"" Approach: More Datacap is gradually released over time based on the time process, such as doubling the rate from the previous round. For example:

First Round: 512 TiB
Second Round: 1 PiB
Third Round: 2 PiB
Fourth Round: 2 PiB
Overall Cap for Each Client: (2 PiB)

Will you use FIDL tooling, such as allocator.tech and other bots?

Yes, all available tools

GitHub Bookkeeping Repo Link

https://github.com/Finonaa/Allocator-Governance

Success metrics

Number of clients,Retrievability of data,Speed of allocations (TTD),Amount of data onboarded, daily & aggregate

Timeline to begin allocating to clients

1 week from RKH approval

Funnel: Expected DataCap usage over 12 months

75-100PiB

Risk mitigation strategies

To protect our organization, reputation, and pathway for our specialized online education Filecoin allocator, we will implement robust risk mitigation strategies:

Operational Security (OpSec) Standards: Adhere to industry best practices for OpSec, including regular security audits, encryption of sensitive data, and access control measures to safeguard against unauthorized access.

User Agreements: Require clients to sign comprehensive user agreements outlining acceptable use policies, data ownership rights, and compliance with legal regulations such as GDPR and FERPA. These agreements ensure clarity and accountability in data handling practices.

Alert Systems: Implement real-time monitoring and alert systems to detect suspicious activities or anomalies in DataCap utilization patterns. Alerts will trigger immediate investigation and response to mitigate potential threats or abuse.

Throttling Mechanisms: Employ rate limiting and throttling mechanisms to control and limit the speed or frequency of data transactions, preventing overload scenarios or abusive usage patterns that could compromise network stability or performance.

Audits and Compliance Checks: Conduct regular audits of client accounts and data transactions to verify compliance with contractual obligations and regulatory requirements. These audits provide assurance of data integrity, security, and legal compliance.

Education and Training: Provide ongoing education and training to clients on best practices for secure data storage and management on Filecoin. This empowers clients to uphold security standards and mitigate risks from their end.

Incident Response Plan: Develop and maintain an incident response plan outlining procedures for handling security incidents, including communication protocols, escalation paths, and post-incident reviews to continuously improve response effectiveness.

Reputation Management: Monitor online reputation and feedback channels to promptly address any issues or concerns raised by clients or stakeholders. Swift resolution and transparency demonstrate commitment to maintaining trust and credibility.

By implementing these risk mitigation strategies, we aim to protect our organization, uphold our reputation, and maintain the integrity of our Filecoin allocator pathway dedicated to serving the online education sector securely and responsibly.

Dispute Resolutions

Response time: within 48 hours. Upon receipt of relevant dispute information, I will initiate the process of handling the dispute within 48 hours.
Transparency: I will create the proposal on GitHub or Google Public Forms and allow parties to leave comments and submit evidence below the proposal.
Dispute communication: Slack or Zoom online meetings. All parties are encouraged to communicate via Slack or Zoom online meetings to express their views and opinions.
Accountability Mechanism: If a customer violates the law, penalties will be applied, including deletion of the remaining DataCap credits, blacklisting of the customer and the SP, and barring the customer from reapplying.

Compliance Audit Check

Regular checking: Check the utilization of DataCap regularly.

Track DataCap allocation metrics: Utilize tools such as datacapstats.io, CID checker bots, etc. to monitor DataCap allocation and usage, focusing on key metrics such as DataCap residuals, allocation frequency, and more.

Monitor time metrics: Track time patterns of client DataCap usage, such as frequency and duration of use, to ensure proper allocation. Regularly assess whether clients are completing data storage and usage on time to manage DataCap effectiveness.

Trust Assessment: Conduct an initial trust assessment of new customers, including their historical credit history and business reputation. When they demonstrate compliance and reliability, their trust score, as well as their DataCap allocation, increases.

Use tools such as CID Checker/Retrievability Bot: Utilize tools such as CID Checker to validate the data stored by the client to ensure it matches the declared data. Retrievability bots can be used to monitor and verify the retrievability of data and ensure that clients are adhering to storage protocols.

Compliance Report content presented for audit

Success metric: onchain report of data onboarded,Client Diligence: Client statements, client provided verification,Client Diligence: KYC/KYB report on clients,Data Compliance: Data Samples,Data Compliance: Manual report,Compliance: CID report,Client/Data Compliance: external third-party audit ,Client Diligence: Legal Review documents,Success metric: onchain data report,Client Diligence: Financial Audits and Credit Check reports,Data Compliance: Proof of provenance report.

Connections to Filecoin Ecosystem

Storage provider,Big data contributor,Developer

Slack ID

Mee

[Kevin-FF-USA]

Hi
Thanks for applying to serve as an Allocator in the Filecoin Plus Program.
In looking at this application, the TYPE OF ALLOCATOR is currently set to REQUEST FOR ALLOCATOR (RFA). Based on the details in application, this reads like a Manual review pathway. Can you please describe what type of Allocator pathway you wish to operate as?

For more details on the types of Allocators please check out this blog.
https://blog.allocator.tech/2024/04/allocator-tech-blog.html

[Kevin-FF-USA]

For MANUAL pathways, would like to make you aware that these types of applications are being processes as the network need becomes available. Currently there are ~50 pathways available for Manual reviews, so the priority for onboarding new Allocators is to pathways doing something novel to support the network.

[Kevin-FF-USA]

Hi @Finonaa,

Wanted to check in and see if you were still interested in this application. Able to join one of the recent calls?
In reading this description, it sounds like this indeed a Manual pathway. If so, many of the detail fields are either empty or lacking detail that would give a score high enough to onboard as a new Allocator.

Recommending a few options.

1. Check out some of the other applications and the details of their program. Specifics are key - how will this pathway be measured for success and diligience. Right now, there is not much detail. Here is an example of a recently onboarded Application .

2. If you have clients you can demonstrate this by brining them to network with an existing Allocator.
   Bring one of your clients into the ecosystem with an Existing Allocator Pathway. Establish that you have real clients and can maintain the diligence standards of this application. Demonstrate that to the community as the ability and value to onboarding this new Manual Pathway.

Steps

1. Work with any existing Allocator to create an application on behalf of your client. FIDL runs an enterprise Allocator if you were looking for a pathway with existing support in place to help with questions.

2. Once the data is onboarded, reply back to this application with the following
   1. Client ID
   2. Links to the DataCap Application
   3. Spark retrieval %
   4. Verification that the Data reached the targeted number of SP's
   5. What the data type was

Onboarding
Once the ability to onboard clients through the application process has been verified, this application will receive a KYC check and begin onboarding as an Allocator to onboard clients directly.

For questions or support

• There is a live Filecoin Plus Program call every two weeks. Calendar link is here. Or as always please tag us in issue for comment or update.

[Finonaa]

Thank you, kevin. @Kevin-FF-USA Here are the premilary structure from our manual pathway. Still should i create an application on behalf my client?

[Kevin-FF-USA]

Hi @Finonaa,
Thanks for sharing the 5W's on the pathway.

Yes, recommend you take one of your clients through an existing pathway, then comment below with this information.
Steps

Work with any existing Allocator to create an application on behalf of your client. FIDL runs an enterprise Allocator if you were looking for a pathway with existing support in place to help with questions.

Once the data is onboarded, reply back to this application with the following

1. Client ID
2. Links to the DataCap Application
3. Spark retrieval %
4. Verification that the Data reached the targeted number of SP's
5. What the data type was

[Finonaa]

Hi @Finonaa, Thanks for sharing the 5W's on the pathway.

Yes, recommend you take one of your clients through an existing pathway, then comment below with this information. Steps

Work with any existing Allocator to create an application on behalf of your client. FIDL runs an enterprise Allocator if you were looking for a pathway with existing support in place to help with questions.

Once the data is onboarded, reply back to this application with the following

1. Client ID
2. Links to the DataCap Application
3. Spark retrieval %
4. Verification that the Data reached the targeted number of SP's
5. What the data type was

Thanks Kevin. We will reply these information soon.

[Finonaa]

@Kevin-FF-USA Here is the another github account that created an application on behalf of our client.I will make a berief introduction with that github account.
Client ID ：xcstoage
Links to the DataCap Application：AlanGreaterheat/Greaterheat-Allocator#13
[Spark retrieval %]：https://check.allocator.tech/report/AlanGreaterheat/Greaterheat-Allocator/issues/13/1730946919308.md
Verification that the [Data reached the targeted number of SP's]: Consistent with the SP information submitted previously
What the data type was： V8-Smart Video
Tips: The retrieval rate will be improved gradually, it is just the beginning.

[Finonaa]

@Kevin-FF-USA

[Finonaa]

@Kevin-FF-USA Any update here?

[Kevin-FF-USA]

Hi @Finonaa

Thanks for the ping.

To make you aware of timelines and process - for Manual review pathways the program already has 60+ pathways available for clients to choose from. As such, resourcing is not being invested into onboarding additional manual pathways, hence the RFA issued for the automated pathways.

One point to clarify - application is for an Automated pathway that links to Github.
Is that still the case? If so, can you please link the technical manuals for how this will be setup and operate?
If this pathway will only serve as a Manual, I will mark it as Manual and leave on record for a time when additional Manual pathways are needed to support client demand.

[Finonaa]

Hi @Finonaa

Thanks for the ping.

To make you aware of timelines and process - for Manual review pathways the program already has 60+ pathways available for clients to choose from. As such, resourcing is not being invested into onboarding additional manual pathways, hence the RFA issued for the automated pathways.

One point to clarify - application is for an Automated pathway that links to Github. Is that still the case? If so, can you please link the technical manuals for how this will be setup and operate? If this pathway will only serve as a Manual, I will mark it as Manual and leave on record for a time when additional Manual pathways are needed to support client demand.

@Kevin-FF-USA Thanks for your reply. We still want apply the Manual pathway.

[Kevin-FF-USA]

Hi @Finonaa ,
Just a friendly check in to keep you updated.

• I've updated the labels for this application FROM AUTOMATED and changed to MANUAL.

• The next Fil+ Community Allocator Governance call is scheduled for Feb 18.
  One of the points we will be discussing is the prioritization of onboarding new pathways that only operating as Manual. (These Manual pathways have been deprioritized for onboarding due to the existing 60+ pathways already operating )

• Applications (like this one) that are bringing clients through an existing Pathway to demonstrate compliance and ability should be able to meet all standards in their application (Spark retrieval, Diligence Records, etc). If there was anything you would like to enhance in your clients, please work to do so by 18Feb.

Again, thank you for your interest in the Fil+ program and please let me know if there is anything I can do or share for you, otherwise I look forward to chatting with you on the 18Feb calls.

Warmly,
-Kevin

[Finonaa]

Hi @Finonaa , Just a friendly check in to keep you updated.

• I've updated the labels for this application FROM AUTOMATED and changed to MANUAL.
• The next Fil+ Community Allocator Governance call is scheduled for Feb 18.
  One of the points we will be discussing is the prioritization of onboarding new pathways that only operating as Manual. (These Manual pathways have been deprioritized for onboarding due to the existing 60+ pathways already operating )
• Applications (like this one) that are bringing clients through an existing Pathway to demonstrate compliance and ability should be able to meet all standards in their application (Spark retrieval, Diligence Records, etc). If there was anything you would like to enhance in your clients, please work to do so by 18Feb.

Again, thank you for your interest in the Fil+ program and please let me know if there is anything I can do or share for you, otherwise I look forward to chatting with you on the 18Feb calls.

Warmly, -Kevin

Thank you Kevin. we will meet all standards in the application (Spark retrieval, Diligence Records, etc).And would like to attend the call.

[Finonaa]

What should i do for the new update for the allocator application? @Kevin-FF-USA

[Kevin-FF-USA]

Hi @Finonaa

Continuing to work through the applications received to provide input and testing on new pathways. Just wanted to send a friendly check in on this application to keep you updated.

At top - Manual pathways are NOT being prioritized for new onboarding. That may change in the coming Quarters - but currently there are 60+ active available pathways providing this service so bandwidth is not being allocated to additional Manual pathways (at this time). Applications who have demonstrated ability of shepherding a client through an existing Allocator Pathway will be held in waiting, for a time when new Manual Pathways are needed.

Pathways developing a new https://blog.allocator.tech/2024/04/allocator-tech-blog.html will be held until there is a workable MVP and testing to prove that the pathway can operate without Manual review. If DC is needed for testing please see. https://faucet.allocator.tech/.

In Q2 the program will publish an updated Application form to better fast track this type of onboarding, along with a dedicated pipeline for reviews and audits. We will keep updates as the technical teams responsible for this work completes their engineering build out for this review process.

If you have any questions or would like to discuss, please join us at the next Governance Call. #297
(you will be able to find recordings and link to slides in this issue as well)

[Kevin-FF-USA]

Hi @Fatman13

Wanted to share comms to ensure you were aware of the new Experimental Allocator Pathway which is now live! 🎉. This is a new way for teams actively developing in the ecosystem to apply for DataCap specifically to experiment, test, and validate their solutions. Here is a short 5m explainer video about the pathway -> https://youtu.be/oXFxrt4Bnxo

For details about this pathway, please check out the Proposal

For Organizations who submitted Allocator Applications that didnt yet meet the standards for a full pathway onboarding (that's you if you're reading this! 👀), you are strongly encouraged to also apply to the Experimental Pathway — especially if you are looking to validate hypotheses, test system behaviors, or iterate on new allocation strategies.

🔗 How to Apply:

1. Visit the Experimental Meta Allocator site for full details.
2. Submit your application via the linked Google Form.
3. You'll receive a KYC verification link and GitHub issue creation automatically after applying.

🛠 Who Should Apply:

• Teams with tested code and an active GitHub repository.
• Projects aiming to validate clear, well-scoped experiments.
• Developers who want to move quickly and gather real-world feedback before a larger allocation.

📋 Key Requirements:

• Submit a clear proposal (hypothesis, goals, expected outcomes).
• Maintain an active GitHub repo (activity and contributions will be reviewed).
• You get up to 1PiB of DataCap for experimentation.
• Final report (success or failure) required after DataCap usage.
• You must wait 6 months before reapplying unless major changes are made.
• Successful teams will be asked to submit a third-party audit post-experiment.

📝 Manual Pathways Note:
THE EXPERIMENTAL PATHWAY DOES NOT APPLY TO MANUAL. If you submitted (or plan to submit) an Allocator Application under the RFA (Request for Allocator) but would now like to modify/submit to operate as a Manual pathway. This Experimental Pathway will NOT APPLY and should not be used.

We are updating the Manual application process to align with the new Meta Allocator standards.
You should wait for the release of the updated application form, which will provide new, clear guidance on how Manual applications will proceed going forward.

📣 Next Steps:
✅ In the meantime, you are welcome to apply to the Experimental Pathway if your project fits the criteria (RFA,active repo, ready-to-test experiments). https://www.fidl.tech/apply-for-datacap_1n. If you think your current application or your team's work fits the experimental model, apply now!

Come to the next Governance Meeting for updates and questions.
#342

Looking forward to great things! 🚀