[Phase 2] HIP-72: Grant to fund a PoH airdrop solution

Voting ended over 3 years agoSucceeded

HIP: 72
title: Grant to fund a PoH airdrop solution
author: green
status: Phase-2
created: 2022-06-29
conflicts with: None
languages: EN

Simple summary

Launch a grant to build an app to ease the process of airdropping to humans registered in PoH.

Abstract

Airdrops are the the currently most used feature of PoH and it would be in the general interest of the DAO to provide an easy way for philanthropists to airdrop tokens to its humans. This HIP sets up a grant to incentivize building such a tool.

Motivation

On making KIP-51, we came to realization that there is no such thing as a tool to airdrop to humans registered in PoH. Since the most interested party in the existence of such a tool is PoH DAO, and not Kleros DAO, it makes sense for PoH DAO to be the one that spends the resources needed for it to exist.

Other DAOs that are interested in performing sybil resistant airdrops could use it as an easy default allocation. Then, in the future we might see projects such as Optimism liberally drop tokens to PoH.

Specification

Upon completion of the PoH airdrop tool, send 3 ETH from the PoH treasury to the grantee, forer.eth. If PoH treasury does not contain enough funds but they are deposited in vaults generating yield (such as the UBI Burner), then this amount will be withdrawn from the vaults and then sent to forer.eth.

The tool will work in the following way:

Contract

Anyone can create an airdrop. They pass a token, an amount per human, the merkle root, a JSON file uploaded to ipfs with info to allow for redemptions, and an optional “fee” that will be awarded to whoever processes a redemption.
Anyone can redeem rewards to whoever was selected, that is, registered at the time. If fees are enabled, they will get a reward for delivering the airdrop.

Subgraph

Keeps track of airdrops, redemptions, and humans. Allows fetching information quickly from the frontend.

Frontend

If the user connects with a wallet with pending airdrops, they’ll be notified and will be able to trigger the transactions needed to withdraw them.
It provides a way for donors to create airdrops easily. Donors can create airdrops through passing parameters in a form, allowing their tokens, and then clicking on create. The frontend will then fetch all registered humans at the time, create a merkle tree, upload it to IPFS and then finally create the airdrop in the contract.

Rationale

Why not support NFTs

It would increase the complexity severely to handle both ERC20 and NFT in the same tool. Merkle airdrop tools benefit from fungibility. To reduce the time needed to ship the tool, reducing features was chosen as the approach.

Why self-select as grantee

Since I made the proposal in June 29, no one offered to take the grant. So, to avoid the proposal from getting stale, I advanced it to Phase 2 through selecting myself.