Learn

How a revnet works

Understand what happens to your money, what a revnet token lets you do, and which terms are fixed at launch. Start with the basics, check a specific question, or prepare your first transaction. No wallet or coding knowledge is needed to learn.

Revnets are built on Juicebox. The Juicebox guide explains the protocol every revnet runs on.

Learn with an AI assistant

Give your assistant the Juicebox V6 skills for contract addresses, interfaces, and economics. Ask it to cite the current contracts so you can check its answers.

Relevant skills: revnet-economics, revnet-modeler, jb-revloans.

The basics

Start with what you want to do

A revnet is a revenue network: payments can fund a shared balance and give people tokens connected to it. You can explore the terms without connecting a wallet.

  • Understand a revnet: Read the basics, then open a revnet's Terms tab for its full stage schedule and token allocations.
  • Buy or use tokens: Compare the amount you receive after splits and fees, the selected chain, and the current cash out quote before signing. A token is not automatically company equity or a right to a product.
  • Launch your own: Use the Build guide to choose the model and prepare a draft. The create page does not require coding; launch terms need careful review because they cannot be edited later.

Explore revnets without a walletPrepare your first transactionLaunch a revnet without codeLook up an unfamiliar term

Back to contents

What a revnet is

A revnet is a Juicebox project owned by the REVOwner contract. Its launch configuration commits to a schedule for issuing tokens, allocating a share to contributors, and letting holders cash out or borrow against their tokens.

Customers and supporters pay the revnet. A payment can issue new tokens or buy existing ones through a market pool. Funds used for new issuance enter the revnet's balance; funds used for a market purchase pay the pool. The payer's token amount depends on the route and the stage's split share.

The operator cannot rewrite the committed stage schedule or take a discretionary payout from the balance. Some settings remain adjustable, including split recipients and market routing. Those powers and the contracts' dependencies still matter when deciding whether to participate.

Revnets are for open source projects, protocols, and any group that wants to share revenue with its contributors and customers without asking anyone to trust a treasury manager.

Juicebox project vs revnet
Juicebox projectRevnet
An owner can keep rule-changing powers, subject to the project's configurationREVOwner enforces the stage schedule committed at launch
Can budget payouts to a teamFunds leave through configured token, loan, market, shop, and bridge flows
Good for teams, DAOs, fundsGood for tokens, protocols, open businesses
Choose a revnet when committed token economics fit the project. Choose a configurable Juicebox project when a team needs a spending budget or the ability to change its economic rules.

Explore live revnetsDecide whether a revnet fits your product

Back to contents

How money flows

Start with payments, cash outs, and loans. A market route or shop purchase can add another step, so always check where a payment actually goes.

For a single-chain revnet with no loans, balance divided by total token supply is a useful starting point. With loans, the contracts also account for outstanding borrowed amounts and the collateral that can be restored. Some revnets include remote-chain accounting too. A backing estimate is not the amount available to withdraw right now.

New issuance changes both balance and supply; backing per token can rise or fall depending on the issuance rate. Auto issuance adds supply without a payment. Cash out taxes retain value for remaining holders, while loans move funds out until repayment or expiry changes the accounting.

Contributors receive the split share in tokens. To obtain ETH, USDC, or another asset, they must cash out, borrow, or find a buyer, subject to the same terms as other holders. There is no discretionary team payout budget.

The loop

A payment can mint tokens and fund the balance, or buy tokens from a market pool. The stage allocates a share of new issuance to split recipients. A treasury cash out burns tokens for funds, while a loan burns collateral that can be restored through repayment.

Back to contents

The three prices

Issuance, cash out, and market prices answer different questions. Compare live quotes for your amount and chain; a chart is only a reference.

Charts may call issuance a ceiling and cash out a floor. Those names describe incentives, not guaranteed market limits. Liquidity, transaction costs, launch locks, bridge delays, and changing state can keep a price outside those reference values. Use the transaction quote for the amount you intend to trade.

  • Issuance price: what a new token costs at the current stage's issuance rate. Your effective price also reflects the split share. Issuance may be zero, so new tokens are not always available at a finite price.
  • Cash out price: what a treasury cash out can return for a specified token amount. It depends on the tax, supply, backing, fees, and funds available on the selected chain. It changes with transaction size.
  • Market price: what a liquidity pool offers for a trade. Its displayed price can differ from the amount your trade achieves because trading moves the price and incurs fees.
Compare routes, then compare the final quote

