NateWebb03
commented
5 months ago Notary Allocator Pathway Name:
Kernelogic Fil+ Datacap Allocator
Organization:
Kernelogic
Allocator's On-chain addresss:
f1yvo2nutvy6a4ortrvv2tguhpsi64a7fgrc42owy
Country of Operation:
Canada
Region(s) of operation:
North America
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.
Automatic
Amount of DataCap Requested for allocator for 12 months:
250 PiB
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 the medium term, we explicitly plan to support ways in which we can programmatically identify use cases that warrant DataCap, both for users of our tools and any others in the network. Examples of this include - identifying ways in which we can programmatically show a “paid” deal (even if its not denominated in a payment on the Filecoin network) as a form of quality utilization of the network, experiment with dIDs to identify real users, and leverage more forms of deal tracking and activity to separate realistic demand from abuse of the system. We were a key part of a lot of the T&T tooling that exists today, and we look forward to coming up with more ways we can contribute to the Fil+ ecosystem.
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,Other (specified above),Small-scale developers or data owners
Describe in as much detail as possible how you will perform due diligence on clients.
KFDA aims to streamline the current, labor-intensive manual process by automating as much as possible in a permissionless manner.
Upon registration with KFDA, clients are required to verify their email address (social login is also an option).
Clients then submit a dataset onboarding request, which can be an AWS open dataset or their private dataset. Provided KFDA has access to the metadata (file list and size), it will conduct automated content verification throughout the lifecycle of the DC distribution.
Pricing starts at a basic rate, but significant discounts are offered for various decentralization characteristics of clients to encourage datacap acquisition. These discounts, which can be combined, include:
5% off for using an AWS public dataset. 5% off if the dataset is not excessively popular. 5% off for collaborating with SPs utilizing green energy. 5% off for working with new SPs. 5% off for working with established SPs. 5% off for collaborating with SPs in specific regions. 5% off for working with SPs that offer higher retrieval speeds. 5% off for repeat clients.
Please specify how many questions you'll ask, and provide a brief overview of the questions.
KFDA, emphasizing efficiency, will ask clients only a few key questions: the dataset name, the owner, their role, the industry, and to upload the dataset metadata. This last requirement is waived if it's an S3 open dataset.
Will you use a 3rd-party "Know your client" (KYC) service?
No. Only email verification or social login. KFDA wants to focus on permissonless.
Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)
KFDA is open to any clients who wish to onboard data that is publicly retrievable and verifiable.
How do you plan to track the rate at which DataCap is being distributed to your clients?
No tracking of the rate. Clients who passed checks need to pay Fil to get DC allocation to prevent hoarding.
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
How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
KFDA operates on a completely permissionless basis, placing the legal responsibility on the client.
How will you ensure the data meets local & regional legal requirements?
KFDA operates on a completely permissionless basis, placing the legal responsibility on the client.
What types of data preparation will you support or require?
Data must not be archived inside sectors. Kernelogic will offer best-effort consultation for onboarding processes.
What tools or methodology will you use to sample and verify the data aligns with your pathway?
The process involves comparing the data with its metadata, including size, to ensure that the sectors store exactly what they claim to. This comparison aims to prevent padding abuse within a reasonable percentage, as well as avoiding duplications and enlargements of the data.
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?
2+
What geographic or regional distribution will you require?
There are no obligatory conditions for clients. However, clients desiring lower costs can benefit from more discounts by increasing their data distribution. Additionally, KFDA plans to organize events offering significant discounts for specific regions to encourage the development of regional Storage Providers (SPs). For instance, to promote more African SPs, KFDA could offer a substantial discount to clients working with SPs in that region.
How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?
2+
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?
KFDA operates on a market-based adjustment principle without stringent requirements. Clients can voluntarily opt to work with green energy Storage Providers (SPs) and indicate this preference by providing supporting materials. This approach allows clients to align with sustainable practices and potentially benefit from associated discounts.
What tooling will you use to verify client deal-making distribution?
KFDA has the ability to develop its own CID checker bot. However if existing bots have good enough APIs KFDA might opt to utilize existing bots.
How will clients meet SP distribution requirements?
No requirement. Market (discount) based adjustment.
As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
Yes, Kernelogic consistently expressed support to reasonable use of VPNs, recognizing them as an integral part of enterprise firewall practices.
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?
No, client specific
Allocation Tranche Schedule to clients:
• First: 100 TiB minimal • Second: 300 TiB maximal • Third: 1 PiB maximal • Fourth: 2 PiB maximal • Max per client overall: No limit as long as the metadata fits replication goal.
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?
filplus.storage for initial application intake. Lotus binary to issue datacap. Lassie to verify data content.
Describe the process for granting additional DataCap to previously verified clients.
KFDA possesses the capability to develop its own DataCap (DC) request calculator. However, if existing bots offer sufficiently robust APIs, KFDA might choose to utilize these existing bots instead. Clients are provided with the flexibility to upload metadata information in tranches. This approach ensures that clients are not required to prepare all the CARs at the outset. They have the liberty to decide the size of the next tranche, adopting an à la carte style approach to data management and submission.
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
KFDA is developing a comprehensive multi-tenant web platform, with a prototype already in place. This platform will provide each client with a dedicated workspace where they can invite collaborators, create a dataset onboarding plan, upload metadata, and monitor the data verification process. Additionally, it will enable clients to apply for subsequent allocation tranches and submit disputes, among other functionalities, thereby streamlining the data management and verification process for each client.
Will you use open-source tooling from the Fil+ team?
The multi-tenant web platform will be built with NodeJS and Postgres DB, Mongo DB will also be utilized to store metadata. Lotus binary will be used to check balance, monitor payment transactions and issue datacaps. Lassie will be used to perform retrieval sampling.
Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
Clients will be able to view every decision making logs in KFDA platform. Upon request, decision making logs can also be exported and provided to Fil+ team. Public page will also be available for total datasets onboarded, total DC distributed, for transparency.
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.
KFDA plans to set up servers in multiple regions to conduct retrieval sampling. This process involves inspecting the content of sectors to determine the files present and their sizes, and then comparing this information with the metadata previously uploaded by clients before allocation.
Clients who comply with the system and exhibit good behavior will receive substantial discounts on DataCap (DC) allocation fees, in accordance with predefined rules. This approach essentially makes the process market-based.
In cases where the onboarded data does not match the provided metadata or is completely unretrievable, KFDA will pause further allocations. Resolution will require a manual review, involving a consensus-reaching dialogue between the clients and KFDA operators. This measure ensures data integrity and compliance with KFDA standards.
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
KFDA will maintain a GitHub repository specifically for submitting dispute issues. In the event of a dispute, KFDA commits to providing a complete audit trail of its decision-making process and is open to constructive suggestions to enhance its verification procedures.
Furthermore, in cases where a datacap revocation occurs by the FIL+ team, KFDA will ensure a refund of Fil for the unused portion of the datacap. This policy demonstrates KFDA's commitment to transparency and accountability in its operations and its responsiveness to the community's needs and feedback.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
KFDA is considering the possibility of open-sourcing the entire platform once it reaches a sufficient level of maturity. This move would allow more allocators to utilize the platform, potentially broadening its impact and utility in the data management and allocation space. Additionally, KFDA is committed to actively listening to constructive feedback. This includes suggestions for improving various aspects of the platform, such as rules, verification processes, discount structures, and more, to better align with market sentiments and needs. This approach demonstrates KFDA's dedication to continuous improvement and responsiveness to user feedback.
How long will you allow the community to provide feedback before implementing changes?
Dedicated KFDA GitHub Repo to collect advice and disputes. Slack channel on filecoin slack for support. Wechat group for Chinese speaking community.
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?
Given the automated nature of KFDA, it will employ standard IT DevSecOps practices to ensure the security of the notary address. Fei Yan, the creator of KFDA, brings a wealth of experience in DevSecOps from his years working in large enterprise environments within the insurance and government industries in Canada. This background equips him with the necessary expertise to implement robust security measures and maintain the integrity of KFDA's operations.
Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
Not initially. However, in a later phase, there are plans to introduce a KFD token. This token would be available to qualified clients, who could exchange it for datacap. Furthermore, the KFD token is expected to be listed on various decentralized finance (DeFi) exchanges, allowing the market to determine its value. This strategy indicates a move towards integrating blockchain-based incentives and market mechanisms within the KFDA ecosystem.
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.
When a client is prepared to receive a tranche of datacap and their data has successfully passed verification, they can proceed to pay for the datacap in Fil, with a set price per TiB. Once the payment transaction is detected, the datacap is automatically issued to the client. The starting price for this service is set at 0.5 Fil per TiB. This automated process ensures efficiency and transparency in the allocation of datacap to clients.
Various discount can be applied to the datacap price, such as Dataset is a AWS public dataset, 5% off Dataset is not overly crowded, 5% off Client is working with SPs using green energy, 5% off Client is working with new SPs, 5% off Client is working with established SPs, 5% off Client is working with SPs in certain region, 5% off Client is working with SPs with higher retrieval speed, 5% off Repeat client, 5% off Therefore if client checks for all above, 40% off bring it down to 0.3F / TiB More discounts in discovery
Describe your organization's structure, such as the legal entity and other business & market ventures.
Sole corporation: Kernelogic Software Inc, registered in Canada.
Where will accounting for fees be maintained?
Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.
If you've received DataCap allocation privileges before, please link to prior notary applications.
https://github.com/filecoin-project/notary-governance/issues/658
How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
Kernelogic as a notary, has allocated over 250 PiBs of datacap to clients, #1 on the leaderboard. Kernelogic participated Space Race, Slingshot 1 and 2. Kernelogic helped Fil+ team to analyze all AWS public datasets for Slingshot v3. Kernelogic was one of the two main developers of Singularity V1. Kernelogic as a client, has onboarded over 100 PiBs of public dataset to the Filecoin network. 2 time dev grant receiver: MusicNFT, Singularity Humans of web3 interview: https://mirror.xyz/joinradius.eth/vwmrtaEcas5Ei3Ff6kNor6FB2i9zTvp0SMRuxOv6l_A Filecoin blog mentions: https://filecoin.io/blog/posts/large-datasets-kernelogic/
How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
Kernelogic has allocated over 250 PiBs of datacap. Therefore KFDA estimates will allocate again 250PiBs of datacap in the first year.
Notary Allocator Pathway Name:
Kernelogic Fil+ Datacap Allocator
Organization:
Kernelogic
Allocator's On-chain addresss:
f1yvo2nutvy6a4ortrvv2tguhpsi64a7fgrc42owy
Country of Operation:
Canada
Region(s) of operation:
North America
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.
Automatic
Amount of DataCap Requested for allocator for 12 months:
250 PiB
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 the medium term, we explicitly plan to support ways in which we can programmatically identify use cases that warrant DataCap, both for users of our tools and any others in the network. Examples of this include - identifying ways in which we can programmatically show a “paid” deal (even if its not denominated in a payment on the Filecoin network) as a form of quality utilization of the network, experiment with dIDs to identify real users, and leverage more forms of deal tracking and activity to separate realistic demand from abuse of the system. We were a key part of a lot of the T&T tooling that exists today, and we look forward to coming up with more ways we can contribute to the Fil+ ecosystem.
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,Other (specified above),Small-scale developers or data owners
Describe in as much detail as possible how you will perform due diligence on clients.
KFDA aims to streamline the current, labor-intensive manual process by automating as much as possible in a permissionless manner.
Upon registration with KFDA, clients are required to verify their email address (social login is also an option).
Clients then submit a dataset onboarding request, which can be an AWS open dataset or their private dataset. Provided KFDA has access to the metadata (file list and size), it will conduct automated content verification throughout the lifecycle of the DC distribution.
Pricing starts at a basic rate, but significant discounts are offered for various decentralization characteristics of clients to encourage datacap acquisition. These discounts, which can be combined, include:
5% off for using an AWS public dataset. 5% off if the dataset is not excessively popular. 5% off for collaborating with SPs utilizing green energy. 5% off for working with new SPs. 5% off for working with established SPs. 5% off for collaborating with SPs in specific regions. 5% off for working with SPs that offer higher retrieval speeds. 5% off for repeat clients.
Please specify how many questions you'll ask, and provide a brief overview of the questions.
KFDA, emphasizing efficiency, will ask clients only a few key questions: the dataset name, the owner, their role, the industry, and to upload the dataset metadata. This last requirement is waived if it's an S3 open dataset.
Will you use a 3rd-party "Know your client" (KYC) service?
No. Only email verification or social login. KFDA wants to focus on permissonless.
Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)
KFDA is open to any clients who wish to onboard data that is publicly retrievable and verifiable.
How do you plan to track the rate at which DataCap is being distributed to your clients?
No tracking of the rate. Clients who passed checks need to pay Fil to get DC allocation to prevent hoarding.
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
How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
KFDA operates on a completely permissionless basis, placing the legal responsibility on the client.
How will you ensure the data meets local & regional legal requirements?
KFDA operates on a completely permissionless basis, placing the legal responsibility on the client.
What types of data preparation will you support or require?
Data must not be archived inside sectors. Kernelogic will offer best-effort consultation for onboarding processes.
What tools or methodology will you use to sample and verify the data aligns with your pathway?
The process involves comparing the data with its metadata, including size, to ensure that the sectors store exactly what they claim to. This comparison aims to prevent padding abuse within a reasonable percentage, as well as avoiding duplications and enlargements of the data.
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?
2+
What geographic or regional distribution will you require?
There are no obligatory conditions for clients. However, clients desiring lower costs can benefit from more discounts by increasing their data distribution. Additionally, KFDA plans to organize events offering significant discounts for specific regions to encourage the development of regional Storage Providers (SPs). For instance, to promote more African SPs, KFDA could offer a substantial discount to clients working with SPs in that region.
How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?
2+
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?
KFDA operates on a market-based adjustment principle without stringent requirements. Clients can voluntarily opt to work with green energy Storage Providers (SPs) and indicate this preference by providing supporting materials. This approach allows clients to align with sustainable practices and potentially benefit from associated discounts.
What tooling will you use to verify client deal-making distribution?
KFDA has the ability to develop its own CID checker bot. However if existing bots have good enough APIs KFDA might opt to utilize existing bots.
How will clients meet SP distribution requirements?
No requirement. Market (discount) based adjustment.
As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
Yes, Kernelogic consistently expressed support to reasonable use of VPNs, recognizing them as an integral part of enterprise firewall practices.
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?
No, client specific
Allocation Tranche Schedule to clients:
• First: 100 TiB minimal • Second: 300 TiB maximal • Third: 1 PiB maximal • Fourth: 2 PiB maximal • Max per client overall: No limit as long as the metadata fits replication goal.
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?
filplus.storage for initial application intake. Lotus binary to issue datacap. Lassie to verify data content.
Describe the process for granting additional DataCap to previously verified clients.
KFDA possesses the capability to develop its own DataCap (DC) request calculator. However, if existing bots offer sufficiently robust APIs, KFDA might choose to utilize these existing bots instead. Clients are provided with the flexibility to upload metadata information in tranches. This approach ensures that clients are not required to prepare all the CARs at the outset. They have the liberty to decide the size of the next tranche, adopting an à la carte style approach to data management and submission.
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
KFDA is developing a comprehensive multi-tenant web platform, with a prototype already in place. This platform will provide each client with a dedicated workspace where they can invite collaborators, create a dataset onboarding plan, upload metadata, and monitor the data verification process. Additionally, it will enable clients to apply for subsequent allocation tranches and submit disputes, among other functionalities, thereby streamlining the data management and verification process for each client.
Will you use open-source tooling from the Fil+ team?
The multi-tenant web platform will be built with NodeJS and Postgres DB, Mongo DB will also be utilized to store metadata. Lotus binary will be used to check balance, monitor payment transactions and issue datacaps. Lassie will be used to perform retrieval sampling.
Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
Clients will be able to view every decision making logs in KFDA platform. Upon request, decision making logs can also be exported and provided to Fil+ team. Public page will also be available for total datasets onboarded, total DC distributed, for transparency.
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.
KFDA plans to set up servers in multiple regions to conduct retrieval sampling. This process involves inspecting the content of sectors to determine the files present and their sizes, and then comparing this information with the metadata previously uploaded by clients before allocation.
Clients who comply with the system and exhibit good behavior will receive substantial discounts on DataCap (DC) allocation fees, in accordance with predefined rules. This approach essentially makes the process market-based.
In cases where the onboarded data does not match the provided metadata or is completely unretrievable, KFDA will pause further allocations. Resolution will require a manual review, involving a consensus-reaching dialogue between the clients and KFDA operators. This measure ensures data integrity and compliance with KFDA standards.
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
KFDA will maintain a GitHub repository specifically for submitting dispute issues. In the event of a dispute, KFDA commits to providing a complete audit trail of its decision-making process and is open to constructive suggestions to enhance its verification procedures.
Furthermore, in cases where a datacap revocation occurs by the FIL+ team, KFDA will ensure a refund of Fil for the unused portion of the datacap. This policy demonstrates KFDA's commitment to transparency and accountability in its operations and its responsiveness to the community's needs and feedback.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
KFDA is considering the possibility of open-sourcing the entire platform once it reaches a sufficient level of maturity. This move would allow more allocators to utilize the platform, potentially broadening its impact and utility in the data management and allocation space. Additionally, KFDA is committed to actively listening to constructive feedback. This includes suggestions for improving various aspects of the platform, such as rules, verification processes, discount structures, and more, to better align with market sentiments and needs. This approach demonstrates KFDA's dedication to continuous improvement and responsiveness to user feedback.
How long will you allow the community to provide feedback before implementing changes?
Dedicated KFDA GitHub Repo to collect advice and disputes. Slack channel on filecoin slack for support. Wechat group for Chinese speaking community.
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?
Given the automated nature of KFDA, it will employ standard IT DevSecOps practices to ensure the security of the notary address. Fei Yan, the creator of KFDA, brings a wealth of experience in DevSecOps from his years working in large enterprise environments within the insurance and government industries in Canada. This background equips him with the necessary expertise to implement robust security measures and maintain the integrity of KFDA's operations.
Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
Not initially. However, in a later phase, there are plans to introduce a KFD token. This token would be available to qualified clients, who could exchange it for datacap. Furthermore, the KFD token is expected to be listed on various decentralized finance (DeFi) exchanges, allowing the market to determine its value. This strategy indicates a move towards integrating blockchain-based incentives and market mechanisms within the KFDA ecosystem.
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.
When a client is prepared to receive a tranche of datacap and their data has successfully passed verification, they can proceed to pay for the datacap in Fil, with a set price per TiB. Once the payment transaction is detected, the datacap is automatically issued to the client. The starting price for this service is set at 0.5 Fil per TiB. This automated process ensures efficiency and transparency in the allocation of datacap to clients.
Various discount can be applied to the datacap price, such as Dataset is a AWS public dataset, 5% off Dataset is not overly crowded, 5% off Client is working with SPs using green energy, 5% off Client is working with new SPs, 5% off Client is working with established SPs, 5% off Client is working with SPs in certain region, 5% off Client is working with SPs with higher retrieval speed, 5% off Repeat client, 5% off Therefore if client checks for all above, 40% off bring it down to 0.3F / TiB More discounts in discovery
Describe your organization's structure, such as the legal entity and other business & market ventures.
Sole corporation: Kernelogic Software Inc, registered in Canada.
Where will accounting for fees be maintained?
Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.Sole corporation: Kernelogic Software Inc, registered in Canada.
If you've received DataCap allocation privileges before, please link to prior notary applications.
https://github.com/filecoin-project/notary-governance/issues/658
How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
Kernelogic as a notary, has allocated over 250 PiBs of datacap to clients, #1 on the leaderboard. Kernelogic participated Space Race, Slingshot 1 and 2. Kernelogic helped Fil+ team to analyze all AWS public datasets for Slingshot v3. Kernelogic was one of the two main developers of Singularity V1. Kernelogic as a client, has onboarded over 100 PiBs of public dataset to the Filecoin network. 2 time dev grant receiver: MusicNFT, Singularity Humans of web3 interview: https://mirror.xyz/joinradius.eth/vwmrtaEcas5Ei3Ff6kNor6FB2i9zTvp0SMRuxOv6l_A Filecoin blog mentions: https://filecoin.io/blog/posts/large-datasets-kernelogic/
How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
Kernelogic has allocated over 250 PiBs of datacap. Therefore KFDA estimates will allocate again 250PiBs of datacap in the first year.