v5 Notary Allocator Application: MPL-50 ☭

[ribasushi]

Please complete the following steps:

1. Fill out the information below and create a new GitHub Issue

1. Notary Allocator Pathway Name (This can be your name, or the name of your pathway/program. For example "E-Fil+"):
   MPL-50 ☭

2. Organization Name:
   Peter 'ribasushi' Rabbitson

3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain):
   f3sdwgbslj4kzduc3753lygavwvja6lgo3ahhqoderwfwffd4bvjavkz34au43ypzixjxkzx6rtfuihk3zybbq

4. Country of Operation (Where your organization is legally based):
   Germany 🇩🇪

5. Region of Operation (What region will you serve?):
   All Regions

6. Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase):
   Manual (manually-driven programmatic solution)

7. DataCap requested for allocator for 12 months of activity (This should be an estimate of overall expected activity. Estimate the total amount of DataCap you will be distributing to clients in 12 months, in TiB or PiB):
   5PiB

2. Access allocator application (download to save answers)

Click link below to access a Google doc version of the allocator application that can be used to save your answers if you are not prepared to fully submit the application in Step 3. https://docs.google.com/document/d/1-Ze8bo7ZlIJe8qX0YSFNPTka4CMprqoNB1D6V7WJJjo/copy

3. Submit allocation application

Clink link below to access full allocator questionnaire and officially submit your answers:
https://airtable.com/appvyE0VHcgpAkt4Z/shrQxaAIsD693e1ns

Note: Sections of your responses WILL BE posted back into the GitHub issue tracking your application.
The final section (Additional Disclosures) will NOT be posted to GitHub, and will be maintained by the Filecoin Foundation.
Application information for notaries not accepted and ratified in this round will be deleted.

[ghost]

Basic Information

1. Notary Allocator Pathway Name:
MPL-50 ☭

2. Organization:
Peter 'ribasushi' Rabbitson

3. On Chain Address for Allocator:
f3sdwgbslj4kzduc3753lygavwvja6lgo3ahhqoderwfwffd4bvjavkz34au43ypzixjxkzx6rtfuihk3zybbq

4. Country of Operation:
Germany

5. Region(s) of operation:
Africa , Asia minus GCR, Greater China, Europe, Oceania, Japan, North America, South America, Other

6. Type of Allocator:
Manual

7. DataCap requested for allocator for 12 months of activity:
5 PiB

8. 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.

9. 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.:
Acknowledge

Client Diligence

10. Who are your target clients?:
Small-scale developers or data owners

11. Describe in as much detail as possible how you will perform due diligence on clients. If you are proposing an automated pathway, what diligence mechanism will you use to determine client eligibility?:
Pathway is manual.

12. 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

13. Will you use a 3rd-party Know your client (KYC) service?:
I will not use a 3rd party KYC service under any circumstances.

14. 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.

15. 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

16. 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, transmit:
Acknowledge

17. What type(s) of data would be applicable for your pathway?:
Other (specified elsewhere)

18. 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.

19. How will you ensure the data meets local & regional legal requirements?:
By due diligence before and during in-person meeting.

20. What types of data preparation will you support or require?:
No data preparation requirements under any circumstances. Service accepts any reasonably-sized opaque bytestream.

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
Manual, proprietary proccess.

Data Distribution

22. How many replicas will you require to meet programmatic requirements for distribution?:
3+

23. What geographic or regional distribution will you require?:
Entirely depends on data-owner request.

24. How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?:
3+

25. 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.

26. What tooling will you use to verify client deal-making distribution?:
Enforced by own proprietary allocator (see answer to 12)

27. How will clients meet SP distribution requirements?:
Enforced by own proprietary allocator (see answer to 12)

28. 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

29. Will you use standardized DataCap allocations to clients?:
Yes, standardized

30. Allocation Tranche Schedule to clients::
Per-sector allocation, see answer 12.

31. Will you use programmatic or software based allocations?:
Yes, standardized and software based

32. What tooling will you use to construct messages and send allocations to clients?:
Own to-be-developed tooling.

33. Describe the process for granting additional DataCap to previously verified clients.:
See answers to 30 and 12

34. 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 • disput:
Effectively all components of ♠️, but without the silly parts.

Tools and Bookkeeping

35. 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)

36. 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

37. Describe your proposed compliance check mechanisms for your own clients.:
See answers to 30 and 12

38. 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.

39. 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.

40. How long will you allow the community to provide feedback before implementing changes?:
Not applicable, see 39.

41. 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.

42. 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

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
No monetization of the datacap-allocation service under any circumstances.

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
This is a proud bus-factor-of-one operation.

45. Where will accounting for fees be maintained?:
As there will be no monetiation, no associated fees apply.

Past Experience, Affiliations, Reputation

46. 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.

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
I am ribasushi.

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
Napkin math.

[ribasushi]

@Kevin-FF-USA @galen-mcandrew @martapiekarska @willscott @dannyob

👋 folks

While my priorities have re-shuffled, I am still interested in getting this looked at eventually. Realistically somewhere around the Nov/Dec timeframe I could have a need for privacy-preserving allocation as described above.

I was told this application requires a resubmission. What does this mean procedurally?

[willscott]

The procedural process begins with https://github.com/filecoin-project/Allocator-Registry/issues/new?assignees=&labels=&projects=&template=Rolling_Application.yml

[ribasushi]

Mmmm @willscott this link suggests I need to restart the process from scratch.

Given the ☝️ existing application was trash-scored with no followup/explanation, and I do not intend to change the answers: is repeating the process the only path available?

If yes, the only path - can I at least get a commitment that someone will engage in on-the-record deliberation of the outcome?

[willscott]

For applications like yours which were rejected from the original allocator selection, I believe the path forward is to apply as a new application to the rolling application form. You're welcome to wait for governance to confirm.

[martapiekarska]

Yes, as I understand it - the right thing is to apply as an "experimental" allocator