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

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

Closed
amy-jung opened this issue Feb 5, 2020 · 2 comments
Closed

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

amy-jung opened this issue Feb 5, 2020 · 2 comments
Assignees

Comments

@amy-jung
Copy link
Contributor

amy-jung commented Feb 5, 2020

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:

  • opening a Vault/CDP
  • vote in a governance poll
  • vote in an executive
  • use the DSR
  • transfer 100 DAI, transfer 1000000 DAI, etc
  • locked MKR in chief for over 180 consecutive days, 365 days, etc

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 ethereum/EIPs#1238 and ethereum/EIPs#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 amy-jung self-assigned this Feb 5, 2020
@amy-jung amy-jung added this to Backlog in Community Development via automation Feb 5, 2020
@amy-jung
Copy link
Contributor Author

amy-jung commented Feb 5, 2020

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

@twblack88
Copy link
Contributor

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

Community Development automation moved this from In progress to Done Oct 15, 2020
blimpa pushed a commit that referenced this issue Apr 2, 2021
…sby-remark-responsive-iframe-2.4.13

Bump gatsby-remark-responsive-iframe from 2.4.12 to 2.4.13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants