[Allocator Application] <FIL DDC>< FIL DDC> PR #49

[martapiekarska]

Allocator Application

Application Number

recFTFrH48qj5W0J1

Organization Name

FIL DDC

Organization On-chain Identity

f410f63ekberkmzacs35vy3fe36o6jmw4duxco2tdy6y

Allocator Pathway Name

FIL DDC

Github PR Number

49

Region of Operation

Asia minus GCR,Greater China Region

GitHub ID

Hannason

On-chain address

I will provide an address on a later date

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 - Social media, WeChat

Allocator Description

Contributions to EcosystemOnboard >10PiBs of Data,Build better data onboarding pathway

Monetization and Fee structure

Client fees,SP fees,Block rewards, pools.

Target Clients

Individuals,Commercial/Enterprise,Open/Public

Client Diligence Check

3rd party Know your customer (KYC) service,Manual verification,Proof of provenance

Description of client diligence

- 身份信息收集：要求客户提供官方身份证明文件，如身份证、护照、营业执照（针对企业客户）等的清晰扫描件或照片，并通过权威的身份验证服务进行核实，确保证件真实性与客户身份匹配。例如，利用政府部门开放的身份验证 API，输入客户提供的证件号码等关键信息，获取核实结果。
 
- 背景调查：对个人客户，查询信用记录、犯罪记录等公共数据库（在合法合规前提下），了解其过往信用表现与潜在风险；对于企业客户，调研其商业登记信息、经营历史、涉诉情况，查看企业注册地工商局网站、法院裁判文书网等官方渠道信息，评估企业信誉与稳定性。
 
- 初始沟通与问询：安排专业客服或客户经理与客户进行初次电话或视频沟通，询问其业务需求、使用产品/服务的预期用途，观察客户回应的逻辑性、专业性，判断其诚意与真实诉求，同时做好沟通记录留存。
 
减轻语言攻击的方法
 
- 内容过滤系统：部署智能文本过滤软件，基于自然语言处理（NLP）技术和预定义的攻击性词汇、语句模板，对客户在交互过程中的输入内容（如咨询、投诉、评论等）进行实时筛查，一旦识别到潜在攻击语言，提示客户修改或直接屏蔽，同时记录日志以便后续分析。
 
- 人工审核兜底：当自动化过滤系统对某些模糊语义难以判断时，设立人工审核岗，由经验丰富的人员快速浏览可疑内容，结合语境判断是否属于攻击性表达，确保精准处理，避免误判影响客户体验。
 
- 反馈与教育机制：若发现客户使用攻击性语言，及时通过温和的反馈告知其行为不妥，引导文明沟通，对于屡教不改者采取限制交互权限等措施；定期向全体客户推送文明沟通指南、常见问题解答，提升客户整体素质。
 
自动化途径的速率限制与确定性
 
- 速率限制设定：如果采用自动化验证流程，如频繁的身份信息自动查询，为防止过度请求导致系统故障或被外部封锁，根据外部数据源提供商的要求及自身系统承载能力，设定合理的每小时/每天查询上限。例如，针对某身份数据库，每天最多发起 1000 次查询，当接近阈值时暂停新的查询请求，等待下一个周期。
 
- 确定性保障：采用多重验证数据源与算法确保验证结果可靠。例如，除了单一的身份验证数据库，还结合社交账号关联验证（若客户授权），通过比对多个渠道信息的一致性来增强确定性；对于关键验证结果，引入人工复核环节，抽查一定比例样本，保证不出差错。
 
验证企业或付费客户数据所有权声明的真实性
 
- 文件审查：要求企业客户提供能证明数据所有权的相关文件，如原始数据采集协议（若从第三方采集）、内部数据生成流程说明、研发记录等，组织法务和专业技术人员审查文件的合法性、完整性与逻辑连贯性。
 
- 数据溯源：利用区块链技术（若适用）或内部数据管理系统的日志追溯功能，跟踪数据的起源、流转过程，查看是否与企业所宣称的所有权路径相符，确保数据不是非法获取或存在权属争议。
 
- 第三方验证：如有必要，聘请独立的第三方数据审计机构，对企业的数据所有权进行专项审计，凭借专业知识与资源，深入调查数据来源、使用权限等，出具权威审计报告。
 
向治理团队提供证据和证明以审计客户尽职调查
 
- 尽职调查报告档案：建立完备的客户尽职调查档案库，将每个客户的身份验证资料、背景调查结果、沟通记录、审核意见等按统一格式整理归档，方便治理团队随时调阅抽查，了解全过程。
 
