EXPERIMENTAL LIQUIDITY PRIMITIVE
FEES GO IN.
SUPPLY GETS LIGHTER.
An experimental one-sided liquidity primitive for Uniswap V4.
- ETHEREUM
- UNISWAP V4
- HOOK
- ONCHAIN
LIQUIDITY MOVES IN ORBIT.
ORBIT uses a Uniswap V4 Hook to route fee flow through a one-sided liquidity mechanism while permanently removing supply.
- SWAP
A trade executes against the pool.
- FEE
The swap fee is accounted at the hook boundary.
- ORBIT
Fee flow enters the mechanism and does not come back out.
BUILT INTO THE POOL.
The mechanism is not a contract that sits beside the pool. It is attached to the pool itself, invoked by the pool manager on every swap.
ONE SIDE.
ONE DIRECTION.
Liquidity is a population, not a shape. As the mechanism runs, depth stops sitting symmetrically around the active tick and collects on a single side of the curve.
Under normal conditions liquidity is provided on both sides of price. The mechanism biases that placement: as fee flow is absorbed and supply leaves circulation, the remaining depth is redeployed to a single side of the curve.
The effect compounds while the mechanism is active. It is a property of where liquidity sits — not a claim about where price goes.
SUPPLY GETS LIGHTER.
What enters the mechanism is not redistributed. It is removed from the supply and does not return.
Figures shown here are example values chosen to demonstrate the shape of the mechanism. They describe no live pool and report no protocol activity.
THE FLOOR FOLLOWS THE FLOW.
Two quantities move in opposite directions while the mechanism runs: circulating supply falls, and the concentration of remaining liquidity rises. The plot below shows the direction of that relationship — nothing more.
Permanent supply destruction can create upward pressure on the liquidity floor while the mechanism remains active. The floor index above is a shape, not a price: it ratchets because removal is irreversible, not because demand is assumed.
ORBIT does not guarantee demand, volume, liquidity or price appreciation. The plot is a conceptual relationship built from illustrative values and should not be read as a projection of any market outcome.
EVERY FLOW HAS A TRAJECTORY.
Some flow is captured. Some settles into orbit. Some passes through and keeps going.
- CAPTURED
- IN ORBIT
- PASSING THROUGH
POWERED BY HOOKS.
Uniswap V4 lets a pool call out to attached code at fixed points in the swap lifecycle. ORBIT occupies those points.
// conceptual shape of the hook
contract OrbitHook is BasedHook {
function beforeSwap(...) returns (bytes4) {
// observe pool state entering the swap
}
function afterSwap(...) returns (bytes4) {
uint256 fee = _accountFee(delta);
_orbit(fee);
}
function _orbit(uint256 amount) internal {
_burn(amount * BURN_BPS / 10_000);
_placeOneSided(amount - burned);
}
}The block above is a conceptual sketch used to show where the mechanism sits in the swap lifecycle. Parameters, ratios and call signatures are indicative.
THE FLOOR CAN RISE.
THE PROJECT CAN STILL DIE.
ORBIT creates a deflationary liquidity mechanism. It does not guarantee demand, volume, adoption, liquidity or price appreciation.
THE MECHANISM, IN PARTS.
The hook is attached to the pool at initialisation and is invoked by the pool manager around the swap lifecycle. It is not an external contract that observes the pool after the fact — the pool calls it.
Because the callbacks run inside the swap, fee flow can be measured and routed in the same transaction that produced it.
- ATTACHED AT POOL INITIALISATION
- INVOKED AROUND SWAP
- SAME-TRANSACTION ACCOUNTING
Deployment metadata is published here as the mechanism moves on-chain. ORBIT is experimental and unaudited software.
ENTER THE FIELD.
FEES GO IN.
SUPPLY GETS LIGHTER.