CDIP 38- Badges Dev Ops

[twblack88]

Title: Dev-ops for Maker badges on mainnet and full-stack micro-services.

Lead: @creativekoder + @naszam

Adviser: @twblack88

Historic context from GitHub issue/forum post/discussion thread: This proposal ties: CDIP 15/26/29 in a bow. Putting the redemption front end and discourse theme in a unified place for issues, management, and PR’s. Also matches a staging/dev environment with a live environment.

Proposal: Now that the contracts for badges have had time to mature for mainnet deployment, and Scott has moved onto other things, the badges team needs to align resources together and push the final piece into place

Deliverables:

• [x] OpenZeppelin Defender Admin Dashboard with
• [x] Documentation for templater changes
• [x] Mono repo owned by multiple people
• [x] Staging setup matches production
• [x] Devops pipeline alignment
• [x] Continuous integration tools
• [ ] Discourse plugins/themes documentation
• [ ] Lambda Badges API documentation
• [x] Front end (domain, includes, contracts) included in mono
• [x] Digital ocean server | multiple password holders

Next Steps

• [ ] Mainnet deploy
• [ ] [Design] Leaderboard spec for discourse
• [ ] 3 signers (Gnosis Safe Multisig, 3 accounts, 2 signers required)
• [ ] OpenZeppelin Relayer (Admin Role) AutoTask to set Root Hashes Daily
• [x] List of future badges to build
• [x] [Design or whimsical flow chart] Badges front end <> Lambda <> Contracts
• [x] Scoping meta transactions or biconomy for the front end

Design

• [ ] Robot challenge
• [ ] Chai challenge

[twblack88]

This was approved on 12-7 with four members in attendance.

[twblack88]

CDIP 38 Retro

Summary

CDIP 38 completed with badges almost ready to deploy to Mainnet. The biggest blockers are simple: gas costs and the closed access to MakerDAO's GraphQL query. There are proposed solutions for both. Along the way towards cleaning up the front-end code base, we also discovered plenty of opportunities to improve, and got the maintenance cost down to $50 a month.

Retro

You can see a full retro of what went well, what needed improvement, and what's next here.

Takeaways & Helpful Links

Abandoning a code base makes it really difficult for people to pick up the work afterward. It's recommended that code is either clean or at least some level of documentation exists for any small project within the greater MakerDAO ecosystem.

The CDIP framework, even stringing together each one after the other, was not a great fit for this kind of R&D heavy engineering work. To just get badges onto the forum requires several workarounds technology obstacles & access problems. It's part of the reason these are still not redeemable on mainnet for someone's wallet. With the DAO growing up it's hard to find the right budget for these badges, as of writing. The team has faith that that will happen, because the project is too valuable to Maker not to create fascinating interactions with on-chain badges and actions.

The team presented a core unit for the comm-dev hackathon, with an idea of creating DeFi 2.0 (inspired by the web2.0 movement). The team currently has dubbed this: "social defi." Feedback can be found in this doc.

There was a myriad of other documents produced over the year of engineering work that went into these ideas including:

• A formal Smart Contract assessment

• Notion Page(s) of badges at a high level, meeting notes, the chart of badges, and other relevant repos.

• User redemption flow

• Current challenges - with less fields than the notion :point_up_2:

• @naszam repo of smart contracts

  • Including this diagram of the badge contract interactions.

• Discourse component plugin

• Merkle service

  • MakerDAOx UI

  Next steps

• Preferred: Grant for Maker Badges on xDai

• Possible: Directly engage with Governance, get a signal, put up MIP14 propose a MIP for on-chain actions and xDai deploy.

• Unclear: Find a core unit or two to work on the Smart Contracts and the rest of the stack.