Banyan Storage Notary Allocator Application

[Tim-Yong]

v5 Notary Allocator Application

To apply to be an allocator, organizations will submit one application for each proposed pathway to DataCap. If you will be designing multiple specific pathways, you will need to submit multiple applications.

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+"): Banyan Storage
2. Organization Name: Banyan Storage
3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): f13p5obq3umad3yk6ukutr72ha6rj2sipqxjfb6xy
4. Country of Operation (Where your organization is legally based): US
5. Region of Operation (What region will you serve?): US
6. Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase): Manual
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): 10 PiB

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.

[Kevin-FF-USA]

Hi @Tim-Yong
Thanks. Wanted to send you a friendly note confirming receipt of this application.

Should you have any issues or questions in the process - please tag me in here and I'll be happy to help.

-Kevin

[ghost]

Providing the information shared in Application for Public Review/Comment.

Basic Info

1. Pathway Name:
Banyan Storage

2. Organization:
Banyan Storage Inc.

3. Allocator's On-chain addresss:
f13p5obq3umad3yk6ukutr72ha6rj2sipqxjfb6xy

4. Country of Operation:
US

5. Region(s) of operation:
North America,Europe

6. Type of allocator:

Manual

7. Amount of DataCap Requested for allocator for 12 months:
20 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?
Banyan is a decentralized end-to-end encrypted storage platform designed to support a variety of enterprise workflows. Those workflows include transitioning data between hot and cold (Filecoin) states seamlessly through their choice of interface. Our customers are able to upload and access their data without intervention from Banyan and their data is kept private through the whole process. Banyan uses Filecoin Storage Providers as infrastructure and those SPs are under legal contract that includes SLAs. Clients of Banyan storing > 10 GB must PAY fiat in order to use the platform.

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

[ghost]

Client Diligence

10. Who are your target clients?
Small-scale developers or data owners,Enterprise Data Clients,Individuals learning about Filecoin

11. Describe in as much detail as possible how you will perform due diligence on clients.
We don't need to. They're paying money to use the platform. Imagine if Backblaze or DropBox performed KYC on all their clients - people would use their competitors instead.

12. Please specify how many questions you'll ask, and provide a brief overview of the questions.
We won't ask any.

13. Will you use a 3rd-party "Know your client" (KYC) service?
No.

14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)
Clients don't do anything. They just want to store and access their data. Banyan would allocate datacap to the SP storing that clients data on Filecoin if they want to do this as verified deals, otherwise it'll be done as unverified deals.

15. How do you plan to track the rate at which DataCap is being distributed to your clients?
Using whatever tooling is out there. If nothing exists, then I guess in a database or spreadsheet.

[ghost]

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, transmitting, or accessing of data.
Acknowledgement: Acknowledge

17. What type(s) of data would be applicable for your pathway?
Public Open Dataset (Research/Non-Profit),Public Open Commercial/Enterprise,Private Commercial/Enterprise,Private Non-Profit/Social Impact

18. How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
We don't. First of all, we can't see it because it's encrypted. Secondly, the client has to pay money to store. So... if they want to pay money to store data that they don't own, then that's their prerogative. If we did find out about it, and it goes against our acceptable use policy, we'll put an end to it though.

19. How will you ensure the data meets local & regional legal requirements?
We can't. The data is encrypted client side using keys only they cont rol before it gets uploaded. But if they're ever found in violation of any laws or our acceptable use policy, we'll put an end to it.

20. What types of data preparation will you support or require?
Banyan custom

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?
Banyan has custom prep and will pack the sectors. Again, clients must pay to store so even if they could pad sectors, which they can't because they're just users, they'd be paying for it.

[ghost]

Data Distribution

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

23. What geographic or regional distribution will you require?
At least two different physical locations. But which regions is determined by what the client wants and their data locality requirements.

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

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?
No and no. The client knows nothing about datacap and knows no difference as to whether a deal is verified or unverified.

26. What tooling will you use to verify client deal-making distribution?
Banyan custom

27. How will clients meet SP distribution requirements?
They won't. They know nothing. Banyan will determine which SPs will store the clients data based on the clients requirements.

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
N/A - clients don't engage directly with SP's. Banyan is the broker.

[ghost]

Datacap Allocation Strategy

29. Will you use standardized DataCap allocations to clients?
No, client specific

30. Allocation Tranche Schedule to clients:
N/A - the client knows nothing about datacap. If an SP of ours wants to store client data thats destined for them to store as verified deals instead of unverified deals, we'll grant datacap to make that happen.

31. Will you use programmatic or software based allocations?
No, manually calculated & determined

32. What tooling will you use to construct messages and send allocations to clients?
Undetermined but we can use whatever existing standard tooling.

33. Describe the process for granting additional DataCap to previously verified clients.
N/A - we don't need to verify clients. If they're storing on our platform, they're paying us money. Our clients won't ask for datacap. They don't know what it is.

[ghost]

Tools and Bookkeeping

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
• dispute discussion & resolution
• community updates & comms
Undetermined.

35. Will you use open-source tooling from the Fil+ team?
Undetermined

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?
Undetermined where we'll keep our records for bookkeeping. Whatever needs to be recorded and shared, we can make that available. Transparency? N/A - again because of our situation of storing encrypted data that clients are paying for

[ghost]

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.
N/A - again because of our situation of storing encrypted data that clients are paying for.

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
We have legally binding contracts with our SP's that include an SLA. Not worried there. When it comes to other parties, if somebody has a dispute they can come to us and we'll discuss it like civilized people. If you need more than that, let us know what you want.

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
Write it in a document and send to whoever/wherever. Unless you guys want something else, open to suggestions

40. How long will you allow the community to provide feedback before implementing changes?
How long? I don't know, you tell us what you think is reasonable

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?
Use a Ledger. Any secret information will be kept in our corp password manager which has tightly controlled access.

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
N/A

[ghost]

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.
We are currently not monetizing this at all. If our SPs are given deals that they happen to want to make verified deals because they're willing to put up 10x collateral and get more QAP for that, then they'll be given that. It's for their benefit.

44. Describe your organization's structure, such as the legal entity and other business & market ventures.
Just a single corporation.

45. Where will accounting for fees be maintained?
Undetermined - we can provide a link or whatever you want.

[ghost]

Past experiences, Affiliations, Reputation

46. If you've received DataCap allocation privileges before, please link to prior notary applications.
filecoin-project/notary-governance#742

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
Banyan is well known in the Filecoin ecosystem. Part of PLN as PL has invested.

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
We have customers in the pipeline awaiting feature releases to onboard