Store POAP codes in DB about bankless-academy HOT 5 CLOSED

Maybe, we can avoid using POAPs here. They are more like "events". I would suggest maybe creating our own NFTs and work them out. Here are the reasons why I think POAPs will be a friction here.

1. POAP needs to have a start and end date. We won't have an end date here.
2. We will still need to manually mint a new tokes/POAP links every time we run out of them. We don't have a number here.
3. The work we will need to make POAP work will be similar to creating our own solution.

Potential Solutions:

1. Our own NFT, maybe on Polygon, as we have grant money from them.
2. POAP just came up with a new update today. I will be spending some time in testing that. If it is what I think it is, then our work there just got simplified.

Let me know your thoughts. I will ping you with an update by E.O.D tomorrow.

from bankless-academy.

For now POAPs are not a debate ... at least not for MVP1.
I already implemented them so I don't see the issue here ... all we have to do is store the codes inside a DB instead of using Notion (current solution).

We can have a long end date so I don't see the problem here.
Having to mint the POAPs manually is a good way to monitor how many POAPs have been claimed so far and making sure we don't get drained by bots.

from bankless-academy.

Okay, if we are fine with those things, then I can implement them. I guess it's better to go this route. Would you mind sharing the codes with me?

from bankless-academy.

Here is the current code for claiming POAPs: https://github.com/BanklessDAO/onboard/blob/main/src/pages/api/claim-poap.ts

Since this ticket is only very minor but requires a lot of context, I think it's better if I take care of this one.

Your value-add is definitely going to be higher on #11 since you already worked on the Moralis prototype.

from bankless-academy.

Sounds good

from bankless-academy.