Create File of Airdrops to Lobters

[nullbitx8]

Description
This isn't meant to be a lengthy proposal or something that requires LOBS payment.
I'm just gauging interest for adding a file to the github repo that shows the details of airdrops/benefits coming to lobster holders.

The file could become a place where projects that are dropping something to LOB holders can come add their info by submitting a pull request.

There is currently a list in telegram being compiled by @LyrrraD that has info on benefits to Lobsters.
The idea is having it here on Github would be easy for everyone to reference and contribute to.

Suggested Format

Date	Name	Contact	Description
October 31	Zombie Lobsters	t.me/zombie-lobs	For Halloween, we will be dropping some spooky monsters to you crustaceans! Boo!
October 23	Mew DAO	discord.gg/fake-link	Our DAO focuses on collecting teh rarest pokemons, and we want active community members as part of our community! Join our Discord for more info...

Prior Work
There's a thread in telegram by @LyrrraD that's currently compiling a list of benefits to Lobsters.
https://t.me/lobsterdao/9219

Implementation
If this issue gets a good response I'll create a pull request.
And if there are any ideas on how this could be done better, let's discuss and I will help in working towards implementing it.

[ethisscam]

em. Very good point! But I think this can be a general curated list of LOBS holder benefits while not only limited to airdrops. Anything such as a whitelist, merch, gateway, discount can be added to the list.

[boqiboy]

That`s great, will be highly appreciated

[nullbitx8]

@ethisscam that makes sense! Maybe we can add sections then like

Q4 2021 (Oct - Dec)

Airdrops

Date	Name	Contact	Description
October 31	Zombie Lobsters	t.me/zombie-lobs	For Halloween, we will be dropping some spooky monsters to you crustaceans! Boo!
October 23	Mew DAO	discord.gg/fake-link	Our DAO focuses on collecting teh rarest pokemons, and we want active community members as part of our community! Join our Discord for more info...

Discounts

From - To	Contact	Description
Oct 1 - Nov 30	t.me/web3-tools-fake	We have a discount for all Lobsters! Connect your wallet to our site at web3-tools.fake to activate yours!

Merch

From - To	Contact	Description
....	....	....

Etc...

[kkkrackpot]

We need a pitch letter for projects -- "Why you must airdrop to lobsters!"

[Ribssss]

We need a pitch letter for projects -- "Why you must airdrop to lobsters!"

I'm not sure that's a good idea. If we start trying to explain why we are the ones who "deserve" an airdrop then projects will want us to guarantee their promotion and that is not the spirit of lobster at all.
We might even end up with twitter contest ^^
Please

[phantohm]

I support this idea. Great way to get people engaged and to raise awareness on new or updated projects.

[IvanGBi]

Looks cool!

[wugamlo]

Considering all the "Minter" vs "Holder" discussions, it might make sense to also clearly state the eligibility criteria.

[IvanGBi]

Considering all the "Minter" vs "Holder" discussions, it might make sense to also clearly state the eligibility criteria.

That can't be "stated" because each project would decide for themselves. See #25

[1a35e1]

Considering all the "Minter" vs "Holder" discussions, it might make sense to also clearly state the eligibility criteria.

I think I think the DAO could surface various (DAO approved) lists and then it's up to the project to elect how they airdrop to LOBS.

excuse pseudo code

GET /lobsters?filter=minters|holders&sort=???


type Address = string

interface Lobster {
  account: Address
}

interface NFT {
  mintedBy: Address
  owner: Address
  transfers: int
  ... traits
}

To keep it simple we could do this in a credible decentralised manner?

i.e open source the code so its verifiable and then deploy on Vercel/Netlify functions so its accessible over a HTTP/GraphQL api.

[wugamlo]

Considering all the "Minter" vs "Holder" discussions, it might make sense to also clearly state the eligibility criteria.

That can't be "stated" because each project would decide for themselves. See #25

Apologies, "state" was the wrong word for what I wanted to say.
After the eligibility criteria have been decided and communicated by each of the projects, this information could be added to the list. This will add to the transparency for all participants.

[norswap]

Someone put together this spreadsheet that seems to accomplish what this issue asks for.

[nullbitx8]

Thanks @norswap that's helpful!

I see a tradeoff here, up to us to decide what's more important.

Google sheet is fast and easier to edit than a pull request. Less friction to post.
Google sheet is permissionless, anyone can edit and enter potentially bad/wrong info.

Github file is slower to edit.
Github file is permissioned via pull request. Safe(r) against bad info or deletion.

I'm going to create the PR anyway just because I have time now, but let's discuss.
My vote would be for Github file mainly to reduce spam / bad actors.

[nullbitx8]

I just realized that the spreadsheet is restricted and LyrrraD is managing edits / requests.
In that case I think it makes sense to close this issue and move forward with the spreadsheet for now.