Learn Juicebox.

1. What is Juicebox?#

Juicebox lets people fund a project together and receive incentives in return, under rules for the money that anyone can read. Those rules run as public programs on a blockchain, called smart contracts.

Incentives are tokens. Depending on the rules, holders can return them for a share of the project’s balance sheet. This is a cash out.

A project’s page shows what your payment supports, what you receive, and who can change the rules.

• Explore projects
• What to check before paying
• Launch a project without code
• Look up a word

Back to contents ↑

2. How money flows#

People pay a project and receive tokens. The project sends money to its chosen recipients through payouts. Holders cash out when the rules allow.

  1. Someone PAYS into a project
     └─▶ They receive project tokens

  2. The project DISTRIBUTES payouts
     └─▶ To team members, partners, other projects

  3. Token holders can CASH OUT
     └─▶ Return tokens for a share of the balance sheet

The owner sets how much can be paid out, how many tokens a payment creates, and how cash outs work. Together these terms are a ruleset.

Pay gives you tokens or items. Add to balance sends money without creating tokens.

Back to contents ↑

3. Projects and owners#

A project has a balance sheet, terms, and an owner. Ownership is a unique token, an NFT: whoever holds it owns the project.

The current ruleset decides what the owner can do: schedule new terms, change recipients, create tokens, or add extras. Upcoming terms show what can change next.

The owner can give another account permission for specific tasks, like sending payouts, without handing over ownership. Some tasks, like sending scheduled payouts, are open to anyone. When ownership changes hands, permissions the previous owner gave stop working.

Projects accept ETH and other currencies, including stablecoins. A project can price its terms in USD while accepting ETH; it uses a price feed to convert.

  ┌───────────────────────────────────────────────┐
  │  YOUR PROJECT                                  │
  │                                                │
  │  accepts payments ──▶ issues tokens            │
  │  holds funds      ──▶ distributes payouts      │
  │  sets aside funds ──▶ allows cash outs         │
  │                                                │
  │  public contracts enforce the rules            │
  └───────────────────────────────────────────────┘

• How terms change
• Grant a specific permission

Back to contents ↑

4. Before your first payment#

Start with a project you recognize.

1. 1Confirm the project, chain, and currency. A project on several chains keeps a separate balance on each.
2. 2Open the Rulesets tab, called Terms on some projects. Check how many tokens you’ll receive, where the money goes, when you can cash out, and what can change.
3. 3Read the project description and any item terms, and check who runs the project.
4. 4Enter an amount and review the result. Keep some ETH for gas. Paying with a token like USDC needs an approval first.
5. 5Approve in your wallet and wait for confirmation. If it stays pending, check its status before trying again.

• Find a project
• How cash outs work
• How payment tokens are shared
• Which terms can change

Back to contents ↑

5. Tokens and reserved tokens#

Creating new tokens is called issuance. At 500 tokens per ETH, a 2 ETH payment creates 1,000 tokens. A rate of zero creates none.

A project can set aside part of every new batch for chosen recipients. These are its reserved tokens. With 20% reserved, a payment that creates 1,000 tokens gives 800 to the payer and reserves 200, which are sent to recipients in a later transaction. Revnets call reserved tokens splits.

You can hold tokens as credits inside Juicebox, or as standard ERC-20 tokens that wallets and markets use. Both count toward your balance; claiming turns credits into ERC-20 tokens one for one.

  payment: 2 ETH
  rate:    500 tokens per ETH
  reserved: 20%

  tokens created = 1,000
       │
  ┌────┴─────────────────┐
  │                      │
  ▼                      ▼
  800 tokens          200 tokens
  (to payer)          (reserved for recipients)

• Cash outs and a worked example

Back to contents ↑

6. Rulesets#

A project’s payment, payout, token, and cash out terms are grouped into a ruleset. The Rulesets tab shows the current terms and what comes next.

A ruleset can repeat in cycles, such as every 30 days, and can create fewer tokens per payment each cycle. A ruleset with no cycle lasts until the owner replaces it.

New terms often need notice or approval first, and a cycled ruleset changes only when a cycle ends. Scheduled terms take effect only when they start.

  schedule terms   notice/approval    cycle ends
       │              checks              │
       ▼                │                  ▼
   SCHEDULED ───▶ APPROVED ──────▶ ACTIVE ──repeats──▶ ACTIVE...
       │                                   ▲
       └── if no notice needed ────────────┘

• Choose each ruleset setting

Back to contents ↑

7. Payouts and splits#

A project can send money from its balance sheet to chosen recipients. These are payouts, and each recipient’s share is a split. A split can go to a wallet, another project, or a contract that does something with it. Anyone can send scheduled payouts, unless the project limits that to the owner.

A payout limit caps how much can be paid out each cycle, per currency and per chain. Everything above the limit stays on the balance sheet and backs cash outs. The owner can also have an allowance to withdraw beyond payouts.

A split can be locked until a date. Until then the owner can’t remove it, but can extend the lock or add new splits.

  project balance sheet
       │
  ┌────┴──────────────────────┐
  │                           │
  ▼                           ▼
  scheduled payouts        the rest
  (sent to splits)         (backs cash outs)

• Send payouts and manage funds

Back to contents ↑

8. Cash outs#

When you cash out, you return tokens to the project and receive a share of its balance sheet, minus anything already scheduled for payouts. The returned tokens are burned.

