Cancelled

JBP-417: Renew & Reduce Recurring Payment Proposal for Viraz

Cycle

55

Requesting

21,000 USD + 1,000,000 TOKEN

loading

Proposed Transactions

Payout action loading...
Transfer1,000,000TOKENto0x2dda...5a51

Synopsis

  • Keep 0xviraz.eth in JuiceboxDAO recurring payouts, with a reduction in compensation, for another 7 cycles.

Motivation

Viraz has been contributing part-time on the protocol side of things since last year and would like to continue the same and keep contributing towards the protocol side of things. Please find details of his previous proposals here

 

Since his last recurring proposal ended, here is the work Viraz has done :

  • Majorly worked on getting buyback delegate close to the finish line and helped Dr G, worked on adding/updating, fixing issues with tests, and reviewing pr's (Commits)
  • added a small update to reduce contract size with the new terminal update in v3 and reviewed pr 
  • PR reviews for new version for 721 delegate, metadata lib
  • Integrate metadata lib in 721 delegate (PR)

Going forward viraz is planning to help on the protocol side of things for any new features (a list is mentioned here https://github.com/orgs/jbx-protocol/projects/5 but not up to date), if any bugs happened and help to patch those and testing the fixes & since at this point the DAO is getting actively involved in hackathons so as one of the early protocol contributors happy to help with any requirements that arise to help new devs getting onboarded etc

Specification

  • Renew 0xviraz.eth payout of 3000$/cycle for 7 cycles
  • Execute a one-time transfer of 1m $JBX from the multisig balance to 0xviraz.eth

If JBP-418 is approved, pay 0xviraz.eth $4500(150% of 3000 $) for 5 cycles instead.

Rationale

  • Viraz has been a consistent contributor at the JB DAO providing a positive impact and helping in wherever required and as experienced protocol dev he want's to continue the same
  • Based on the current needs of the DAO he has reduced his payout as mentioned in this proposal
  • Having a $JBX allocation will help him to participate in voting more actively, this is the first time he has mentioned a jbx transfer in his proposal and in case the DAO is not aligned on this he can reduce/remove this one-time transfer

Risks

Viraz could go AWOL

Unable to deliver according to the timelines or produce low-quality buggy code

Timeline

Start next cycle