Type of allocator:
What is your overall diligence process? Automated (programmatic), Market-based, or Manual (human-in-the-loop at some phase). Initial allocations to these pathways will be capped.
Manual
Amount of DataCap Requested for allocator for 12 months:
70P
Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing?
In order to prevent customers from malicious use or abuse of DataCap, we will carefully review customers, examining their needs, and allocate them on demand. So I first specify some rules to figure out the true identity of the applicant.Browse its official website to get a general understanding of the company or individual.
Browse its official website to get a general understanding of the company or individual. If necessary, go to the company for on-site inspections and review whether the data is valid.
Check the company's registration information on relevant government websites to ensure that the information submitted is true.
Ask some questions to understand the applicant's position/organization/plan/use case, etc.
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, or other operating entity. *
You can read the Filecoin Code of Conduct here: https://github.com/filecoin-project/community/blob/master/CODE_OF_CONDUCT.md
Acknowledgment: Acknowledge
Cient Diligence Section:
This section pertains to client diligence processes.
Who are your target clients?
Individuals learning about Filecoin,Small-scale developers or data owners,Enterprise Data Clients
Describe in as much detail as possible how you will perform due diligence on clients.
In order to ensure the fairness and justice of DataCap distribution, we have formulated separate online and offline application procedures based on the number of DataCap applications and individual and corporate users.
For individual users:
We will review their Github registration years (180 days at least) to prevent malicious application bots. The amount of approval will also be controlled below 5 TiB.
For business users:
We have developed different review methods and requirements based on the number of their DataCap applications.
If it is less than or equal to 5TiB, we will use online review. The following points will be reviewed.
• Business license
• Enterprise authorization letter (CEO's signature + seal)
• All shareholders who account for more than 25% of the total number of shareholders must provide ID cards or passport photos.
• Sample data submission (accounting for 0.2% of its total DataCap requests)
If the application is larger than 5TiB, we will add offline comments based on online surveys (visit customers on business trips or invite them to our company).
Enterprise business type
• data source
• Data volume (monthly)
• What companies think about Filecoin
• Data storage plan
Complete automated approvals by filling out a request form.
Please specify how many questions you'll ask, and provide a brief overview of the questions.
Question:
Please introduce yourself and your personal information on social media (official website, WeChat, LinkedIn,, GitHub).
• What is the purpose of your application for DataCap?
• Please provide the wallet address you want to apply for DataCap
• Please provide the quota of Datacap you want to apply for.
• Please provide the name of the organization, nationality, country of registration, time of registration, name of the executive, and relevant website (if you are an institutional user).
• Please provide the region where you want to use DataCap, if it is more than one region, please pay attention.
• How many miners do you plan to distribute DataCap to, if there are specially designated miners, please pay attention.
• Have you assigned DataCap before? If so, please provide details.
https://docs.google.com/spreadsheets/d/1ZZVv7ubFyXG8jdx6lXQi48yJ2U1MdjVzpMFwhIF9rXE/edit#gid=2015743766
Will you use a 3rd-party "Know your client" (KYC) service?
Ｙｅｓ．Toggle is the appropriate one that i used.
Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)
Any client．It is a fully open and inclusive access.We encourage diversity programs come to filecoin.
How do you plan to track the rate at which DataCap is being distributed to your clients?
Real-time tracking on DC distribution, integrates and uses multiple open sourced tooling. The number of DC allocations by the same client shall not exceed 30% of the total number. And the allocated DC amount does not exceed 2P. The time allocated is a working day. The distribution speed is to complete the review questions and answers to obtain DC.
Data Diligence
This section will cover the types of data that you expect to notarize.
As a reminder: The Filecoin Plus program defines quality data is all content that meets local regulatory requirements AND
• the data owner wants to see on the network, including private/encrypted data
• or is open and retrievable
• or demonstrates proof of concept or utility of the network, such as efforts to improve onboarding
As an operating entity in the Filecoin Community, you are required to follow all local & regional regulations relating to any data, digital and otherwise. This may include PII and data deletion requirements, as well as the storing, transmitting, or accessing of data.
Acknowledgement: Acknowledge
What type(s) of data would be applicable for your pathway?
Public Open Dataset (Research/Non-Profit),Public Open Commercial/Enterprise,Private Commercial/Enterprise,Private Non-Profit/Social Impact
How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
First, we will require the applicant to provide the corresponding business license, relevant information of the company's legal person, facial recognition, tax bill, and the corresponding legal certificate of the location of the data storage server to verify the company's application entity information. Secondly, applicants are required to provide relevant proof of data ownership, and the data samples provided must account for 20% of the total application quota.Finally, only through KYB information verification can the data applicant's information be proven. The public and enterprise client must be open and transparent。
How will you ensure the data meets local & regional legal requirements?
We will check local legal requirements. Data that does not comply with the law will be rejected directly.If some data that we can't be sure is legal or not, we will disclose it to the community. Even to the notary call.
What types of data preparation will you support or require?
We will support text, graphic images, video, audio, numbers, AI, GIS, hot and cold data, etc.
What tools or methodology will you use to sample and verify the data aligns with your pathway?
We will initiate a retrieval request to the SP and randomly access some sectors for spot checks.
Data Distribution
This section covers deal-making and data distribution.
As a reminder, the Filecoin Plus program currently defines distributed onboarding as multiple physical locations AND multiple storage provider entities to serve client requirements.
How many replicas will you require to meet programmatic requirements for distribution?
5+
What geographic or regional distribution will you require?
At least 3 geopolitical regions，each replica at different physical location, no or minimal VPN, different SP owner operators.
How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?
5+
Do you require equal percentage distribution for your clients to their chosen SPs? Will you require preliminary SP distribution plans from the client before allocating any DataCap?
The proportion does not exceed 25%, and the SP is required to do the KYB and provide a distribution plan and obey it . Then it should publicly disclose through comments on Github.
What tooling will you use to verify client deal-making distribution?
By far, the most convenient way is through the CID Checker, AC bot and datacapstats.io
How will clients meet SP distribution requirements?
Yes.we will use programmatic (such as software or smart contract) deal distribution to set of vetted and reputable SPs.
As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
I use a list of common VPN server IP addresses to filter whether a VPN is used.I am Willing to support SPs that utilize VPNs, but requires additional KYB checks and enforces distribution.
DataCap Allocation Strategy
In this section, you will explain your client DataCap allocation strategy.
Keep in mind the program principle over Limited Trust Over Time. Parties, such as clients, start with a limited amount of trust and power.
Additional trust and power need to be earned over time through good-faith execution of their responsibilities and transparency of their actions.
Will you use standardized DataCap allocations to clients?
Yes, standardized
Allocation Tranche Schedule to clients:
• First:1. Review the information in the application form
• Second:2. Ask the questions in Q12 above regarding the application
• Third:3. Review the answers to the questions and ask further questions based on the answers. It is required to list data samples of no less than 20% of the total applied DC quota.
• Fourth:4.Verify the authenticity, legality, and data size of the stored data type.
• Max per client overall:2P
All the information and decisions should be open and transparency.
Will you use programmatic or software based allocations?
Yes, standardized and software based
What tooling will you use to construct messages and send allocations to clients?
Describe the process for granting additional DataCap to previously verified clients.
Applicants are required to distribute Datacap to at least 4 or more miners, which will increase storage redundancy and help maintain decentralization and reduce the potential for abuse. The more the miner client allocates, the more the Datacap client may receive. The remaining 20% of DC can be applied for the next round. In addition, the SP retrieval rate must be more than 20%, and at least 5 copies must be stored. CID checker and AC bot will be used for inspection.
Tooling & Bookkeeping
This program relies on many software tools in order to function. The Filecoin Foundation and PL have invested in many different elements of this end-to-end process, and will continue to make those tools open-sourced. Our goal is to increase adoption, and we will balance customization with efficiency.
This section will cover the various UX/UI tools for your pathway. You should think high-level (GitHub repo architecture) as well as tactical (specific bots and API endoints).
Describe in as much detail as possible the tools used for:
• client discoverability & applications
• due diligence & investigation
• bookkeeping
• on-chain message construction
• client deal-making behavior
• tracking overall allocator health
• dispute discussion & resolution
• community updates & comms
• client discoverability & applications GitHub
• due diligence & investigation GitHub Comment
• bookkeeping Github
• on-chain message construction https://filplus.fil.org/#/
• client deal-making behavior Github CID Check Report and on-chain messaging
• tracking overall allocator health https://datacapstats.io/
• dispute discussion & resolution Google Dispute
• community updates & comms * Github & Slack
Will you use open-source tooling from the Fil+ team?
Yes,we will use the boost and Github repo.
Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
All allocation decisions will follow the guidelines published on Github. The same is true for all communications.It will be real-time update.It should be open and transparency.But for E-fil+ the information will not be disclosed.It needs the third party KYC or KYB.
Since all interactions are intended to be done publicly, most allocation decisions should be self-explanatory.
Any challenges related to allocation decisions should first be discussed publicly in the Github repository.
If the notary public can’t provide a convincing reason, it can submit a dispute resolution application to the Notary Public Administration 14 business days from the date of the initial challenge. After submitting the dispute resolution application, the notary public can appoint an arbitrator among the root key holders to resolve the dispute. According to the decision of the arbitrator, a hearing may be held within 30 business days after the dispute resolution application is made.
Risk Mitigation, Auditing, Compliance
This framework ensures the responsible allocation of DataCap by conducting regular audits, enforcing strict compliance checks, and requiring allocators to maintain transparency and engage with the community. This approach safeguards the ecosystem, deters misuse, and upholds the commitment to a fair and accountable storage marketplace.
In addition to setting their own rules, each notary allocator will be responsible for managing compliance within their own pathway. You will need to audit your own clients, manage interventions (such as removing DataCap from clients and keeping records), and respond to disputes.
Describe your proposed compliance check mechanisms for your own clients.
Datacap distribution tracking is mainly at https://filplus.fil.org/#/ and https://datacapstats.io/. Customers' DC usage can be viewed through Github's CID Report. Regarding customer tolerance, we will respond based on the most basic LDN Q&A. KYC questions and answers for customers will include company entity information, development status, data storage type, size, and SP related information.
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
First of all, when a dispute arises, we should immediately stop DC distribution to the LDN. Only when the dispute is resolved can normal distribution be carried out. When a dispute arises, the corresponding LDN should be marked and the dispute should be resolved below on GitHub. Any dispute should be handled fairly and transparently. Any distribution of DC should comply with distribution rules and audit mechanisms.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
About tooling, we will announce it on Twitter and Slack and Github.Follow the announcement process and detailed rules introduction.For new optional tools, announce availability but make opt-in. Clearly explain purpose and intended usage. Pathway Guidelines For clarifications or minor adjustments, announce via release notes on documentation page. For substantive changes, first publish a proposal for public feedback on a discussion forum. Allow 2-4 weeks for comments. If approved, announce finalized changes along with a summary of feedback received and reasoning behind decisions. Give notice period before enforcement. Process Alterations Clearly define any proposed new processes as "pilots" or "optional" at outset to avoid scope creep. For pilots, set review period to assess usefulness prior to potential incorporation as standard process.
How long will you allow the community to provide feedback before implementing changes?
I will research the proposal and ask for opinions from multiple parties, and come to a conclusion that favors the axiomatic side.For minor clarifications or bug fixes, 1-2 weeks for feedback should suffice.
For substantive changes or new proposals, 4 weeks minimum to allow broader discussion.
Actively moderate discussions to prevent domination by any single entity.
Synthesize feedback themes rather than taking a headcount approach. Consider perspectives across various stakeholder groups.
Where there are disagreements, discuss trade-offs transparently in proposal updates. Explain rationale for final decisions.
For proposals where consensus cannot be reasonably achieved, allow voting as a last resort - but only among validated members to prevent manipulation.
Continue engaging skeptics after a decision to understand concerns and refine approach over time based on experience.
Consult Fil+ Governance team proactively for guidance on complex proposals or issues lacking clear resolution from community process alone.
The goal would be fair representation rather than pure democracy or decentralization for its own sake. Moderated, thoughtful discussion aimed at consensus wherever possible seems most likely to maintain community trust over the long run.
Regarding security, how will you structure and secure the on-chain notary address? If you will utilize a multisig, how will it be structured? Who will have administrative & signatory rights?
I use a hardware wallet。Here is how I would recommend structuring and securing the on-chain notary address:
Use a multisig address requiring M-of-N signatures for transactions.
M should be sufficiently high (e.g. 3 or 4) to prevent funds loss from any single compromised signatory.
N should include 5-7 signatories total for redundancy and in case any signers become unavailable long-term.
Signatories would include technical operators plus independent compliance/oversight roles assigned by the Fil+ Governance team.
Private keys would be split and stored securely using hardware security modules (HSMs), multisig wallets, offline storage.
Regular audits of private key storage, hardware, and software would be conducted by independent assessors.
Administrative rights like adding/removing signatories would require oversight approval via governance process.
Daily operations could be handled via multisig transactions initiated by dev/ops staff.
Secure development practices like secret scanning, access control, logging/monitoring would be implemented.
Networks would be firewalled/segregated, critical systems airgapped when possible.
Data loss/leak prevention, backups, disaster recovery plans in place.
The goal is a secure setup with balanced control, oversight to prevent malfeasance, and resilience against both external threats and internal compromise.
Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
I haven't done this yet
Monetization
While the Filecoin Foundation and PL will continue to make investments into developing the program and open-sourcing tools, we are also striving to expand and encourage high levels of service and professionalism through these new Notary Allocator pathways. These pathways require increasingly complex tooling and auditing platforms, and we understand that Notaries (and the teams and organizations responsible) are making investments into building effective systems.
It is reasonable for teams building services in this marketplace to include monetization structures. Our primary guiding principles in this regard are transparency and equity. We require these monetization pathways to be clear, consistent, and auditable.
Outline your monetization models for the services you provide as a notary allocator pathway.
We will release the quota in batches, and when the first batch of quota is completed, a data audit will be performed. We list the audit fees: 0.5FIl/TiB for both client & SP
Describe your organization's structure, such as the legal entity and other business & market ventures.
Genesis team focus on the field of distributed storage, with blockchain and filecoin data storage track as the major development business sectors.It currently has more than 80 members, invested about 300 million yuan, and deployed more than 4,000 storage server equipment in four cities across the country. The current daily growth rate is 500TB to 1.5PiB.The legal entity is Ying Xu。About filecoin products developed by the Genesis team :Firstly, The Genesis Browser。Secondly,"SD Cloud" filecoin storage cloud service platform。
Where will accounting for fees be maintained?
We will charge the customer trading account and SP trading account in the early stage and retain the evidence for community review. In the future we will write a smart contract to ensure smooth auditing and distribution.
If you've received DataCap allocation privileges before, please link to prior notary applications.
How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
Our team has some SP:f020330 f025002 f024483 f0101020 f0101021 with 143.22PiB and the total amount of fil is 1.27Million Product: Genesis browser for filecoin SDCloud Storage platform
How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
We usually receive requests via SLack, email, and GitHub. Customer demand is often estimated based on past allocations. Existing customers are also contacted through Slack.
Notary Allocator Pathway Name:
Genesis
Organization:
Genesis
Allocator's On-chain addresss:
f1ldkhvk55psquvhc727udmdl2tgm55exndh2meqa
Country of Operation:
China
Region(s) of operation:
Asia minus GCR,Greater China
Type of allocator: What is your overall diligence process? Automated (programmatic), Market-based, or Manual (human-in-the-loop at some phase). Initial allocations to these pathways will be capped.
Manual
Amount of DataCap Requested for allocator for 12 months:
70P
Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing?
In order to prevent customers from malicious use or abuse of DataCap, we will carefully review customers, examining their needs, and allocate them on demand. So I first specify some rules to figure out the true identity of the applicant.Browse its official website to get a general understanding of the company or individual.
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, or other operating entity. * You can read the Filecoin Code of Conduct here: https://github.com/filecoin-project/community/blob/master/CODE_OF_CONDUCT.md
Acknowledgment: Acknowledge
Cient Diligence Section:
This section pertains to client diligence processes.
Who are your target clients?
Individuals learning about Filecoin,Small-scale developers or data owners,Enterprise Data Clients
Describe in as much detail as possible how you will perform due diligence on clients.
In order to ensure the fairness and justice of DataCap distribution, we have formulated separate online and offline application procedures based on the number of DataCap applications and individual and corporate users. For individual users: We will review their Github registration years (180 days at least) to prevent malicious application bots. The amount of approval will also be controlled below 5 TiB. For business users: We have developed different review methods and requirements based on the number of their DataCap applications. If it is less than or equal to 5TiB, we will use online review. The following points will be reviewed. • Business license • Enterprise authorization letter (CEO's signature + seal) • All shareholders who account for more than 25% of the total number of shareholders must provide ID cards or passport photos. • Sample data submission (accounting for 0.2% of its total DataCap requests) If the application is larger than 5TiB, we will add offline comments based on online surveys (visit customers on business trips or invite them to our company). Enterprise business type • data source • Data volume (monthly) • What companies think about Filecoin • Data storage plan Complete automated approvals by filling out a request form.
Please specify how many questions you'll ask, and provide a brief overview of the questions.
Question: Please introduce yourself and your personal information on social media (official website, WeChat, LinkedIn,, GitHub). • What is the purpose of your application for DataCap? • Please provide the wallet address you want to apply for DataCap • Please provide the quota of Datacap you want to apply for. • Please provide the name of the organization, nationality, country of registration, time of registration, name of the executive, and relevant website (if you are an institutional user). • Please provide the region where you want to use DataCap, if it is more than one region, please pay attention. • How many miners do you plan to distribute DataCap to, if there are specially designated miners, please pay attention. • Have you assigned DataCap before? If so, please provide details. https://docs.google.com/spreadsheets/d/1ZZVv7ubFyXG8jdx6lXQi48yJ2U1MdjVzpMFwhIF9rXE/edit#gid=2015743766
Will you use a 3rd-party "Know your client" (KYC) service?
Ｙｅｓ．Toggle is the appropriate one that i used.
Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)
Any client．It is a fully open and inclusive access.We encourage diversity programs come to filecoin.
How do you plan to track the rate at which DataCap is being distributed to your clients?
Real-time tracking on DC distribution, integrates and uses multiple open sourced tooling. The number of DC allocations by the same client shall not exceed 30% of the total number. And the allocated DC amount does not exceed 2P. The time allocated is a working day. The distribution speed is to complete the review questions and answers to obtain DC.
Data Diligence
This section will cover the types of data that you expect to notarize.
As a reminder: The Filecoin Plus program defines quality data is all content that meets local regulatory requirements AND • the data owner wants to see on the network, including private/encrypted data • or is open and retrievable • or demonstrates proof of concept or utility of the network, such as efforts to improve onboarding
As an operating entity in the Filecoin Community, you are required to follow all local & regional regulations relating to any data, digital and otherwise. This may include PII and data deletion requirements, as well as the storing, transmitting, or accessing of data.
Acknowledgement: Acknowledge
What type(s) of data would be applicable for your pathway?
Public Open Dataset (Research/Non-Profit),Public Open Commercial/Enterprise,Private Commercial/Enterprise,Private Non-Profit/Social Impact
How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
First, we will require the applicant to provide the corresponding business license, relevant information of the company's legal person, facial recognition, tax bill, and the corresponding legal certificate of the location of the data storage server to verify the company's application entity information. Secondly, applicants are required to provide relevant proof of data ownership, and the data samples provided must account for 20% of the total application quota.Finally, only through KYB information verification can the data applicant's information be proven. The public and enterprise client must be open and transparent。
How will you ensure the data meets local & regional legal requirements?
We will check local legal requirements. Data that does not comply with the law will be rejected directly.If some data that we can't be sure is legal or not, we will disclose it to the community. Even to the notary call.
What types of data preparation will you support or require?
We will support text, graphic images, video, audio, numbers, AI, GIS, hot and cold data, etc.
What tools or methodology will you use to sample and verify the data aligns with your pathway?
We will initiate a retrieval request to the SP and randomly access some sectors for spot checks.
Data Distribution
This section covers deal-making and data distribution.
As a reminder, the Filecoin Plus program currently defines distributed onboarding as multiple physical locations AND multiple storage provider entities to serve client requirements.
Recommended Minimum: 3 locations, 4 to 5 storage providers, 5 copies
How many replicas will you require to meet programmatic requirements for distribution?
5+
What geographic or regional distribution will you require?
At least 3 geopolitical regions，each replica at different physical location, no or minimal VPN, different SP owner operators.
How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?
5+
Do you require equal percentage distribution for your clients to their chosen SPs? Will you require preliminary SP distribution plans from the client before allocating any DataCap?
The proportion does not exceed 25%, and the SP is required to do the KYB and provide a distribution plan and obey it . Then it should publicly disclose through comments on Github.
What tooling will you use to verify client deal-making distribution?
By far, the most convenient way is through the CID Checker, AC bot and datacapstats.io
How will clients meet SP distribution requirements?
Yes.we will use programmatic (such as software or smart contract) deal distribution to set of vetted and reputable SPs.
As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
I use a list of common VPN server IP addresses to filter whether a VPN is used.I am Willing to support SPs that utilize VPNs, but requires additional KYB checks and enforces distribution.
DataCap Allocation Strategy
In this section, you will explain your client DataCap allocation strategy.
Keep in mind the program principle over Limited Trust Over Time. Parties, such as clients, start with a limited amount of trust and power. Additional trust and power need to be earned over time through good-faith execution of their responsibilities and transparency of their actions.
Will you use standardized DataCap allocations to clients?
Yes, standardized
Allocation Tranche Schedule to clients:
• First:1. Review the information in the application form • Second:2. Ask the questions in Q12 above regarding the application • Third:3. Review the answers to the questions and ask further questions based on the answers. It is required to list data samples of no less than 20% of the total applied DC quota. • Fourth:4.Verify the authenticity, legality, and data size of the stored data type. • Max per client overall:2P All the information and decisions should be open and transparency.
Will you use programmatic or software based allocations?
Yes, standardized and software based
What tooling will you use to construct messages and send allocations to clients?
I use notary registry tooling at https://filplus.fil.org
Describe the process for granting additional DataCap to previously verified clients.
Applicants are required to distribute Datacap to at least 4 or more miners, which will increase storage redundancy and help maintain decentralization and reduce the potential for abuse. The more the miner client allocates, the more the Datacap client may receive. The remaining 20% of DC can be applied for the next round. In addition, the SP retrieval rate must be more than 20%, and at least 5 copies must be stored. CID checker and AC bot will be used for inspection.
Tooling & Bookkeeping
This program relies on many software tools in order to function. The Filecoin Foundation and PL have invested in many different elements of this end-to-end process, and will continue to make those tools open-sourced. Our goal is to increase adoption, and we will balance customization with efficiency.
This section will cover the various UX/UI tools for your pathway. You should think high-level (GitHub repo architecture) as well as tactical (specific bots and API endoints).
Describe in as much detail as possible the tools used for: • client discoverability & applications • due diligence & investigation • bookkeeping • on-chain message construction • client deal-making behavior • tracking overall allocator health • dispute discussion & resolution • community updates & comms
• client discoverability & applications GitHub • due diligence & investigation GitHub Comment • bookkeeping Github • on-chain message construction https://filplus.fil.org/#/ • client deal-making behavior Github CID Check Report and on-chain messaging • tracking overall allocator health https://datacapstats.io/ • dispute discussion & resolution Google Dispute • community updates & comms * Github & Slack
Will you use open-source tooling from the Fil+ team?
Yes,we will use the boost and Github repo.
Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
All allocation decisions will follow the guidelines published on Github. The same is true for all communications.It will be real-time update.It should be open and transparency.But for E-fil+ the information will not be disclosed.It needs the third party KYC or KYB. Since all interactions are intended to be done publicly, most allocation decisions should be self-explanatory. Any challenges related to allocation decisions should first be discussed publicly in the Github repository. If the notary public can’t provide a convincing reason, it can submit a dispute resolution application to the Notary Public Administration 14 business days from the date of the initial challenge. After submitting the dispute resolution application, the notary public can appoint an arbitrator among the root key holders to resolve the dispute. According to the decision of the arbitrator, a hearing may be held within 30 business days after the dispute resolution application is made.
Risk Mitigation, Auditing, Compliance
This framework ensures the responsible allocation of DataCap by conducting regular audits, enforcing strict compliance checks, and requiring allocators to maintain transparency and engage with the community. This approach safeguards the ecosystem, deters misuse, and upholds the commitment to a fair and accountable storage marketplace.
In addition to setting their own rules, each notary allocator will be responsible for managing compliance within their own pathway. You will need to audit your own clients, manage interventions (such as removing DataCap from clients and keeping records), and respond to disputes.
Describe your proposed compliance check mechanisms for your own clients.
Datacap distribution tracking is mainly at https://filplus.fil.org/#/ and https://datacapstats.io/. Customers' DC usage can be viewed through Github's CID Report. Regarding customer tolerance, we will respond based on the most basic LDN Q&A. KYC questions and answers for customers will include company entity information, development status, data storage type, size, and SP related information.
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
First of all, when a dispute arises, we should immediately stop DC distribution to the LDN. Only when the dispute is resolved can normal distribution be carried out. When a dispute arises, the corresponding LDN should be marked and the dispute should be resolved below on GitHub. Any dispute should be handled fairly and transparently. Any distribution of DC should comply with distribution rules and audit mechanisms.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
About tooling, we will announce it on Twitter and Slack and Github.Follow the announcement process and detailed rules introduction.For new optional tools, announce availability but make opt-in. Clearly explain purpose and intended usage. Pathway Guidelines For clarifications or minor adjustments, announce via release notes on documentation page. For substantive changes, first publish a proposal for public feedback on a discussion forum. Allow 2-4 weeks for comments. If approved, announce finalized changes along with a summary of feedback received and reasoning behind decisions. Give notice period before enforcement. Process Alterations Clearly define any proposed new processes as "pilots" or "optional" at outset to avoid scope creep. For pilots, set review period to assess usefulness prior to potential incorporation as standard process.
How long will you allow the community to provide feedback before implementing changes?
I will research the proposal and ask for opinions from multiple parties, and come to a conclusion that favors the axiomatic side.For minor clarifications or bug fixes, 1-2 weeks for feedback should suffice. For substantive changes or new proposals, 4 weeks minimum to allow broader discussion. Actively moderate discussions to prevent domination by any single entity. Synthesize feedback themes rather than taking a headcount approach. Consider perspectives across various stakeholder groups. Where there are disagreements, discuss trade-offs transparently in proposal updates. Explain rationale for final decisions. For proposals where consensus cannot be reasonably achieved, allow voting as a last resort - but only among validated members to prevent manipulation. Continue engaging skeptics after a decision to understand concerns and refine approach over time based on experience. Consult Fil+ Governance team proactively for guidance on complex proposals or issues lacking clear resolution from community process alone. The goal would be fair representation rather than pure democracy or decentralization for its own sake. Moderated, thoughtful discussion aimed at consensus wherever possible seems most likely to maintain community trust over the long run.
Regarding security, how will you structure and secure the on-chain notary address? If you will utilize a multisig, how will it be structured? Who will have administrative & signatory rights?
I use a hardware wallet。Here is how I would recommend structuring and securing the on-chain notary address: Use a multisig address requiring M-of-N signatures for transactions. M should be sufficiently high (e.g. 3 or 4) to prevent funds loss from any single compromised signatory. N should include 5-7 signatories total for redundancy and in case any signers become unavailable long-term. Signatories would include technical operators plus independent compliance/oversight roles assigned by the Fil+ Governance team. Private keys would be split and stored securely using hardware security modules (HSMs), multisig wallets, offline storage. Regular audits of private key storage, hardware, and software would be conducted by independent assessors. Administrative rights like adding/removing signatories would require oversight approval via governance process. Daily operations could be handled via multisig transactions initiated by dev/ops staff. Secure development practices like secret scanning, access control, logging/monitoring would be implemented. Networks would be firewalled/segregated, critical systems airgapped when possible. Data loss/leak prevention, backups, disaster recovery plans in place. The goal is a secure setup with balanced control, oversight to prevent malfeasance, and resilience against both external threats and internal compromise.
Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
I haven't done this yet
Monetization
While the Filecoin Foundation and PL will continue to make investments into developing the program and open-sourcing tools, we are also striving to expand and encourage high levels of service and professionalism through these new Notary Allocator pathways. These pathways require increasingly complex tooling and auditing platforms, and we understand that Notaries (and the teams and organizations responsible) are making investments into building effective systems.
It is reasonable for teams building services in this marketplace to include monetization structures. Our primary guiding principles in this regard are transparency and equity. We require these monetization pathways to be clear, consistent, and auditable.
Outline your monetization models for the services you provide as a notary allocator pathway.
We will release the quota in batches, and when the first batch of quota is completed, a data audit will be performed. We list the audit fees: 0.5FIl/TiB for both client & SP
Describe your organization's structure, such as the legal entity and other business & market ventures.
Genesis team focus on the field of distributed storage, with blockchain and filecoin data storage track as the major development business sectors.It currently has more than 80 members, invested about 300 million yuan, and deployed more than 4,000 storage server equipment in four cities across the country. The current daily growth rate is 500TB to 1.5PiB.The legal entity is Ying Xu。About filecoin products developed by the Genesis team :Firstly, The Genesis Browser。Secondly,"SD Cloud" filecoin storage cloud service platform。
Where will accounting for fees be maintained?
We will charge the customer trading account and SP trading account in the early stage and retain the evidence for community review. In the future we will write a smart contract to ensure smooth auditing and distribution.
If you've received DataCap allocation privileges before, please link to prior notary applications.
Yes ,we are V3 and V4 notary . For V4: https://github.com/filecoin-project/notary-governance/issues/732
How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
Our team has some SP:f020330 f025002 f024483 f0101020 f0101021 with 143.22PiB and the total amount of fil is 1.27Million Product: Genesis browser for filecoin SDCloud Storage platform
How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
We usually receive requests via SLack, email, and GitHub. Customer demand is often estimated based on past allocations. Existing customers are also contacted through Slack.