[Allocator Application] <LaughStorage>< LaughStorage Allocator> PR #73

[martapiekarska]

Allocator Application

Application Number

recIj2bMwnNSJ3JsU

Organization Name

LaughStorage

Organization On-chain Identity

f1rezheyjsdejlxgssaqkvtg5buhsiubevgsbyjsa

Allocator Pathway Name

LaughStorage Allocator

Github PR Number

73

Region of Operation

Greater China Region

GitHub ID

26dos

On-chain address

I have a multisig I want to provide now

Type of Allocator

RFA

Filecoin Community Agreement

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, allocator, or other operating entity Acknowledge

Type of Allocator and RFA List

RFA: Automated - Client staking

Allocator Description

Contributions to EcosystemDevelop Open-Source Tools,Build better data onboarding pathway,Onboard >10PiBs of Data

Monetization and Fee structure

Client staking.

Target Clients

Web3 developers,Nonprofit organizations,Commercial/Enterprise,Individuals,Open/Public

Client Diligence Check

On-chain deal pricing,Automated deterministic

Description of client diligence

I will create a staking smart contract that automatically binds the client's wallet address, equivalent to automated identity authentication.  The requirement here would be that the client needs to stake a certain amount of FIL up front to receive the DataCap. The allocation size is dependent on how much they choose to stake. 

Type of data

Private encrypted with on-chain deal pricing,Public, open, and retrievable

Description of Data Diligence

At present, the only way to verify data is for customers to provide provable sample data. Because pre-staking contracts will manage my pathway. There are two types of data: 1. Public data sets. Such clients need to provide sufficient sample data links, and the retrieval rate after data upload must reach at least 70%. For such clients, the period of their pledged fil will be shorter than that of private clients because their content is verifiable. If their packaging situation does not meet the requirements, then we have the right not to proceed with the next round of approval. 2. Privacy data sets. Such clients will focus on checking the client’s background when applying for dc, because their data is privacy-encrypted, so their pledge period needs to be longer than other customers.

Data Preparation

Client-provided,Go-CAR,IPFS Kubo,Singularity,RIBS,Other existing ecosystem tooling

Replicas required, verified by CID checker

3+

Distribution required

Equal distribution of deals across regions

Number of Storage Providers required

3+

Retrieval Requirements

Public data highly retrievable over Spark.

Allocation Tranche Schedule TypeManual or other allocation schedule.

Pledge Logic: A. Public Dataset:

1. Submit Application Form: The maximum size of a single application form is 2PB. The application form should contain complete information and substantial sample data. 2.Allocator Review: The allocator reviews the application form. Upon approval, based on the customer scale, 10-50TB will be allocated for the Service Provider (SP) to perform encapsulation verification. 3.Data Verification: The SP downloads and verifies the public dataset. If the data content and node match the application form, the customer is notified to proceed with the pledge.
2. Client Pledge: The client pledges FIL based on the application amount. The maximum application amount is 2PB, and the client must pledge FIL corresponding to the remaining balance in a single transaction. 5.Signing and Encapsulation: The allocator signs off, and the SP performs the encapsulation. *Pledge Cycle: The pledge cycle for public datasets is 20 days. The rate is 10TB = 1 FIL, and the pledge is automatically returned to the pledge address upon maturity. 6.Reapplication: If the client has more data, they can submit a new application form (each form cannot exceed 2PB). Trusted clients can skip the review process, but any updates must be disclosed in advance.

B. Private Data: 1.Submit Application Form: The maximum size of a single application form is 1PB. 2.Allocator Review: The allocator reviews the application form, focusing on verifying the customer's identity and the corresponding SP information. 3.Client Pledge: Upon approval, the allocator notifies the customer to pledge the requested amount. 4.Signing and Encapsulation: The allocator signs off, and the SP performs the encapsulation. *Pledge Cycle: The pledge cycle for private data is 40 days. The rate is 10TB = 1.5 FIL, and the pledge is automatically returned to the pledge address upon maturity. 5.Reapplication: If the client has more data, they can submit a new application form (each form cannot exceed 1PB). Trusted clients can skip the review process, but any updates must be disclosed in advance.

Will you use FIDL tooling, such as allocator.tech and other bots?

Yes, all available tools

GitHub Bookkeeping Repo Link

https://github.com/26dos/AllocatorBookkeeping

Success metrics

Number of clients,Amount of data onboarded, daily & aggregate,Number of paid deals

Timeline to begin allocating to clients

1 month from RKH approval

Funnel: Expected DataCap usage over 12 months

100-200PiB

Risk mitigation strategies

Audit & Penalty: If the following situations occur, the customer and all corresponding nodes will not be approved again in this channel:

