• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
JuiceboxDAOJuiceboxDAOby0x50e70c43a5DD812e2309eAcea61348041011b4BAgnance.eth

JBP-436 - Update Reserved Allocation (September 2023)

Voting ended over 2 years agoSucceeded

Synopsis

Update the reserved list to include active JuiceboxDAO contributors. For organizations that work with JuiceboxDAO, send reserved tokens to their multisigs instead of individuals.

Motivation

  1. Sending reserved JBX to multisigs instead of individuals allows those organizations to use their JBX more creatively – to distribute as an added incentive, to build a stockpile, to vote collectively, or to do something else.
  2. Allocating reserved issuance to align incentives with active contributors will become even more important as the buyback delegate is implemented, which may significantly increase reserved issuance.
  3. Simplifying this list makes it easier to verify relevant multisig transactions.

Risks

Sending JBX to multisigs gives these organizations more to manage, even if minor. This distribution is only a loose approximation.

Specification

Update reserved JBX distributions like so:

Recipient Percentage
dao.jbx.eth 32%
Peel (6) 24%
Nance (2.5) 10%
Juicecast (2) 8%
WAGMI Studios (1.5) 6%
drgorilla.eth 4%
filipv.eth 4%
breadfruit.eth 4%
jb.0xba5ed.eth 4%
zhape.eth 4%

Rationale

Since there are now fewer recipients, I've slightly increased the allocation to dao.jbx.eth (from 30% -> 32%).

The list was updated to only include current contributors, with 4% per individual. Organization allocations were calculated based on the following list:

Org Members
Peel 6: TJL, peri, aeolian, Strath, wraeth, johnnyd
Nance 2.5: jigglyjams, twodam, Zeugh (part-time)
Juicecast 2: matthewbrooks, brileigh
WAGMI Studios 1.5: Sage, mieos (part-time)

Timeline

Implement in the cycle following this proposal's approval.

Off-Chain Vote

For
127.13M JBX100%
Against
0 JBX0%
Abstain
0 JBX0%
Download mobile app to vote

Discussion

JuiceboxDAOJBP-436 - Update Reserved Allocation (September 2023)

Timeline

Sep 12, 2023Proposal created
Sep 12, 2023Proposal vote started
Sep 16, 2023Proposal vote ended
Feb 25, 2026Proposal updated