When a market asks more than issuance, a buyer may prefer to mint. When a market pays less than cash out, a seller may prefer to cash out. These incentives do not enforce a guaranteed market floor or ceiling: fees, liquidity, delays, and price changes can prevent a profitable trade.

Back to contents

Stages

A revnet's rules change over time, but only along a schedule of stages that was written at launch. The current stage decides what happens now; the full list shows what happens later.

Each stage sets when it can start, how many tokens a payment issues, how fast that rate falls, what share of new tokens goes to splits, the cash out tax, and any auto issuance allocations that become claimable after the stage starts.

  • Start: the earliest timestamp the stage can take over; check the effective start shown in Terms.
  • Issuance: tokens issued per unit of the base currency paid.
  • Issuance cut: a percentage the rate drops by on a fixed cadence, so earlier payers get more tokens for the same money.
  • Split share: the percent of every issuance that goes to the stage's split recipients rather than the payer.
  • Cash out tax: a parameter in the cash out curve, not a flat percentage deducted from every withdrawal.
  • Auto issuance: a fixed token allocation for named recipients, claimable after the stage starts without a payment. A transaction must claim it; it does not mint merely because time passes.
Example schedule

Illustrative schedule: stage one starts on day zero, issues 1,000 tokens per ETH before a 30% split, cuts issuance by 10% every 30 days, and has a 20% cash out tax. Stage two starts on day 365, inherits the rate, cuts it by 5% every 90 days, and uses a 10% split and 50% tax. Stage three starts on day 1,825 with no new issuance and a 50% tax. Actual stage transitions follow their on-chain ruleset timing.

Always read the whole schedule, not just today's rate. A generous first stage followed by a harsh second one is a real deal that should be judged as a whole.
Back to contents

Going deeper

Cash outs and the cash out tax

A treasury cash out burns tokens for funds. A positive cash out tax reduces the proportional amount returned when less than the full effective supply is cashed out, leaving value behind for remaining holders.

In the simplified example below, a 0% tax returns 10% of the balance for 10% of the supply. A 20% tax parameter returns 8.2 ETH, not 8 ETH: the formula also accounts for the share being cashed out. This example excludes fees, loans, remote balances, and market routing.

  • Size changes the effective tax: for the same starting balance and supply, a larger share receives more per token. Splitting a withdrawal into smaller transactions does not create a discount; each transaction changes the state and adds gas costs.
  • The tax is set per stage: so a revnet can start liquid and become stickier as it matures, or the reverse.
  • Fees: a standard taxed treasury cash out includes a 2.5% Juicebox protocol fee and a Revnet fee calculated from 2.5% of the token count. These use different bases and are separate from the cash out tax. Even a 0% tax can incur a protocol fee on funds previously received through fee-free payouts. Check the net quote; a market route or fee exemption can change the result.
Worked example before fees

With a balance of 100 ETH and a cash out of 10% of total supply, a 0% tax returns 10 ETH, 20% returns 8.2 ETH, 50% returns 5.5 ETH, and 80% returns 2.8 ETH, before fees. Multiply balance by the share, then by one minus the tax plus the tax times the share. Use 0.1 for a 10% share and 0.2 for a 20% tax.

Cash out formula in the contractsHow an app quotes cash outs

Back to contents

Splits and auto issuance

A stage can route a fixed share of every issuance to contributors, partners, or other revnets. That share is how a revnet pays the people building it.

The split share is a percentage of each issuance, fixed per stage. If the share is 30%, a payment that issues 1,000 tokens sends 700 to the payer and 300 to the split recipients. The recipients get tokens, never the balance itself.

The operator can redirect split recipients while respecting allocations that are still locked, but cannot raise the committed split percentage. Auto issuance is a separate stated allocation, claimable for its named recipient after its stage starts. Anyone can trigger that claim; the tokens still go to the configured beneficiary.

Both mechanisms affect who holds the supply. Payment issuance adds funds as well as tokens; auto issuance adds tokens without funds. On a multichain revnet the split share is the same on every chain, but recipients can differ. Include unclaimed allocations when considering future dilution.
Back to contents

Markets and buybacks

A liquidity pool holds assets that people can trade. A revnet's buyback hook can use a configured pool when it offers a better rate than new issuance, or combine a market purchase with issuance.

The buyback hook is a contract called during a payment. Funds spent in the pool buy existing tokens from liquidity providers; they do not all enter the revnet's balance. The standard route applies the split share to the tokens obtained. Some integrations can opt out of splits on the purchased portion; newly minted tokens still follow the stage's split.

