Approved

JBP-315: Install V3 Split allocator in JB DAO v2 treasury, set allocator as feeless

Author

Anon

Cycle

38

Requesting

9,999,900 USD

loading

Proposed Transactions

Payout action loading...

Status: Draft

Author: jango.eth
Date: (2022-12-16)

Synopsis

Set the JuiceboxDAO v2 treasury distribution limit to infinite, and route all accumulated funds to the jbdao v3 treasury without incurring fees when doing so.

Motivation

JuiceboxDAO now has funds in its v3 treasury in order to service ongoing funding cycle commitments. All token redemptions are also moving to the v3 treasury. Thus, any funds accumuated on v2 should be able to move to v3 without further questions.

Specification

  1. Juicebox DAO multisig should call setFeelessAddress on the v2 JBETHPaymentTerminal (https://github.com/jbx-protocol/juice-contracts-v2/blob/2ef95921d5729e801d131939a7ae1bf6ba80851f/contracts/abstract/JBPayoutRedemptionPaymentTerminal.sol#L661) (0x7Ae63FBa045Fec7CaE1a75cF7Aa14183483b8397), adding the v3 allocator (0x6aaf7afef64c6852ee507876f9d25f92bd9a1ae7) as feeless.
  2. Set the Juicebox DAO v2 treasury distribution limit to the max value. Route 100% of it to the v2 => v3 allocator noted above.

Rationale

The allocator was built with this single purpose in mind.

Risks

There is smart contract risk when utilizing additional components. There's also governance risk that there might still be commitments from the v2 treasury that don't get upgraded to v3 in time.

Timeline

The next Funding cycle.

Votes

loading