Africa ,Asia minus GCR,Greater China,Europe,Oceania,Japan,North America,South America,Other
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:
5 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?
Allocator will focus on permissionlessly serving a closed circle of small-scale data owners requiring maximum anonymity with lowest possible on-chain footprint.
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?
Small-scale developers or data owners
Describe in as much detail as possible how you will perform due diligence on clients.
Pathway is manual.
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?
I will not use a 3rd party KYC service under any circumstances.
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 can apply, but approval will require an actual physical meeting or in select cases a "vouching friend" introduction.
How do you plan to track the rate at which DataCap is being distributed to your clients?
Through a sole-operated matchmaking platform MPL-50 (similar to ♠️, but radically distinct in key aspects)
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?
Other (specified elsewhere)
How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
See answers to 12, 13 and 14.
How will you ensure the data meets local & regional legal requirements?
By due diligence before and during in-person meeting.
What types of data preparation will you support or require?
No data preparation requirements under any circumstances. Service accepts any reasonably-sized opaque bytestream.
What tools or methodology will you use to sample and verify the data aligns with your pathway?
Manual, proprietary proccess.
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?
3+
What geographic or regional distribution will you require?
Entirely depends on data-owner request.
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?
Negotiated during in-person meeting.
What tooling will you use to verify client deal-making distribution?
Enforced by own proprietary allocator (see answer to 12)
How will clients meet SP distribution requirements?
Enforced by own proprietary allocator (see answer to 12)
As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
The profile of my clients absolutely supports and strongly encourages use of VPN.
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:
Per-sector allocation, see answer 12.
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?
Own to-be-developed tooling.
Describe the process for granting additional DataCap to previously verified clients.
See answers to 30 and 12
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
Effectively all components of ♠️, but without the silly parts.
Will you use open-source tooling from the Fil+ team?
I will not use Fil+ team tooling under any circumstances. Everything will be developed by me personally (open sourced where reasonable)
Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
Public to the extent of no impact to anonymity/premissionlessness.
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.
See answers to 30 and 12
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
Due to allocator design all disputes will end up being internal. They will be dealt with internally in private.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
There will be no iteration on the allocator: it will either continue working exacty as described or will be shut down.
How long will you allow the community to provide feedback before implementing changes?
Not applicable, see 39.
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?
This is a proud bus-factor-of-one operation. Security is derived from the operator's experience building the Filecoin blockchain.
Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
Design will strive to have zero smart contract involvement.
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.
No monetization of the datacap-allocation service under any circumstances.
Describe your organization's structure, such as the legal entity and other business & market ventures.
This is a proud bus-factor-of-one operation.
Where will accounting for fees be maintained?
As there will be no monetiation, no associated fees apply.
If you've received DataCap allocation privileges before, please link to prior notary applications.
I was the first active Root Key Holder on the current Filecoin blockchain.
How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
I am ribasushi.
How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
Notary Allocator Pathway Name:
MPL-50 ☭
Organization:
Peter 'ribasushi' Rabbitson
Allocator's On-chain addresss:
f3sdwgbslj4kzduc3753lygavwvja6lgo3ahhqoderwfwffd4bvjavkz34au43ypzixjxkzx6rtfuihk3zybbq
Country of Operation:
Germany
Region(s) of operation:
Africa ,Asia minus GCR,Greater China,Europe,Oceania,Japan,North America,South America,Other
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:
5 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?
Allocator will focus on permissionlessly serving a closed circle of small-scale data owners requiring maximum anonymity with lowest possible on-chain footprint.
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?
Small-scale developers or data owners
Describe in as much detail as possible how you will perform due diligence on clients.
Pathway is manual.
Please specify how many questions you'll ask, and provide a brief overview of the questions.
Clients are exclusively anonymous individuals, who will not be asked any questions on record. Potential absue will be limited by coupling the act of dispensing datacap with presence of multi-SP storage contracts instantly consuming said datacap . More info on philosophy here: https://filecoinproject.slack.com/archives/C01DLAPKDGX/p1674041338953649?thread_ts=1674014944.338909&cid=C01DLAPKDGX
Will you use a 3rd-party "Know your client" (KYC) service?
I will not use a 3rd party KYC service under any circumstances.
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 can apply, but approval will require an actual physical meeting or in select cases a "vouching friend" introduction.
How do you plan to track the rate at which DataCap is being distributed to your clients?
Through a sole-operated matchmaking platform MPL-50 (similar to ♠️, but radically distinct in key aspects)
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?
Other (specified elsewhere)
How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
See answers to 12, 13 and 14.
How will you ensure the data meets local & regional legal requirements?
By due diligence before and during in-person meeting.
What types of data preparation will you support or require?
No data preparation requirements under any circumstances. Service accepts any reasonably-sized opaque bytestream.
What tools or methodology will you use to sample and verify the data aligns with your pathway?
Manual, proprietary proccess.
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?
3+
What geographic or regional distribution will you require?
Entirely depends on data-owner request.
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?
Negotiated during in-person meeting.
What tooling will you use to verify client deal-making distribution?
Enforced by own proprietary allocator (see answer to 12)
How will clients meet SP distribution requirements?
Enforced by own proprietary allocator (see answer to 12)
As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
The profile of my clients absolutely supports and strongly encourages use of VPN.
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:
Per-sector allocation, see answer 12.
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?
Own to-be-developed tooling.
Describe the process for granting additional DataCap to previously verified clients.
See answers to 30 and 12
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
Effectively all components of ♠️, but without the silly parts.
Will you use open-source tooling from the Fil+ team?
I will not use Fil+ team tooling under any circumstances. Everything will be developed by me personally (open sourced where reasonable)
Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
Public to the extent of no impact to anonymity/premissionlessness.
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.
See answers to 30 and 12
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
Due to allocator design all disputes will end up being internal. They will be dealt with internally in private.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
There will be no iteration on the allocator: it will either continue working exacty as described or will be shut down.
How long will you allow the community to provide feedback before implementing changes?
Not applicable, see 39.
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?
This is a proud bus-factor-of-one operation. Security is derived from the operator's experience building the Filecoin blockchain.
Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
Design will strive to have zero smart contract involvement.
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.
No monetization of the datacap-allocation service under any circumstances.
Describe your organization's structure, such as the legal entity and other business & market ventures.
This is a proud bus-factor-of-one operation.
Where will accounting for fees be maintained?
As there will be no monetiation, no associated fees apply.
If you've received DataCap allocation privileges before, please link to prior notary applications.
I was the first active Root Key Holder on the current Filecoin blockchain.
How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
I am ribasushi.
How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
Napkin math.