Juicebox

• Name: Juicebox
• URL: https://juicebox.money/
• Category: programmable treasury protocol / tokenized fundraising engine / ruleset-based capital-formation infrastructure
• Summary: Juicebox is best understood not as a crowdfunding frontend, but as a programmable treasury and tokenized capital-formation system where each project can pre-commit rules for contribution intake, token issuance, treasury payouts, redemption rights, and future policy changes. Its reusable mechanism is the split between project ownership, scheduled rulesets, payout and reserved-token splits, and cash-out rights against treasury surplus. That combination makes Juicebox a useful comparison class for crowdfunding protocols, DAO treasury managers, memecoin launch systems, and public-goods funding tools: it turns a treasury into a configurable issuance-and-redemption machine rather than a static multisig wallet with ad hoc governance layered on top.
• What it does:
  • Lets anyone deploy a project represented by an admin NFT that controls future configuration
  • Allows projects to queue any number of future rulesets covering payout limits, surplus allowances, token issuance weight, reserved-token allocation, cash-out tax, and approval hooks
  • Issues project-specific tokens or credits when payments are received, with optional later ERC-20 issuance
  • Supports payout splits and reserved-token splits so incoming capital and newly minted tokens can be routed automatically to teams, communities, other Juicebox projects, or hook contracts
  • Holds treasury surplus that token holders may partially reclaim by cashing out, making token exit rights part of treasury design rather than an afterthought
  • Supports omnichain operation and custom hooks that can extend payment, payout, redemption, and approval logic
• Key claims:
  • The current developer docs explicitly describe Juicebox as a payment processor and capital-formation engine for tokenized fundraises, revenues, incentives, and financial operations, which is broader and more structurally important than a simple donation app
  • The project-NFT model matters because administrative power sits with whoever controls the project NFT; this is the constitutional owner of future rulesets, not merely a UI account
  • Rulesets are the key control surface. The docs emphasize that active rulesets cannot be changed mid-flight but future rulesets can always be queued, which makes timing, approval hooks, and community monitoring central governance questions
  • Juicebox’s payout limit / surplus / cash-out structure means treasury rights are split between operator spending discretion and token-holder redemption rights. That is a meaningful mechanism distinction from systems where contributors simply donate into an owner-controlled wallet
  • Splits add another governance surface: a project can pre-program who receives funds and reserved tokens, and can even route them to other projects or hook contracts, so treasury policy becomes composable infrastructure
  • The docs explicitly present custom hooks as first-class, meaning teams can graft governance, NFT rewards, buybacks, or approval criteria onto the base treasury engine without changing the core architecture
  • The repo and interface materials make clear that Juicebox is not only contracts; it is a live protocol plus frontend stack used to launch and manage projects, which increases the importance of interface defaults and contributor-controlled documentation as practical governance layers
• Whitepaper: No canonical standalone Juicebox whitepaper surfaced in this pass. The strongest primary materials were the official docs plus the official contracts and interface repositories; see ../whitepapers/juicebox-primary-sources-2026-05-10.md.
• Sources:
  • https://juicebox.money/
  • https://docs.juicebox.money/
  • https://docs.juicebox.money/dev/
  • https://docs.juicebox.money/dev/v5/learn/overview/
  • https://docs.juicebox.money/dev/v5/learn/glossary/ruleset/
  • https://docs.juicebox.money/dev/v5/learn/glossary/splits/
  • https://github.com/jbx-protocol/juice-docs
  • https://github.com/jbx-protocol/juice-contracts-v3
  • https://raw.githubusercontent.com/jbx-protocol/juice-contracts-v3/master/README.md
  • https://raw.githubusercontent.com/jbx-protocol/juice-interface/main/README.md

Internal linkages

• Best allocation-policy contrast: allo-protocol.

• Best shared-ownership and exit-rights contrast: party-protocol.

• Best constitutional-treasury lineage read: molochdao.

• Last reviewed: 2026-05-27 UTC