Asia minus GCR,Greater China,Japan,Europe,North America,Africa
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:
50Pib
Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing?
We use advanced AI data analysis tools to mark all applicants. Delay the allocation speed for some applicants with bad credit. Overall, our configurator is more than just a product; it is a dynamic and evolving solution capable of adapting to today's complex environment
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?
Enterprise Data Clients,Small-scale developers or data owners
Describe in as much detail as possible how you will perform due diligence on clients.
I will determine the authenticity and legality of the client entity.
I will determine whether the customer is the data owner or the data preparer.
I will look at the data sample to check if the data is consistent with the application description.
I will review the number of SP entities and the distribution of data storage.
I will evaluate the client's historical performance.
Please specify how many questions you'll ask, and provide a brief overview of the questions.
Organization name
Region
Organization type, whether it is a Filecoin miner
Contact information such as slack, telegram, wechat, gmail etc.
Describe how to do the work
Provide information related to cooperative SPs
Whether to use VPN
Will you use a 3rd-party "Know your client" (KYC) service?
It may be used in the future, but not yet. But I still have some conditions for selecting clients. I would allow new clients to start with fewer applications. For clients with good historical performance, we will support their large-amount applications and strictly review them.
Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)
Of course, I welcome all new clients to join and contribute to Filecoin's storage of real data. At the same time, I will guide them and provide help with issues such as application, data preparation, and data distribution. I hope to help onboard new clients with complete tutorial documentation.
How do you plan to track the rate at which DataCap is being distributed to your clients?
I considered using a mature, open source client quota monitoring tool to monitor the client's distribution rate. If there is no useful tool, we will develop and open source a monitoring tool to regularly detect the client's distribution rate.
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),Private Non-Profit/Social Impact,Public Open Commercial/Enterprise,Private Commercial/Enterprise
How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
Currently I prefer to authenticate clients storing public datasets. For Clients who store their own private data, I will strictly review the legality of entities (Related entity files may be required), data legality, and data sources. Clients need to provide proof of the number of users and data volume. I will experience the customer's product and guarantee that I will not be cheated.
How will you ensure the data meets local & regional legal requirements?
I think it is difficult to 100% supervise whether the data complies with the laws of each region. I think I might be more concerned about whether the data is illegal in most places. (For example, I will strictly prohibit data containing pornography, gambling, drugs, etc.)
What types of data preparation will you support or require?
We have extensive experience in data preparation. Therefore, I can help customers in need in this aspect. I would recommend customers to use the singularity open source tool to complete the data cutting work. We have also customized some functions based on this tool, which I am happy to provide to customers. Hope this helps them.
What tools or methodology will you use to sample and verify the data aligns with your pathway?
We will verify whether the commp results of different miners refer to the same order under the same LDN are consistent. If singularity is required for data cutting, the cut cars will be consistent. (CIDcommD= PieceCID = Rroposa.RiegeGID in Publish message)
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?
No less than 5 physical locations. no less than 2 separate geopolitical regions. No less than 3 or more SP entities. Less VPN usage
How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?
3+
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?
I will ask for a preliminary SP allocation plan. But considering the unpredictable factors, I will not force SPs to be allocated in equal percentages, and I am willing to accept clients to add new SPs. The premise is that they must meet the rules of FIL+ and complete KYC.At the same time, it must meet the data distribution requirements I mentioned above.
What tooling will you use to verify client deal-making distribution?
The existing datacapstats.io tooling
How will clients meet SP distribution requirements?
I will fully understand the customer's needs for data distribution. If the customer lacks SP in some regions. I will provide customers with a list of some well-performing SPs to promote cooperation. I will maintain a table of SPs, and the data comes from SPs that are already cooperating, or SPs that have performed well in historical audits.
As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
Before starting, I ask the client if they are using a VPN and I support their use of one. If using a VPN, customers will need to provide documentation proving that the physical devices are not in the same region.
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:
I will divide it into 3 stages.
For new clients, allocation of 100-500Tib per LDN is allowed.
Good performing clients are allowed to allocate 1-5Pib per LDN.
clients with excellent reputation are allowed to allocate 5-15Pib per LDN.
The maximum does not exceed 75Pib.
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?
Notary Registry
Describe the process for granting additional DataCap to previously verified clients.
Use the Subsequent Allocation (SA) bot, manual review
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
I will use Google Online Document Classification Records • Due Diligence and Investigation
• Bookkeeping
• On-chain message construction
• Customer trading behavior
• Track overall dispenser health
and other information.
Dispute discussion & resolution will be conducted directly on github.
community updates & comms *use slack
Because we believe that Google Docs, GitHub, and Slack are the tools that community members are most familiar with. If everyone uses their own tools, it will only increase the cost of learning.
Will you use open-source tooling from the Fil+ team?
Sure, but currently I only use singularity and Notary Registry. If there is a new useful tool. I will use it too.
Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
In order to be responsible for user information, I will disclose the review results of the information provided by customers, the reasons for consent/rejection and other relevant information through Google documents. If a dispute arises, I will provide more details in the google documentation and github.
What will your DataCap distribution look like?
N/A
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.
Through the current robot report, first exclude necessary conditions such as CID sharing, number of copies, and repetition rate.
Mark the customer's credit and enter all customer SP nodes into our database. Perform SP scoring based on factors such as retrieval success rate, geographical distribution, number of copies, etc.
Tolerance: Description: relax a little in the first round, and close it in the second round if there is no sign of correction.
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
If there is any dispute, I will respond within 1-2 days (taking into account some uncontrollable factors). I hope that all discussions will be conducted directly under a specific issue. Both the challenger and the person being challenged need to provide comprehensive evidence.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
Considering that FIL+ applications are all processed on github, I will maintain a public folder under the github account to disclose information such as tooling, pathway guidelines, parameters, and process alterations. Once there is any update, I will append the new file and keep the old file content. It is convenient for anyone to find the previous public information.
How long will you allow the community to provide feedback before implementing changes?
Once there is an update, I will launch a proposal in the public announcement file I maintain and notify everyone in the slack channel. Community members can discuss different opinions on github. Our department will complete the collection of suggestions and start implementation within 7-10 days.
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?
Consider that rights are not transferred at will like tokens. Also take into account unnecessary multi-party signature confirmation. I would use a hardware wallet(Ledger) to manage it instead of multi-signature. The hardware wallet is kept by the team and signatures are completed by specialists who review the client's application.
Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
If necessary, I will develop simple smart contracts. But there are currently no plans to do so.
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.
There are currently no plans for monetization.
Describe your organization's structure, such as the legal entity and other business & market ventures.
Our team is registered in Singapore and is a development team focusing on technology output.
Where will accounting for fees be maintained?
None
If you've received DataCap allocation privileges before, please link to prior notary applications.
None
How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
Froghub is a completely technical team and an early participant and ecological builder of Filecoin. We have started to understand and participate in Filecoin in 2020, providing technical support for Filecoin mining to many customers and helping them become a qualified storage provider. At the same time, we are also working hard to build ecological projects and provide free and open source tools for community developers.
How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
We connect with many storage providers and developers. We encourage them to store valuable public data sets on Filecoin. We were proficient in this process, but we hadn’t established an onboarding pipeline yet.
Pathway Name:
FrogHub
Organization:
FrogHub Tech
Allocator's On-chain addresss:
f1a7ngs2e6vb2mlwjqjazk44c7dzck5yuslb5tgcy
Country of Operation:
Singapore
Region(s) of operation:
Asia minus GCR,Greater China,Japan,Europe,North America,Africa
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:
50Pib
Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing?
We use advanced AI data analysis tools to mark all applicants. Delay the allocation speed for some applicants with bad credit. Overall, our configurator is more than just a product; it is a dynamic and evolving solution capable of adapting to today's complex environment
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?
Enterprise Data Clients,Small-scale developers or data owners
Describe in as much detail as possible how you will perform due diligence on clients.
Please specify how many questions you'll ask, and provide a brief overview of the questions.
Will you use a 3rd-party "Know your client" (KYC) service?
It may be used in the future, but not yet. But I still have some conditions for selecting clients. I would allow new clients to start with fewer applications. For clients with good historical performance, we will support their large-amount applications and strictly review them.
Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)
Of course, I welcome all new clients to join and contribute to Filecoin's storage of real data. At the same time, I will guide them and provide help with issues such as application, data preparation, and data distribution. I hope to help onboard new clients with complete tutorial documentation.
How do you plan to track the rate at which DataCap is being distributed to your clients?
I considered using a mature, open source client quota monitoring tool to monitor the client's distribution rate. If there is no useful tool, we will develop and open source a monitoring tool to regularly detect the client's distribution rate.
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),Private Non-Profit/Social Impact,Public Open Commercial/Enterprise,Private Commercial/Enterprise
How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
Currently I prefer to authenticate clients storing public datasets. For Clients who store their own private data, I will strictly review the legality of entities (Related entity files may be required), data legality, and data sources. Clients need to provide proof of the number of users and data volume. I will experience the customer's product and guarantee that I will not be cheated.
How will you ensure the data meets local & regional legal requirements?
I think it is difficult to 100% supervise whether the data complies with the laws of each region. I think I might be more concerned about whether the data is illegal in most places. (For example, I will strictly prohibit data containing pornography, gambling, drugs, etc.)
What types of data preparation will you support or require?
We have extensive experience in data preparation. Therefore, I can help customers in need in this aspect. I would recommend customers to use the singularity open source tool to complete the data cutting work. We have also customized some functions based on this tool, which I am happy to provide to customers. Hope this helps them.
What tools or methodology will you use to sample and verify the data aligns with your pathway?
We will verify whether the commp results of different miners refer to the same order under the same LDN are consistent. If singularity is required for data cutting, the cut cars will be consistent. (CIDcommD= PieceCID = Rroposa.RiegeGID in Publish message)
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?
No less than 5 physical locations. no less than 2 separate geopolitical regions. No less than 3 or more SP entities. Less VPN usage
How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?
3+
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?
I will ask for a preliminary SP allocation plan. But considering the unpredictable factors, I will not force SPs to be allocated in equal percentages, and I am willing to accept clients to add new SPs. The premise is that they must meet the rules of FIL+ and complete KYC.At the same time, it must meet the data distribution requirements I mentioned above.
What tooling will you use to verify client deal-making distribution?
The existing datacapstats.io tooling
How will clients meet SP distribution requirements?
I will fully understand the customer's needs for data distribution. If the customer lacks SP in some regions. I will provide customers with a list of some well-performing SPs to promote cooperation. I will maintain a table of SPs, and the data comes from SPs that are already cooperating, or SPs that have performed well in historical audits.
As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
Before starting, I ask the client if they are using a VPN and I support their use of one. If using a VPN, customers will need to provide documentation proving that the physical devices are not in the same region.
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:
I will divide it into 3 stages. For new clients, allocation of 100-500Tib per LDN is allowed. Good performing clients are allowed to allocate 1-5Pib per LDN. clients with excellent reputation are allowed to allocate 5-15Pib per LDN. The maximum does not exceed 75Pib.
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?
Notary Registry
Describe the process for granting additional DataCap to previously verified clients.
Use the Subsequent Allocation (SA) bot, manual review
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
I will use Google Online Document Classification Records • Due Diligence and Investigation • Bookkeeping • On-chain message construction • Customer trading behavior • Track overall dispenser health and other information. Dispute discussion & resolution will be conducted directly on github. community updates & comms *use slack Because we believe that Google Docs, GitHub, and Slack are the tools that community members are most familiar with. If everyone uses their own tools, it will only increase the cost of learning.
Will you use open-source tooling from the Fil+ team?
Sure, but currently I only use singularity and Notary Registry. If there is a new useful tool. I will use it too.
Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
In order to be responsible for user information, I will disclose the review results of the information provided by customers, the reasons for consent/rejection and other relevant information through Google documents. If a dispute arises, I will provide more details in the google documentation and github.
What will your DataCap distribution look like?
N/A
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.
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
If there is any dispute, I will respond within 1-2 days (taking into account some uncontrollable factors). I hope that all discussions will be conducted directly under a specific issue. Both the challenger and the person being challenged need to provide comprehensive evidence.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
Considering that FIL+ applications are all processed on github, I will maintain a public folder under the github account to disclose information such as tooling, pathway guidelines, parameters, and process alterations. Once there is any update, I will append the new file and keep the old file content. It is convenient for anyone to find the previous public information.
How long will you allow the community to provide feedback before implementing changes?
Once there is an update, I will launch a proposal in the public announcement file I maintain and notify everyone in the slack channel. Community members can discuss different opinions on github. Our department will complete the collection of suggestions and start implementation within 7-10 days.
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?
Consider that rights are not transferred at will like tokens. Also take into account unnecessary multi-party signature confirmation. I would use a hardware wallet(Ledger) to manage it instead of multi-signature. The hardware wallet is kept by the team and signatures are completed by specialists who review the client's application.
Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
If necessary, I will develop simple smart contracts. But there are currently no plans to do so.
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.
There are currently no plans for monetization.
Describe your organization's structure, such as the legal entity and other business & market ventures.
Our team is registered in Singapore and is a development team focusing on technology output.
Where will accounting for fees be maintained?
None
If you've received DataCap allocation privileges before, please link to prior notary applications.
None
How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
Froghub is a completely technical team and an early participant and ecological builder of Filecoin. We have started to understand and participate in Filecoin in 2020, providing technical support for Filecoin mining to many customers and helping them become a qualified storage provider. At the same time, we are also working hard to build ecological projects and provide free and open source tools for community developers.
How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
We connect with many storage providers and developers. We encourage them to store valuable public data sets on Filecoin. We were proficient in this process, but we hadn’t established an onboarding pipeline yet.