filecoin-project / Allocator-Governance

7 stars 33 forks source link

[Allocator Application] <Filecoin Incentive Design Labs>< Gitcoin verified Allocator> #56

Closed martapiekarska closed 2 days ago

martapiekarska commented 3 months ago

Allocator Application

Application Number

recwGYDP5qLv2Z0I3

Organization Name

Filecoin Incentive Design Labs

Organization On-chain Identity

f1v24knjbqv5p6qrmfjj5xmlaoddzqnon2oxkzkyq

Allocator Pathway Name

Gitcoin verified Allocator

Github PR Number

54

Region of Operation

North America

GitHub ID

kevzak

On-chain address

f2g24hk5zgpguw2netrc22mv34gtrbdevph22zdpa

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

Allocator Description

require identity verification of 30+ points on gitcoin.passport.io

Contributions to EcosystemBuild better data onboarding pathway

Monetization and Fee structure

None.

Target Clients

Open/Public,Individuals,Nonprofit organizations,Web3 developers

Client Diligence Check

Client promise/attestation

Description of client diligence

KYC portal check: client to visit passport.gitcoin.co client to validate their identity with a score of 30+ client to bring passport onchain to optimism client to sign a message in their wallet to get eth address

Type of data

Private encrypted with on-chain deal pricing,Public, open, and retrievable,Proof of concept, network utilities

Description of Data Diligence

Only using the KYC portal check. If client has a score of 30+ on gitcoin passport, then they are marked as KYC completed.

Data Preparation

None

Replicas required, verified by CID checker

1+

Distribution required

Single region of SPs

Number of Storage Providers required

1+

Retrieval Requirements

Data retrievable over other standard. not required

Allocation Tranche Schedule TypeSingle size allocation.

64

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

Yes, some tools

GitHub Bookkeeping Repo Link

github.com/fidlabs

Success metrics

Number of clients

Timeline to begin allocating to clients

1 month from RKH approval

Funnel: Expected DataCap usage over 12 months

<5PiB

Risk mitigation strategies

check for growth of new clients accounts

Dispute Resolutions

Disputes can go to governance team. There is nothing to dispute to the allocator of an automated KYC check that provides 64GB DataCap

Compliance Audit Check

provide list of KYC checks complete

Compliance Report content presented for audit

Client Diligence: Client statements, client provided verification.

Connections to Filecoin Ecosystem

Previous allocator

Slack ID

@KZ

galen-mcandrew commented 3 months ago

Pathway for GitCoin autoverifier is ready to be approved, but missing some details.

Specifically:

Can we get some more details @willscott & @kevzak ?

martapiekarska commented 3 months ago

Hi @galen-mcandrew jumping in here.

Sorry for a scarce application, we should have put in more details, but I guess the idea wasn't fully crystalised in our heads before submission. This application is for an automated META-allocator with the gitcoin passport verification as a first pathway in that metaallocator. As we read in the blogpost on blog.allocator.tech this is the desired structure:

image

FIDL team has worked with Neti on a Smart Contract that would be able to automate the DataCap allocation to allocators and to clients, you can find the code here: https://github.com/fidlabs/contract-metaallocator. The code has been audited and minor issues were found and fixed. We published the audit here: https://www.fidl.tech/tools/updates.

We would like to Receive the 5PiB allocation to a metapathway f4 address that will feed into the Gitcoin Passport automated allocator pathway that will be a replacement for the Glif github-based system that is no longer operating. That ensures that even in case of compromise of the allocator, we will not automatically give away 5PiB allocation at once, and also start testing the meta-allocator code with a relatively small amount of total datacap.

willscott commented 3 months ago

the original issue is updated with the deployed metapathway contract, at f2g24hk5zgpguw2netrc22mv34gtrbdevph22zdpa (equivalent to f410fhbxqr5xi4rshxbyucxv7xbmldy3x3gvsjrcnply)

galen-mcandrew commented 3 months ago

RKH have completed this approval, DataCap is now on chain.