Buying directly from a pool skips the revnet's payment path and split share, but it is not always the best deal. Compare the tokens you receive after all costs, including price movement caused by your trade. A shop purchase may require the payment path to receive the item.

Cash outs can also use a configured pool when selling tokens there produces a better result. In that case the market supplies the funds; the treasury-only formula is not the complete quote. The confirmation should identify the route and enforce the minimum amount you accept.

A pool may be absent or have too little liquidity for your amount. A displayed market price is not a promise of an executable trade. Check the live quote and its minimum output before signing.
Back to contents

Loans

A loan gives a holder funds now and a way to recover token collateral by repaying. The collateral tokens are burned while the loan is open, so they cannot also be spent or cashed out.

The amount you can borrow uses the current cash out tax and the revnet's effective backing, then is capped by funds available on the selected chain. A loan does not bypass a high cash out tax. Compare net proceeds, repayment cost, and the token rights you want to recover.

A standard new loan deducts a 2.5% Juicebox protocol fee, a 1% REV fee where its fee payment is available, and your chosen prepaid source fee of 2.5% to 50%. The source fee returns to the lending revnet. You receive less than the recorded principal, but repayment is based on that principal, plus any additional time-based fee.

The prepaid fee sets the window with no additional source fee: 2.5% covers 182.5 days; 50% covers the full 3,650 days. After that window, the additional source fee increases until expiry. Read the exact repayment quote and expiry timestamp; waiting past expiry permanently loses the right to recover collateral.

Outstanding loan principal counts in backing and burned collateral counts in effective supply while the claim exists. After expiry, anyone can liquidate the loan to remove both. Expiry does not send new money into the balance or guarantee a higher value per remaining token. Transferring the loan NFT transfers control of the loan, including the right to recover its collateral.

Loan lifecycle

Borrowing burns collateral, sends funds after fees, and creates a transferable loan NFT. Repayment before expiry pays the required principal and any additional source fee to restore collateral. After 3,650 days the loan expires; a permissionless liquidation removes both its outstanding debt and collateral from accounting. No price-triggered margin call is part of this loan lifecycle.

Loan rules and fee calculationIntegrate loan quotes and repayment

Back to contents

Shops

A revnet can sell items through a shop. A qualifying payment can mint an item NFT alongside revnet tokens, subject to the item's price, supply, and payment rules.

Items are organised into categories and can have supply limits, prices, token splits, discounts, and transfer rules. Some shop configurations route part of an item payment to another recipient, so check the purchase breakdown. The operator may keep powers to change shop settings or mint items.

An NFT is an on-chain record. Any promised physical item, service, access, delivery, or refund depends on the seller's stated terms; the token itself does not fulfil that promise. Read the item description and check the seller before buying.

Back to contents

Under the hood

One revnet, many chains

A revnet can run on several Ethereum chains at once. Each chain has its own balance and token supply, running the same stage schedule in sync.

Payments and cash outs execute on the selected chain once the transaction is included. Ordinary cash out and loan accounting may include remote balances and supply, depending on the launch configuration, but actual withdrawals are limited by local funds.

A cross-chain move uses bridge contracts called suckers. They cash tokens out using the source chain's local backing without the normal cash out tax, move the corresponding funds, and allow tokens to be claimed on the destination. This is a separate registered bridge path, not a tax exemption on a holder's later cash out.

Cross-chain moves are asynchronous. A balance shown for the whole group can include value that is queued, in transit, or waiting to be claimed on the other side.

Keep the source transaction and destination chain handy until the claim completes. A successful source transaction does not mean destination tokens are ready. Bridge messages, fees, and claim transactions can take additional time.

Back to contents

The operator

REVOwner is the on-chain project owner. An optional human or contract operator has limited permissions; it cannot rewrite the stage schedule, but its routing, allocation, and shop decisions can still affect users.

  • Can: update the name, description, and token metadata; redirect the precommitted split share; choose the buyback pool, its TWAP window, and the router terminal; manage sucker safety; and extend the revnet to new chains if the deployment allowed it. A revnet launched with a shop also lets the operator add items, set discounts, update item metadata, and mint.
  • Cannot: change issuance, cuts, cash out taxes, split percentages, or stage timing. Cannot withdraw the balance.
  • Can hand over: the role to another address, or to nobody.
The zero address is the contract's explicit no-operator setting, and relinquishing to it is permanent. This site's create flow uses a dead address intended to be inaccessible when the operator is off. Inspect the actual address and permissions on every chain; do not infer control from an address label alone.
Back to contents

Built on Juicebox

