Finished

JBP-123: Renew & update DrGorilla.eth recurring payout

Author

Anon

Cycle

17

loading

After a trial period of 1-3 cycles, contributors are encouraged to propose a recurring role for themselves. Recurring payouts should be renewed/updated every 90 days.

Author:

@Dr Gorilla

Proposal date:

2022-02-25

Summary:

Renew the 90-days recurring payout of DrGorilla.eth (contract engineer), from FC#17 to FC#23 included (90 days)

Risks:

Lack/absence of productivity

Payout recipient:

drgorilla.eth

Payout amount:

9694.20

How have you contributed to the DAO?

  • Some highlights:
    • Found & suggested fix for critical vulnerability in the V1 the rescue terminal (a reentrancy that might have allowed a bad project owner to drain the whole contract balance).
    • Found & suggested fix for a critical overflow allowance issue in V2 (a missing assertion that might have allowed someone with an allowance to empty the whole treasury of the related project).
  • Currently 3 work in progress (unit test of ballot using Foundry, allowance fix & fee precision adjustment), 3 open PR and 19 merged (https://github.com/pulls?q=is%3Apr+author%3Adrgorillamd+archived%3Afalse+is%3Aclosed+user%3Ajbx-protocol). Those were mostly tests (unit and system tests) and bug fixes.
  • While the proposal doesn’t target it, I’ve started and push for the launch of Moody’sDAO (providing clear and concise information about projects living on Juicebox, to our community, to give them food for thought in terms of investment decisions) - https://twitter.com/MoodySdao
  • Consistently shitposting against the BSC Scam which popped up recently. Hopefully, some people saved their money after seeing a tweet/telegram/discord post message.

How do you want to contribute to the DAO going forward**?**

Pursuing my role as a contract engineer, including but not limited to:

  • Pursuing V2 launch effort:
    • implementing audits finding patches
    • finish system test & fix what’s needing a fix
    • depending on audit’s timeline and potential (unforeseen) delay, deployment of V2 🥳
  • Post-V2 launch:
    • Insure new project contract support → hopefully, there will be a need for custom solutions (custom terminal, “mint a NFT when paying”, etc) - fun things
    • Insure support for our L2 think-thank and deploy accordingly
    • Insure support for the contract-side of the force, to the dao and to the end-users

Find other spots where our community might have an unmet need and DAOify them.

Continuously find situational gif-gems & shit post accordingly.

What does success look like for someone taking on your role?

Sleepless nights and flawless code.

Under what criteria should the community reassess this payout?

Number of significant improvement to the Juicebox codebase or projects revolving around Juicebox codebase

Sponsors:

Community members who agree to act as spokespeople for this proposal can add themselves here.

Note: recurring payout recipients are required to participate in votes for future payout allocations. For payouts to non-EOAs, attach an address that will manage voting on the non-EOA address's behalf.

Votes

loading