- 审计指标可视化：开发内部审计仪表板，将客户尽职调查的关键指标，如身份验证通过率、风险客户比例、调查平均耗时等以图表形式展示，直观反映工作成效与动态变化，同时提供数据导出功能，供深入分析。
 
- 定期汇报与案例分享：每月或每季度向治理团队进行专项汇报，总结客户尽职调查工作开展情况，选取典型案例（包括合规范例与问题案例）进行详细剖析，阐述处理过程与经验教训，便于团队持续优化流程。

Type of data

Public, open, and retrievable

Description of Data Diligence

文档记录类
 
- 客户信息收集表：包含客户基本信息、联系方式、业务范围、行业信息等详细内容的表单，显示已全面收集客户基础资料。
 
- 身份证明文件副本：客户提供的身份证、护照、营业执照等证明文件复印件，证明对客户身份的核实。
 
- 授权书与声明：客户签署的授权同意进行尽职调查的文件，以及关于所提供信息真实性的声明书，体现合规操作流程。
 
调查与分析报告类
 
- 背景调查报告：由专业调查机构或内部团队出具的关于客户信用状况、经营历史、涉诉情况等的报告，展示对客户背景的深入调查。
 
- 风险评估报告：基于收集的信息和调查结果，对客户进行风险评级的报告，说明对客户风险的评估过程和结论。
 
- 数据所有权审计报告：针对企业客户数据所有权声明进行审计后出具的报告，证实数据来源和权属的真实性。
 
沟通与记录类
 
- 沟通记录：与客户的邮件、电话、会议等沟通记录，包括询问的问题、客户的回答等，证明与客户有充分的信息交互。
 
- 问题反馈与处理记录：对客户提供信息存在疑问或发现问题时的反馈记录，以及客户的解释和处理结果，显示对问题的跟进和解决。
 
系统与技术类
 
- 验证系统日志：身份验证、数据溯源等系统的操作日志，记录了验证的时间、对象、结果等信息，证明验证工作的执行。
 
- 数据存储与访问记录：存储客户数据的系统记录，显示数据的存储位置、访问时间、访问人员等信息，保证数据的可追溯性。
 
培训与制度类
 
- 培训记录：员工参加客户尽职调查相关培训的记录，包括培训内容、培训时间、考核成绩等，证明团队具备专业能力。
 
- 内部制度与流程文件：公司制定的客户尽职调查相关制度、操作流程手册等文件，体现有规范的工作流程和标准。

Data Preparation

Client-provided,IPFS Kubo

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.

第一部分：100 TiB
• 第二部分：200 TiB
• 第三部分：400 TiB
• 第四部分：1000 TiB

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

Yes, some tools

GitHub Bookkeeping Repo Link

https://github.com/filecoin-project/Allocator-Governance

Success metrics

Number of clients,Amount of data onboarded, daily & aggregate,Number of paid deals,Retrievability of data

Timeline to begin allocating to clients

1 week from RKH approval

Funnel: Expected DataCap usage over 12 months

50-75PiB

Risk mitigation strategies

数据加密、访问控制、网络安全防护、行为规范、知识产权保护、内容检测警报、异常行为警报、声誉检测警报等等

Dispute Resolutions

DAYOU

Compliance Audit Check

Audit Check第三方审计报告、自我评估报告、实时合规监控仪表板、历史趋势仪表板、数据日志与记录等等

Compliance Report content presented for audit

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

Connections to Filecoin Ecosystem

Storage provider

Slack ID

Hannason

[Kevin-FF-USA]

Hi @hannoson,

Thanks for submitting this application. Have a request, can you please summit a version of this application translated to English? Due to the tooling and Governance teams which are reviewing in English, I'm concerned that if I make the translations something could get crossed from your original intent.

I could see that this pathway is developing an automated pathway. Thats great! Looking forward to it. Also wanted to flag an option that may help you in the development. #313. The experimental pathway could be an option if you dont yet have a working MVP.

[Kevin-FF-USA]

🚀 New Opportunity: Apply to the Experimental Allocator Pathway! 🚀

Hi @hannoson,

Wanted to reopen this application 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 Update:
If you submitted (or plan to submit) an Allocator Application under a RFA (Request for Allocator) process but would now like to submit to operate as a Manual pathway. The Experimental Pathway will not apply to MANUAL Pathways.

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.

✅ In the meantime, you are still welcome to apply to the Experimental Pathway if your project fits the criteria (RFA,active repo, ready-to-test experiments).

📣 Next Steps:
If you think your current application or your team's work fits the experimental model, apply now!
This is a fantastic opportunity to validate ideas faster and get on track for longer-term participation in the ecosystem.

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

Looking forward to great things! 🚀