Skip to main content



Funding parameters dictate how your project distributes funds. This section also dictates the behaviour of your project's funding cycle. A project's funding cycle determines how its time-locked rules operate. These details can be updated over time.


Automate funding cycles

Projects are expressed in terms of funding cycles.

  • Payouts happen once per funding cycle.
  • Some token incentives are calculated using funding cycles.
  • Most importantly, projects cannot be reconfigured in the middle of a funding cycle. Instead, changes are queued for the next funding cycle.
With automated funding cycles turned off, the project owner can reconfigure the project at any time, triggering a new funding cycle in the process. This provides flexibility for the project owner, but increases the community's percieved risk of rugpulls or other malicious behaviour.

When automated funding cycles are turned on, the project owner must choose a cycle duration. A shorter funding cycle provides more flexibility, but greater percieved risk. A longer funding cycle will do the opposite.

Automated funding cycles are particularly useful for projects with regular costs or payouts.


Payouts dictate how funds leave a treasury.

  • Amounts payouts are specific ETH or dollar amounts.
  • Percentages payouts are percentages of the entire treasury.
Payouts to Ethereum addresses invoke a 2.5% fee, which is routed to the Juicebox DAO treasury. These fees issue JBX tokens, granting projects partial ownership of the ecosystem. Payouts to other Juicebox projects do not invoke fees.

Funds not needed for a project's payouts are considered overflow. Community members can redeem their tokens for a portion of overflow funds, if enabled by the project owner. Overflow also serves as a project's runway. Projects using percentages payouts do not have any overflow.


Funding cycle information on

A project with ETH payout amounts on