The cash out tax leaves part of your share behind for remaining holders. At 0% you get your proportional share; at 100% cash outs are off. In between, bigger cash outs lose less of their share, because the formula also weighs how much of the supply you return.

  balance 100 ETH, you hold 10% of the supply

  tax  0%  → cash out returns 10.0 ETH
  tax 20%  → cash out returns  8.2 ETH   (1.8 ETH stays)
  tax 50%  → cash out returns  5.5 ETH   (4.5 ETH stays)
  tax 80%  → cash out returns  2.8 ETH   (7.2 ETH stays)

  returned = balance × share × ((1 − tax) + tax × share)

1. 1Open Cash out on the chain where you hold the tokens.
2. 2Enter an amount, and check what you’ll receive and the minimum you’ll accept.
3. 3Approve in your wallet and wait for confirmation.

• Fees on cash outs
• Integrate a cash out

Back to contents ↑

9. Fees#

Juicebox charges 2.5% when money leaves a project: payouts, allowance withdrawals, and cash outs with a tax above 0%. The fee is a payment into the Juicebox Protocol’s own project (JBP6), so it comes back as JBP6 tokens: to the owner for payouts, to the chosen recipient for withdrawals, and to you for cash outs.

Paying a project has no fee. Launching one costs a creation fee of up to 0.001 ETH per chain. A 100 ETH payout sends 2.5 ETH to JBP6 and 97.5 ETH to recipients, and the owner receives JBP6 tokens.

• Fee details for builders

Back to contents ↑

10. Shops#

A project can sell items through a shop. Buying one gives you the item, recorded as an NFT, plus any tokens the project’s rules create.

Items with the same price, supply, and terms form a tier. Some tiers reserve copies for chosen recipients or carry voting power. Owners can add or remove items and mint reserved copies when the shop’s rules allow. Anything physical depends on the seller, so read the item description.

Croptop lets people post content to a project’s shop for supporters to collect. The project sets who can post, the minimum price, and how many copies can be collected. Posting adds 5% of the item price, paid to the Croptop Publishing Network project (CPN), and the poster chooses who receives its CPN tokens.

• Set up a shop

Back to contents ↑

11. Markets and buybacks#

People can deposit tokens and money into a shared market, called a liquidity pool, for others to trade against. When you pay a project that has one, it checks the pool and buys existing tokens for you when they’re cheaper than new ones. Cash outs work in reverse: if selling to the pool pays more, the cash out sells there, and the review shows the route.

A project can also accept currencies it doesn’t hold directly; the payment converts them first.

• Integrate the buyback
• Build your own extension

Back to contents ↑

12. Projects across chains#

A project can run on Ethereum, Optimism, Base, and Arbitrum at once. Each chain has its own project ID, balance, and tokens.

Moving tokens between chains takes three steps: send from one chain, wait for the bridge, then claim on the other. Your tokens carry their share of the balance with them. Keep the transaction link until you’ve claimed; a confirmed send doesn’t mean the tokens have arrived.

• Multichain integration details

Back to contents ↑

13. Revnets#

A revnet is a Juicebox project with its token schedule fixed at launch: tokenized incentives backed by a balance sheet. Each period in the schedule is a stage, and later stages can create fewer tokens per payment.

A revnet has no owner who can change its terms. An operator can manage details like its name, recipients, and shop, but can’t change the schedule or withdraw from the balance sheet.

Revnet holders can also borrow against their tokens. The tokens are burned while the loan is open and minted back when it’s repaid within 10 years. Revnets add their own fees on cash outs and loans.

  PROJECT                          REVNET
  owner can schedule new terms     schedule fixed at launch
  payouts to a team                contributors receive tokens
  cash outs if the rules allow     cash outs and loans

• Learn about revnets
• How loans work
• Revnet fees

Back to contents ↑

14. Reward distributors#

A project can set up a separate contract to share rewards with holders over time. This is a distributor. Rewards come from funds deposited into it; holding tokens doesn’t create them.

Each round records who qualifies at that moment, then unlocks their share gradually. Token holders must delegate their votes, even to themselves, to qualify; NFT holders qualify through eligible shop items. Claim unlocked rewards before the round expires.

  funds deposited into the distributor
     │
     ▼
  round starts → records who qualifies
     │
     ▼
  each participant’s share begins to unlock
     └─▶ share = your eligible weight / total eligible weight
     └─▶ rewards unlock gradually over time
     │
     ▼
  collect unlocked rewards as rounds pass

• Deploy and integrate a distributor

Back to contents ↑

15. Payment addresses and names#

A project can have its own address that turns any ETH sent to it into a payment, so anyone who can send ETH can fund it. Tokens go to the sender, or to a recipient the owner chose; the owner can also make it add to the balance without creating tokens. Send only ETH: other tokens sent directly to it don’t count as a payment.

A project can use an ENS name, like myproject.eth, instead of a number. The name’s owner adds a record pointing to the project, then registers the link. Apps check the record before showing the name.

  someone sends ETH to the payment address
     │
     ▼
  the address finds the project’s current payment contract
     │
     ├─ default mode
     │  └─▶ pays the project → tokens to the sender or chosen recipient
     │
     └─ "add to balance" mode
        └─▶ adds funds to the balance → no tokens created

  1. own an ENS name (e.g. "myproject.eth")
  2. add a "juicebox" text record: "1:42"  (chain:project)
  3. register the name onchain for your project
  4. apps verify the ENS record matches
  5. your project now shows as "myproject.eth"

• Deploy a payment address
• Set a project name

Back to contents ↑

16. Glossary and next steps#

Words you’ll see on project pages.

• Explore projects
• Create a project
• Build an app or extension
• Inspect source and audit prompts
• Learn about revnets

Back to contents ↑