JBP-83 - Add dhyon to recurring payout

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:

dhyon

Proposal date:

January 14, 2022

Summary:

Hi I'm dhyon and I've been contributing as a Juicebox protocol dev since FC #10.

You can find me tucked away in the “V2 Testing” dev thread where I’ve been focused on the Juicebox V2 smart contracts.

Risks:

I could stop performing.

Payout recipient:

dhyon.eth

Payout amount:

$3000 in ETH

How have you contributed to the DAO?

V2 protocol efforts - most of the work has been diving deep into the new solidity contracts, identifying edge cases, simulating these cases in the form of unit tests, and then making the necessary adjustments to the contract code as needed. We're also moving in the system testing phase and prepping the contracts for an official audit on Jan 24.

It's been fun and educational working alongside @Jango , @Exekias , @Dr Gorilla and others on this endeavor.

• JBToken tests https://github.com/jbx-protocol/juice-contracts-v2/pull/29
• Finish off JBTokenStore tests https://github.com/jbx-protocol/juice-contracts-v2/pull/32
• Debug, fix, and write a test utility for JBFundingCycleMetadataResolver https://github.com/jbx-protocol/juice-contracts-v2/pull/38
• JBFundingCycleMetadataResolver tests https://github.com/jbx-protocol/juice-contracts-v2/pull/52
• JBETHPaymentTerminalStore tests https://github.com/jbx-protocol/juice-contracts-v2/pull/43
• Currently helping out with JBETHPaymentTerminal tests https://github.com/jbx-protocol/juice-contracts-v2/pull/49
• Discussing and scheming our potential new mechanism design

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

In the short term, V2 stuff.

In the long term, areas of interest that I'd like to build out for Juicebox are extensions for the V2 contracts, the vote-locking staking mechanism, and perhaps forking the protocol to other L1s and L2s.

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

Ships code, reviews code, consistent team player, communicates clearly and effectively, eager to learn, offers ideas/suggestions for design and implementation, and active in the community.

Under what criteria should the community reassess this payout?

There are three scenarios where my payout may need to be reassessed:

1. My personal circumstances change such that I am unable to contribute at an acceptable level. In this case, my payout should be reduced or removed.
2. My responsibility grows within the DAO, and more of my time is required. In this case, I would propose an increase to my payout.
3. I become available to the DAO full-time. In this case, I would propose an increase to my payout.

Sponsors:

@Jango @Exekias @Dr Gorilla

---

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.

IPFS https://gateway.pinata.cloud/ipfs/QmWSVxQzDd59Chhg3w7MBwEFQALZdHPH25kCtHvcPS1kE5?preview=1

Discord Discussion https://discord.com/channels/775859454780244028/873248745771372584/931682877354176592

Notion https://www.notion.so/juicebox/Add-dhyon-to-recurring-payout-37112314834949659447dc79daba5b2e