NateWebb03 / FilTestRepo

A test repository for allocator application automation
1 stars 0 forks source link

Test app 1082 #1084

Open NateWebb03 opened 5 months ago

NateWebb03 commented 5 months ago

Notary Allocator Pathway Name:

Nandit Mehra

Organization:

Lighthouse.Storage

Allocator's On-chain addresss:

f1x66qujypjp5miucjypizfdwruef6sbv33nxxpza

Country of Operation:

Singapore

Region(s) of operation:

Asia minus GCR,Europe,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.

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?

We bring our experience of building essential tooling in Filecoin and the FVM ecosystem at Lighthouse.Storage where we work with various clients and know what data can be valuable for the filecoin network. Lighthouse has a big focus on bringing many kinds of web3 applications to store on filecoin with use cases ranging from NFTs, Web3 social, Data availability, and much more.

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,Enterprise Data Clients

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.

Here are the 11 initial questions we will ask our clients:

  1. Please provide information such as the company's registered name, legal representative, and registered address.
  2. Is the company legally registered and operating in the region? If so, please provide relevant business registration information or business license.
  3. Please describe the data that you want to store through Lighthouse?
  4. What is the Filecoin address you would like me to allocate the DataCap to?
  5. Can you share a sample of the data? A link to a file, an image, a table, etc.
  6. What is the expected retrieval frequency for your data?
  7. For how long do you plan to keep this dataset stored through Lighthouse?
  8. What are your security and privacy requirements? Do they need encryption or access control?
  9. Do you have any preferences for where your data is stored geographically?
  10. What payment methods are preferred?
  11. Are you willing to sign a Non Disclosure Agreement?

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

We can use a 3rd-party "Know your client" (KYC) service if needed

Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)

Our channel will be open for any customer to apply and obtain the corresponding DataCap which means both our own internal clients and external clients can apply

How do you plan to track the rate at which DataCap is being distributed to your clients?

It will be done Manually by our team on google sheets

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,Private Commercial/Enterprise,Private Non-Profit/Social Impact

How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?

We will do an initial manual checks which will include some verification information like:

If required we will take up some KYB Services for further verification

How will you ensure the data meets local & regional legal requirements?

  1. After onboarding Client: Secure legal documentation related to location and data privacy from clients. Obtain commitments from clients to comply with relevant regulations. 2. Legal Compliance Assessment: Conduct a thorough review of local data privacy laws. Consult with legal professionals for expert insights. Make informed judgments on legal compliance based on relevant laws. 3. Dynamic Legal Adaptation: Actively monitor changes in data privacy laws globally. Continuously update compliance strategies to reflect the evolving legal landscape.

What types of data preparation will you support or require?

If required we can provide specific data preparation or integrations as and when needed

What tools or methodology will you use to sample and verify the data aligns with your pathway?

  1. Data Integrity Checks: We routinely download customer data to confirm its accuracy and adherence to agreed-upon specifications. This process ensures data preparation matches declared data types. 2. Random Verification Audits: To continuously monitor data quality, our team will randomly selects a small portion (e.g., 5%) of the data for in-depth download and verification in the background. This ongoing audit catches any potential issues. 3. Consequences for Abuse: If we detect misuse of resources or data, we will immediately halt the allocation of further quotas. Additionally, any unused data credits associated with the abuse will be automatically reduced.

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?

It’s quite flexible and we can expand to geographic locations as per the client’s request.

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

5+

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?

  1. Transparency and Consistency: To promote open allocation processes, we'll request public allocation plans on Github from clients. Subsequent applications will be assessed for plan consistency. 2. Public Scrutiny and Verification: Clients will outline their data allocation plans publicly on Github for transparency. During future applications, we'll ensure their plans remain consistent with their published versions. 3. Collaborative Commitment and Monitoring: We encourage public planning through Github for customer data allocation. Later applications will verify if plans remain aligned, fostering ongoing commitment and transparency.

What tooling will you use to verify client deal-making distribution?

It will be done by our team but we are open to explore open source tooling like AC Bot and CID checker datacapstats.io

How will clients meet SP distribution requirements?

Working with the client, we'll analyze their KYC and distribution plan for compliance and provide relevant information about the SP's reputation to enhance their due diligence.

As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?

No we don't encourage this because as the SP can be from a sanctioned country.

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:

We I will refer to the current FIL+ allocation rules

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?

Open source tools such as the current Filecoin Plus Registry

Describe the process for granting additional DataCap to previously verified clients.

Currently we will be doing it manually by Verifying the previous data cap. If it falls below 10%, the next round of allocation requests will be approved, but we are open to explore open-source tooling or other automated tooling.

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

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

We Will be using GitHub repositories and Google Sheets.

Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?

We will place the publicly available data in the public repository of our Github account apart from that there will be a public (View only) Google sheet maintained by our team.

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.

Regular inspection and tracking is a key step in ensuring data compliance and security. Here are the specific plans we will implement: a. We will communicate with the client on a monthly basis and the client should provide an update on their progress b. Tracking DataCap allocation and client usage with CID Checker, AC Bot and DataCapstats.io We welcome new clients, but new clients are also required to follow Fil+'s rules and participate in line with the laws and regulations of their country of location.

Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.

To establish trust and confidence in Filecoin's dispute resolution process, we prioritize building a transparent, efficient, and fair mechanism for data storage and retrieval that empowers all relevant parties. Here's how: Internal Dispute

External Disputes:

Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.

Any changes will be posted in the fil-plus channel in Slack with advance notice. Relevant update announcements will also be posted in GitHub.

How long will you allow the community to provide feedback before implementing changes?

We'll leverage diverse feedback mechanisms to ensure inclusive decision-making:

We value your input! We're committed to collaborating with the community through the notary governance GitHub repo. If your feedback makes logical sense and aligns with our team's vision, we'll implement changes together.

Ongoing Engagement:

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?

It will be controlled by our team with a access on the cold wallet

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

n/a

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.

This strategy focuses on selling storage deals to miners through two primary methods: auctions and commissions. Selling Storage Deals:

Auctions: Platform: Leverage a platform like BDE (Big Data Exchange) to host transparent and efficient auctions for storage deals. Deal types: Offer various deal types with different durations, storage capacities, and pricing tiers to cater to diverse miner needs.

Commissions: Partner with miners: Establish partnerships with large, established miners who have a network of smaller miners seeking storage solutions. Commission Structure: we would be the sales team for these miners. Every time we get them enough customers to fill a sector, they pay you a commission

Describe your organization's structure, such as the legal entity and other business & market ventures.

Web3 tech labs pte. Ltd is a Singapore registered entity

Where will accounting for fees be maintained?

None

If you've received DataCap allocation privileges before, please link to prior notary applications.

N/A

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

Active builder in the ecosystem. Protocol Labs is an investor.

How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?

Yes we have existing clients using Lighthouse CLI, SDK, Files dapp to onboard to filecoin.