A V6 revnet uses Juicebox's payment and token contracts with REVOwner as its project owner. It selects a constrained set of Juicebox features and removes the ordinary owner's ability to change the committed economic rules.

Juicebox supplies payments, tokens, rulesets, splits, cash outs, hooks, and cross-chain suckers. The Revnet contracts add the stage schedule, the cash out and loan economics, and the operator's limited permissions on top.

If you want to understand rulesets, terminals, hooks, and fees at the protocol level, the Juicebox guide covers them in the same plain style.

Learn JuiceboxRevnet V6 sourceJuicebox V6 source

Back to contents

What to check before you trust one

Revnets follow a known set of rules, but each revnet chooses its own numbers, recipients, chains, and operator. Read them.

The code and transaction records are inspectable. Fixed stages limit owner discretion, but they do not guarantee token value, revenue, liquidity, or fulfilment of a team's promises. Check contract dependencies, operator permissions, and bridge and pricing assumptions alongside the economic terms.

  • Stages: the full schedule, especially the stage after the one you are paying into.
  • Splits and auto issuance: who receives tokens without paying, and how much.
  • Chains: which chains it runs on and whether the numbers match across them.
  • Balance and supply: what backs a token today, and how much of the supply is in loans.
  • Operator: who it is and what they were granted.
  • Pool: whether there is one, how much it can trade at your amount, and how its net quote compares with issuance or a treasury cash out.
  • The transaction: that what your wallet is about to sign matches the call this site describes.

Audit the contracts and this siteWebsite source

Back to contents

Try it

Your first transaction

Browse first, choose an amount, and connect a wallet when you are ready to act. Wallets hold your tokens and approve transactions on a particular chain.

  • 1. Choose the revnet: Open Discover, then check the project's identity, Terms, token allocations, accepted assets, and operator. An attractive name or chart is not enough to identify the contract you mean to use.
  • 2. Choose the chain and amount: Use an asset the payment flow accepts on that chain. Leave enough of the chain's gas token for transaction fees. Bridging from another chain takes a separate flow and can require another claim.
  • 3. Review what you receive: Check the beneficiary address, split share, route, fees, and minimum token output. For a shop item, also check the NFT and seller's fulfilment terms. An ERC-20 approval authorizes spending; it may be followed by a separate payment transaction.
  • 4. Wait for confirmation: A submitted transaction is pending until the chain confirms it. A Safe multisig proposal still needs execution. Keep the transaction link and check your holdings on the same chain if tokens are not immediately visible.
  • 5. Plan your next action: Use the project's holder controls to quote cash out or borrowing. A zero quote can mean no available funds, a launch lock, or an unsupported route. Refresh the quote and check Terms before trying again; do not lower a minimum just to make an unexplained failure pass.

Find a revnet to exploreReview the terms before signingSave a launch draft before deploying

Back to contents

Reference

Words used in this guide

You do not need to know Solidity or DeFi terminology to read a revnet's terms.

  • Balance / treasury: assets held for a revnet in its payment contracts. Available local funds can differ from an aggregate backing estimate.
  • Token / supply: the revnet's units of participation, and the total number accounted for. Loan collateral and pending allocations matter when interpreting supply.
  • Credits / ERC-20: two ways the protocol records a token balance. Credits can be used within Juicebox; claiming turns them into ERC-20 tokens that compatible wallets and markets can use. Claiming does not create an extra economic allocation.
  • Stage / ruleset: a scheduled set of token and cash out terms. Juicebox calls the underlying configuration a ruleset.
  • Issuance / mint / burn: creating tokens, creating tokens on-chain, and destroying tokens. Loan collateral can be minted back only through the loan's permitted recovery flows.
  • Split share: the portion of issuance allocated to named recipients instead of the payer.
  • Cash out tax: the curve parameter that keeps part of a proportional treasury withdrawal for remaining holders. It is separate from a protocol fee or a government tax.
  • Pool / liquidity / slippage: assets available for trading, how much can be traded, and the difference between an expected result and execution. A minimum output limits how much deterioration you accept.
  • Collateral / loan NFT: tokens committed to a loan, and the transferable record controlling that loan and recovery of its collateral.
  • Terminal / hook / sucker: a payment-and-withdrawal contract, a contract called to customize an operation, and a bridge contract that moves a revnet's tokens and backing between chains.
  • Gas / approval: the network fee for a transaction, and permission for a contract to spend a token. Neither is the same as paying the revnet.
  • TWAP: time-weighted average price: a pool price averaged over a window, used in routing. It is a reference, not a guaranteed execution price.
Back to contents