1. The node number/number of nodes/number of backups and regional distribution described in the application form content are inconsistent with the actual situation;
2. There are any cid sharing issues;
3. The public data set cannot be retrieved

Dispute Resolutions

Customers have the right to explain their application forms, and customers need to respond to allocator's questions within 48 hours. Allocator needs to give a clear response to the questions within 72 working days.

When allocator is questioned, it needs to provide verifiable and recorded evidence to respond. At the same time, the questioning needs to be based on reliable evidence to be effective. Efficiency needs to be guaranteed, and disputes must be resolved within 7 working days.

Compliance Audit Check

As I said, applications for public data sets will first have a small amount (no more than 50t) allocated for node and data verification; the rest will be reviewed through public tools.

Compliance Report content presented for audit

Success metric: Proof of Payments from clients,Success metric: onchain report of data onboarded,Data Compliance: Data Samples,Data Compliance: Manual report,Compliance: CID report.

Connections to Filecoin Ecosystem

Storage provider,Developer

Slack ID

Laugh Storage

[26dos]

Dear @Kevin-FF-USA

I hope this message finds you well. About two months ago, I submitted an application for a project focused on developing an automated tool that would assist clients with the pledging process. As we continue to make progress with the tool’s development, I wanted to kindly inquire about the status of my application.

If there are any suggestions for improvement or additional feedback from your side, I would greatly appreciate it. Please feel free to communicate any thoughts or adjustments you may have, as we are eager to align with your expectations.

Thank you for your time, and I look forward to hearing from you.

Best regards, Laugh Storage

[Kevin-FF-USA]

Hi @26dos,

Thanks for the follow up note. I took a look at this application and have some notes on details that would need to be provided. Not sure if you were able to join the recent calls, but wanted to send a friendly check and see if this organization was still interested in pursing a role as an Allocator in the Fil+ program, coming to the calls is a great way to get information and learn much about the application process.

If so, have initial feedback on this application. Seeking more clarification on how this pathway will actually operate. Requesting some more additional details to help establish this pathways ability to operate as RFA: Automated - Client staking. Once received, will enter into this scoring rubric.

Allocator Description Describe how the automations will take place. What tooling will be used. How the clients will be verified with their staking. Is there a website for LaughStorage? Is there a past Filecoin ecosystem project that this org has been a part of?

Monetization What is the staking process? Fil or fiat? How is it communicated? How is it tracked?

Client Diligence Check Automated deterministic - what are the metrics you will take from Github? What is the automated program you created. Is there an MVP running for testing/verification?

This information will help start the scoring mechanisms for this pathway. Once we receive this additional information we can begin testing the applications of this pathway for meeting the program goals to onboard as an Allocator.

For questions or support There is a live Filecoin Plus Program call every two weeks. Calendar link is here. Or as always please tag us in issue for comment or update

[26dos]

Hi @Kevin-FF-USA

I can confirm that we are still interested in taking on the role of an Allocator, and we will participate in the upcoming calls.

Regarding our automated staking, we have completed the development of the smart contract and provided the necessary tools for applicants. Here is a brief description of the process:

1.  The client submits an application form.
2.  We will review the process via GitHub and provide the staking method to the client.
3.  The client can use the tools we provide to stake FIL.
4.  The staking process and the refund process are clearly outlined in the contract.
5.  Once the client completes the staking, we will allocate DataCap (DC).

In the contract, we have set the limits for DC and the required staking ratio, and we have also established the rules for the refund of the client’s FIL.

For the client diligence check, we will primarily focus on tracking the client’s retrieval rate, node distribution, and data backup status. Additionally, below are the GitHub links to the staking tool and the staking contract that we have completed:

•   Staking Tool: https://github.com/26dos/Laugh-Storage-staking-tool
•   Staking Contract: https://github.com/26dos/staking-tool-contract

[26dos]

Hello, @Kevin-FF-USA Could you let us know what additional steps we need to complete to move on to the next stage?

[26dos]

Hello, @Kevin-FF-USA

https://drive.google.com/file/d/1tEZ5BBPP7V4zwlIEpzR9vp7VaNHraUmk/view?usp=sharing

Here is a link to our demo video showcasing the staking contract and staking tool. In the video, we demonstrate the entire process, from FIL staking to the retrieval of funds upon maturity. Our staking tool makes it simple for clients to complete these operations, and the contract is deployed on-chain, ensuring that the entire process is managed and controlled by the contract.

Additionally, in the coming months, we plan to continuously optimize this staking tool, including the development of a user-friendly, visual front-end interface. This will make it even easier for clients to onboard and use the tool.

[26dos]

@Kevin-FF-USA Is there anything else we need to do? If there are any issues, please let me know. Thanks.