Learn
How a revnet works
A revnet turns payments, token issuance, cash outs, loans, and markets into one public agreement that runs on a schedule and cannot be rewritten. Start at the top if you are new; jump to a section if you are checking one thing.
Revnets are built on Juicebox. The Juicebox guide explains the protocol every revnet runs on.
Reading with an agent? Give it the Juicebox V6 skills so it answers from the deployed addresses, ABIs, and economics rather than from memory. The revnet ones are revnet-economics, revnet-modeler and jb-revloans.
The basics
What a revnet is
A revnet is a Juicebox project whose owner is a contract instead of a person. That contract holds the project to one narrow intent, written down at launch: take payments, issue tokens, hold the balance, honour cash outs and loans, and never change the terms.
Customers and supporters pay the revnet. Every payment issues the revnet's token to the payer, and the money stays in the revnet's balance, where it backs those tokens. Token holders can cash out for a share of the balance, borrow against their tokens, or sell them on an open market.
That is the whole deal. Because the owner is a contract, nobody can pause the revnet, raise prices in secret, or take the money out. It has a schedule, and the schedule runs.
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 project
Revnet
Owned by a person or multisig, who can change the rules
Owned by a contract that never changes the economics
Owner can pay funds out
Balance only leaves through cash outs and loans
Good for teams, DAOs, funds
Good for tokens, protocols, open businesses
Explore live revnetsDecide whether a revnet fits your product
How money flows
There are only two core actions: pay and cash out. Everything else is a rule about how those two behave.
Because payments never leave the balance except through cash outs, loans, and the fees on them, the backing per token can only be moved by the rules: new issuance dilutes it, cash out taxes and loan fees add to it.
Contributors get paid from the split share of newly issued tokens, so their upside is the same token everyone else holds. There is no payout budget for anyone to manage.
1. Someone PAYS the revnet
└─▶ they receive tokens at the current issuance rate
└─▶ a fixed share of new tokens goes to the revnet's splits
└─▶ the payment stays in the balance
2. Holders CASH OUT
└─▶ burn tokens, take a share of the balance
└─▶ the cash out tax decides how much stays for everyone else
3. Or holders BORROW against tokens instead of cashing out
backing per token = balance ÷ token supplyThe three prices
A revnet token always has an issuance price, a cash out price, and, once a pool exists, a market price. They answer different questions.
The price chart on every revnet page draws all three. Read the gap between them: a wide gap means the market has room to move, a narrow one means the revnet's own terms are doing most of the pricing.
- Issuance price: what one new token costs when you pay the revnet. Set by the current stage. Acts as a ceiling: nobody pays more on the market than they would pay the revnet.
- Cash out price: what the contracts return for burning one token right now. Set by the balance, the supply, and the cash out tax. Acts as a floor: nobody sells below it on the market.
- Market price: what traders in the buyback pool quote right now. It lives between the other two, because stepping outside either bound hands someone an arbitrage.
CEILING issuance price the pool cannot sell above this
▲
market price moves in here
▼
FLOOR cash out price the pool cannot buy below this
above the ceiling → people pay the revnet instead of the pool
below the floor → people cash out instead of sellingStages
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 starts, 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 tokens issued automatically when the stage begins.
- Start: the timestamp the stage takes over from the previous one.
- 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: how much of a cash out stays behind for remaining holders.
- Auto issuance: a fixed number of tokens created for named recipients when the stage begins, without a payment.
STAGE 1 day 0 1,000 tokens per ETH, cut 10% every 30 days
split 30% to contributors, cash out tax 20%
STAGE 2 day 365 rate carries over, cut 5% every 90 days
split 10%, cash out tax 50%
STAGE 3 day 1,825 issuance stops
split 0%, cash out tax 50%, foreverGoing deeper
Cash outs and the cash out tax
Cashing out burns tokens for a share of the balance. The tax makes each cash out leave some value behind, which raises the backing of every token that stays.
With a 0% tax, burning 10% of the supply returns 10% of the balance. With a tax, the return curves down: the first tokens out of the door get less than their proportional share, and the difference stays in the revnet.
- Small cash outs are cheaper than big ones: the formula rewards leaving in pieces, and rewards everyone who stays.
- The tax is set per stage: so a revnet can start liquid and become stickier as it matures, or the reverse.
- Fees: cash outs from a stage with a tax above 0% pay the Juicebox protocol's 2.5% fee on the value returned, and a revnet fee on the tokens burned. Both fund the fee projects' own revnets, so fee payers receive their tokens.
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)
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 may be allowed to redirect who receives the split, but can never raise the percentage. Auto issuance is the other way tokens appear without a payment: a stated amount to stated recipients when a stage starts.
Markets and buybacks
When a revnet has a pool, payments are routed to whichever is better for the payer: issuing new tokens or buying existing ones from the pool.
This is the buyback hook. If the market price dips below the issuance price, a payment buys from the pool instead of minting, and the split share is still honoured from what comes back. Payers always get at least the issuance rate.
Someone who only wants the token, with no interest in funding the revnet, is better off buying directly from the pool, because a direct swap does not pay the split. Interfaces should route to the best price and say which route they took.
Loans
Holders who need cash can borrow against their tokens instead of cashing out. They keep their position and get liquidity now.
Borrowing costs three fees: the Juicebox protocol's 2.5%, a 1% revnet fee, and a prepaid fee the borrower picks between 2.5% and 50%. The prepaid fee buys a window during which repaying costs nothing extra; after that window the cost rises over time until the ten-year expiry. Because the collateral is burned when the loan opens and minted again when it closes, an unpaid loan simply ends with fewer tokens in circulation.
At high cash out taxes a loan can be cheaper than cashing out, since the fee is smaller than the value the tax would leave behind. The loan is an NFT, so it can be transferred or sold.
borrow
└─▶ your tokens are burned as collateral
└─▶ the revnet sends you funds, minus fees
└─▶ you receive a loan NFT as your receipt
repay (any time inside 10 years)
└─▶ return the funds plus any time-based fee
└─▶ your collateral is minted back to you
expiry (after 10 years)
└─▶ the loan is written off, collateral stays burned
└─▶ remaining holders share the same balance with fewer tokensShops
A revnet can sell items. Buying one is a payment like any other: the money enters the balance and the buyer receives tokens alongside the item.
Items are organised into categories and can carry their own supply limits, prices, and transfer rules. They play no part in the revnet's economics beyond bringing in revenue.
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 settle instantly on whichever chain they happen on. Holders can move tokens to another chain. The move cashes the tokens out of the source chain's own balance at a 0% tax and mints them on the destination, so the value that travels is the source chain's backing for those tokens.
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.
The operator
A revnet has no owner. It has an operator with a short, fixed list of powers granted at launch, and none of them touch the economics.
- 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.
Built on Juicebox
Under the hood a revnet is a Juicebox V6 project whose owner is the REVOwner contract. Everything Juicebox can do, a revnet can do; what the contract removes is the owner's discretion.
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.
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.
All of it is open source and inspectable. That removes the need to trust an owner; it does not remove contract, market, bridge, oracle, or key-management risk. Those are borne by whoever uses the code.
- 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 deep it is, and how far the market price sits from the floor and ceiling.
- The transaction: that what your wallet is about to sign matches the call this site describes.