PRISM Run the bench
PRISM
Fixed split · Robinhood Chain · chain id 4663

One flow in.
Fixed bands out.

A fixed share of every trade enters the prism as one undivided flow. It leaves as three bands, and the angle each band leaves at was set at deploy. There is no function that re-aims them, because the function was never written.

See the split Run the bench
3bands, fixed
60°apex
0admin paths
1split rate
The premise

A fee with no fixed angle is just a treasury with better manners.

Most protocols take a cut and then decide where it goes. The decision sits behind a multisig, a governance vote or a variable nobody reads, and it can be re-pointed on any afternoon. The cut is real. The destination is a preference.

01 / the usual shape

The destination is a setting

A treasury address in a storage slot is one transaction away from being a different treasury address. Nothing about the fee itself stops that.

02 / what it costs

You cannot price a variable

If a third of the fee might become buybacks, or might become salaries, then the fee has no meaning you can hold in your head while you trade.

03 / the fix

Fix the angle, not the promise

Refraction does not consult anybody. Give each band a destination at deploy, then delete the ability to change it. What is left is arithmetic.

The mechanism

The glass decides the spectrum. Nobody else gets a vote.

A prism does not choose where each colour goes. The apex angle and the index of the glass decide it, and they decide it identically every time, for everybody, forever. PRISM is that idea applied to a swap fee.

The split happens inside the swap

The rate comes off in the swap path, not in a separate transaction a keeper has to remember to send. There is no queue, no batch and no window where the fee sits somewhere waiting to be routed.

Each band is paid to its destination in the same call. If the swap succeeds, all three bands landed. If any band would fail, the swap reverts and nothing moved at all.

Measured at incidence 48°
WavelengthIndex nDeviation

Snell at a 60 degree apex, Cauchy index. True spread across the visible band is about 1.6 degrees, so the fan in the render above is opened by a constant factor to be visible at this size. The figures in this table are not.

The three bands

Three destinations. Set once, at deploy.

The split rate is a parameter. The way the split divides is not. Fifty, thirty, twenty, in that order, to those three places, on every trade.

50%

Band one, into depth

Paired into liquidity and the receipt burned in the same call. The depth is real, it is on the book, and no address holds a claim on it.

LP, receipt burned
30%

Band two, into the burn

Buys on the open book at whatever the book says, then destroys what it bought. It pays the same price as anyone else trading in that block.

Buy and destroy
20%

Band three, into the reserve

Held on chain in a contract with no withdraw function. Visible to everyone, spendable by nobody, including whoever deployed it.

Reserve, no withdraw
The bench

Set the volume. Read the bands.

Nothing here is a projection. It is the split arithmetic run on a number you choose, which is the same arithmetic the contract runs on a number the market chooses.

GlassFLINT

The split rate is the only thing the glass changes. The fifty thirty twenty division is the same in all three.

Split taken from volume0
Band one, into depth0
Band two, destroyed0
Band three, reserved0
Unrecoverable, total0

Figures are the split arithmetic only. They assume the volume you set actually happens, which is the one thing no contract can promise.

The index

Three glasses. Denser glass bends the band further.

A pool picks its glass once, at deploy. The index is written into the pool and the pool cannot be re-cut afterwards, so what a trader reads on day one is what a trader reads on day four hundred.

CROWN
n 1.52
1.50%
Split rate
  • The light setting. Lowest drag on the trader.
  • Suits pools that expect high turnover and thin margins.
  • Same three bands, same fifty thirty twenty.
FLINT
n 1.62
3.00%
Split rate
  • The default. Twice the depth per unit of volume.
  • Suits a pool that wants its book to thicken visibly.
  • Same three bands, same fifty thirty twenty.
SAPPHIRE
n 1.77
5.00%
Split rate
  • The heavy setting. Highest drag, fastest accumulation.
  • Suits a pool that would rather have depth than volume.
  • Same three bands, same fifty thirty twenty.
What it does

One flow, three fixed angles, step by step.

It plays on a loop. Click a dot to jump to a stage, or pause it and read.

Rails

What the glass is mounted on.

Three pieces, none of them ours: the rollup it settles on, the unit it settles in, and the venue the liquidity sits in.

the chain

Robinhood Chain

An Arbitrum Orbit rollup, chain id 4663, EVM equivalent throughout. Testnet is 46646 and runs the same bytecode.

the unit

USDG, natively

The chain settles and charges gas in USDG, eighteen decimals. Nothing here has to be wrapped on the way in or out.

the venue

Uniswap v4 pools

Liquidity sits in ordinary v4 pools on the same chain, so any router, wallet or explorer reads the market without a special integration.

Settlement

PRISM settles on Robinhood Chain.

A USDG native L2, an Arbitrum Orbit rollup, chain id 4663, fully EVM. The splitter is an ordinary contract with no owner, and every band payment is a public transaction anyone can replay.

Burned receipts and destroyed supply

Both are arithmetic on chain, not a figure this site reports to you.

All three bands run inside the swap

Capped gas, public calldata, no keeper and no settlement window.

No admin path exists

Nothing to pause, upgrade, re-aim or drain. The functions are absent.

Native gas and unit

USDG

Arbitrum L2 rollup

Orbit

Chain id

4663

No custom opcodes

EVM

Wallet

The values you need before you point a wallet at it.

Click any value to copy it. Every endpoint below was answered by the chain itself, not read off a docs page.

Network nameRobinhood Chain Copy
Chain id4663 Copy
Hex chain id0x1237 Copy
Currency symbolUSDG Copy
Decimals18 Copy
Rollup stackArbitrum Orbit Copy
RPC endpointhttps://rpc.mainnet.chain.robinhood.com Copy
Explorerhttps://robinhoodchain.blockscout.com Copy
Testnet chain id46630 Copy
Testnet RPChttps://rpc.testnet.chain.robinhood.com Copy
Sealed at deploy

Cut the glass once.

These are not defaults with a setter behind them. Each one is a constant in the deployed bytecode, which is a different claim, and a checkable one.

ParameterValueChangeable
Band one share50%No
Band two share30%No
Band three share20%No
Band destinations3 addressesNo
Split ratePer pool, at deployNo
Reserve withdrawAbsentNo function
OwnerNoneRenounced at deploy
Order of work

Cut, then widen.

STAGE 01

The glass

Splitter contract, three bands, no owner. Verified source published with the first pool.

STAGE 02

First pool

One pool at one index, so the arithmetic is observable on a real book before anything else exists.

STAGE 03

Three glasses

Crown, flint and sapphire available at deploy time, same bytecode, different constant.

STAGE 04

Open the bench

Anyone can cut a pool without asking, since there is nobody to ask.

Straight answers

The three things a fixed split does not fix.

01

Depth is not price

Band one thickens the book. A thick book still moves down if enough people sell into it. Permanent liquidity is a floor under the spread, not under the chart, and anyone telling you otherwise is selling something.

02

No volume, no bands

Every number on this site is a function of volume. If nothing trades, the split takes nothing, the burn destroys nothing and the reserve stays where it is. The mechanism cannot manufacture its own inputs.

03

Immutable includes the mistakes

The same absence of an admin path that stops a treasury being re-aimed also stops a bug being patched. That is the actual trade. Read the source before you decide it is the one you want.

Short answers

The questions worth asking.

Can the three shares be changed later?
No. They are constants in the deployed bytecode, not storage slots. There is no setter, no governance hook and no proxy in front of the contract, so there is no path that reaches them.
Who holds the reserve?
A contract with no withdraw function. It can receive and it can be read. It has no code path that sends anything out, which includes any path that the deployer might use.
Why three bands and not two, or five?
Three is the smallest number that covers the three things a fee can usefully do: deepen the book, reduce the supply, and hold something in reserve. Two drops one of those. Five splits the same money into portions too small to read.
Does the split rate change with volatility?
No. It is fixed per pool at deploy. A rate that moves with conditions is a rate somebody has to decide, and deciding is the thing this design removes.
What happens if a band payment fails?
The swap reverts. All three bands land or the trade does not happen, so there is never a state where the fee was taken and part of it is sitting somewhere waiting to be routed.
Is there a token?
Not announced on this page. When there is one, its address will appear here and on chain at the same time, and this line will say so plainly rather than hinting.

Cut it once.
Read it forever.

One flow in, three bands out, at an angle nobody can change after the glass is cut.

Run the bench Settlement values