search

makerdao / community

Contains current and historical governance polls and executives used in the governance of the Maker Protocol. Previously contained a lot of other content which remains in the 'prior-cleanup' branch.
https://forum.makerdao.com/
GNU Affero General Public License v3.0
193 stars 161 forks source link

CDIP 2 - Non-transferable Badges for Maker Ecosystem Activity #433

Closed amy-jung closed 4 years ago

amy-jung commented 4 years ago

Title: Non-transferable Badges for Maker Ecosystem Activity

Your name/handle: @ lix

Links to Github issue/forum post/ or discussion thread: https://chat.makerdao.com/channel/general?msg=ukvxuysoTugky9aY9

Proposal abstract: A video game like “achievement” would be a fun way to engage users. It gives all participants (large and small) a way to be proud of their on chain activity and show off to their peers. These badges would only have personal value since they would be non-transferable. Some ideas for individual badges which users could claim:

Much of the implementation for an idea like has already been done here: https://github.com/poapxyz/poap

I think Mariano Conti did a poap NFT for his birthday party, so ask him how it went if you’re exploring this idea. The only difference is that the poap smart contract would have to be changed to not allow transfers of the badges. Or, if transfers were allowed, they would only be allowed by the owner address. I’ve looked into non-transferable badge EIPs such as https://github.com/ethereum/EIPs/issues/1238 and https://github.com/ethereum/EIPs/issues/735 The non transferable claim seems to have gained the most traction so far in the ethereum community, but it is still hard to see a clear winner as far as which claim standard will become mainstream.

From Maker's point of view, here is how the badges would work:

On the backend, we run a script every hour that checks for new badges. User 0xabe1 logs into metamask, goes to badges.makerdao.com If 0xabe1 is on the list of claimable badges, then we sign a message with our issuance key saying that “0xabe1 can claim the DSR badge at 0x2345” The user signs the signed message above. This proves that both parties want the badge issued, and the issuer (Maker) can execute the transaction and issue the badge. Maker pays the gas for this transaction.

CDIP2

amy-jung commented 4 years ago

Was approved to move forward into execution. Unfortunately Lix ran out of bandwidth to continue. It's open for others to tackle

twblack88 commented 4 years ago

I think with the closing of #536 this is all set!