Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merkle Drop Dapp Requirements #3

Open
8 tasks
META-DREAMER opened this issue Aug 6, 2021 · 1 comment
Open
8 tasks

Merkle Drop Dapp Requirements #3

META-DREAMER opened this issue Aug 6, 2021 · 1 comment

Comments

@META-DREAMER
Copy link
Contributor

META-DREAMER commented Aug 6, 2021

Overview

A simple dapp to curate and publish "token distributions" from various projects / communities. Allow anyone to see the curated list of token distributions and permissionlessly merkle drop any tokens to the same recipients proportionally.

MVP requirements

  • As a curator I should be able to upload a CSV file containing eth addresses and token amounts in order to generate a merkle root

  • As I curator I should be able to assign / label these merkle roots with the community / project they are from

  • As a curator I should be able to publish this merkle root on chain so it can be used by others to airdrop tokens to the same people

  • As a curator I should be able to update the merkle root for a given community project with new token distributions (e.g. for communities doing new distro's every month to contributors)

  • As a whale I should be able to see the curated list of merkle drops so I can decide where to allocate my tokens

  • As a whale I should be able to merkle-drop any amount of any token to any of the published merkle roots

  • As a recipient I should be able to see all the merkle drops I have received tokens from so I can have one place to find them all

  • As a recipient I should be able to claim the all tokens from a merkle drop in a single transaction

Notes

A good place to store / manage the merkle root data would be Ceramic. It allows for the files to be version controlled and verifiable so that there's a version history of the merkle roots as they changed and there's a cryptographic proof that the allocation was correct / signed by the community multisig/dao/etc. (e.g. gitcoin.eth publishing the distribution data on all the GTC recipients).

The suuuuper MVP version could even be without any of the contracts, just a place to upload and share token distributions.

We can target any DAOs using Coordinape and/or SourceCred and get all their regular distributions added into the list seamlessly.

Cool things we can do post-MVP:

  • setup ENS addresses like merkle.metafam.eth where anyone can send any token to that address and have it automatically distributed to that community
  • allow these lists to be composed so people can aggregate / curate the drops further. e.g. a "MetaCartel Ecosystem" list that is composed of the merkle drops of all MC related
  • or for communities that are doing new distributions every month, letting people distribute tokens to many or all of the previous months instead of just the current one
  • Dogfood it by getting some of the DAOs we are in to do "token swaps" between eachother by distributing their native tokens to the other DAOs recipients.
@META-DREAMER
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant