Allocation ratio
A/B
The split between two tokenized assets
You decided on 70/30 across two positions. Markets move, the weight slides, and within a quarter the portfolio you hold is no longer the one you chose.
Open the composerProgrammable exposure for tokenized assets
Set your exposure.We maintain it.
Declare the ratio you want to live at — the split between two tokenized assets, or the collateral standing behind what you borrow. Ratio holds that number for you, block after block, through every price move. You never place the rebalancing trade.
Scroll
Collateral deposited
0.0M
tokenized equity + ETF
rUSD outstanding
0.0M
avg. rate 4.85%
Average ratio held
0%
target band ±1.5%
Rebalances settled
0
zero liquidations to date
The primitive
Declare it once.
Every position on Ratio is one number and a tolerance around it. The protocol reads that number on every block and does the arithmetic you would otherwise be doing by hand, at the hour you would least like to be doing it.
Collateral ratio
C/D
The cover standing behind your debt
You decided on 250% while your rUSD is outstanding. Same drift, except at the far end of this one there is a liquidation rather than a tracking error.
Open the engineDeclare
One call fixes the target and the tolerance around it. The engine rejects a band whose floor would sit too close to liquidation — a promise it could not keep is not accepted.
Watch
Both legs are priced by a dual feed behind a staleness guard. Anyone can read the position and compute its drift; no privileged keeper stands between you and the number.
Correct
Crossing the band moves the smallest amount that restores the target — a trim or an extend, never a full unwind, and never a cliff-edge auction you had to stay awake for.
Ratio one · allocation
Two assets, one number
Choose a pair and the split you want to hold. Ratio prices both legs and moves only the difference when the weight leaves your band. Drag anything below and the market re-runs against your parameters.
AllocationIn band
Pair
Target split70 / 30
5%95%
Tolerance band±2.5%
- Rebalances
- 0
- Turnover
- $0
- Worst drift held
- —
- Left alone, ends at
- —
Weight against target
One simulated trading year on both legs, drawn from each asset’s realized volatility.
Maintained
Left alone
Your band
Opened at target. Run the market and let both legs move.
Simulated price paths, not live market data. Allocation vaults are not deployed yet — the target-and-band machinery below them is what is written in the contracts.
Ratio two · collateral
The collateral engine
The same machinery, pointed at debt instead of allocation. Open a position, pick the cover you want to keep, then knock the price down and watch what the engine does about it. Every number below is computed live from the parameters on the left.
PositionNominal
Collateral asset
Deposit$50,000
$5K$500K
Target ratio250%
130% aggressive500% defensive
Health
2.05×
Distance to the liquidation ratio of 122%.
- Collateral
- —
- rUSD debt
- —
- Equity
- —
- Engine activity
- —
Collateral value vs. debt
60 sessions of simulated price action. The engine rebalances whenever the ratio leaves the target band.
Collateral
Debt
Liquidation floor
Borrow power
$20,000
at 250% target
Exposure kept
100%
no collateral unwound
Liquidation price
$0.00
from spot
Levered carry
0.00%
borrow rate vs. drift
Position open. The ratio sits inside its band.
Collateral registry
Markets
Each asset carries its own loan-to-value, liquidation threshold and debt ceiling, set by realized volatility and on-chain depth rather than a single blanket parameter.
| Asset | Oracle price | 24h | 30d | Max LTV | Liq. threshold | Borrow APR | Supplied | Status |
|---|
Drag the table sideways →
Illustrative parameters for a pre-launch protocol. Prices and balances are simulated, not live market data.
System
Four contracts, one invariant
The vault holds the asset. The engine owns the ratio. The oracle prices it. Keepers do the work and get paid for it. Nothing else is allowed to move collateral.
Drag the diagram sideways →
Isolated
Each collateral type carries its own ceiling. A broken oracle on one asset cannot drain the others.
Continuous
Rebalancing is a small, frequent trim — not a cliff-edge auction at the liquidation line.
Permissionless
Anyone can run a keeper. The reward scales with how far the position has drifted.
Composable
rUSD is a plain ERC-20 with permit and every position is readable on-chain, so anything can price, hedge or unwind one.
Why it matters
Traditional assets, crypto mechanics
A tokenized share that only sits in a wallet is a screenshot of ownership. The point of putting it on-chain is what happens next.
Capital
Liquidity without exit
Raise cash against a position instead of closing it. No realized gain, no lost upside, no re-entry cost.
Control
Risk as a parameter
Your leverage stops being a number you monitor and becomes a number you declare once.
Reach
One collateral layer
Equities, ETFs and treasuries settle into the same vault standard the rest of DeFi already speaks.
Questions
The parts worth asking about
Short answers, taken from what the contracts actually do rather than what would sound best.
What does non-custodial mean here, concretely?
Collateral sits in RatioVault, and the engine is the only contract permitted to move it — only inside the target you declared. There is no queue, no withdrawal window and no address that can sweep a vault. You leave on whatever block you decide to.
Who actually performs the rebalances?
Anyone. Rebalancing is permissionless and the reward scales with how far the position has drifted, starting from a base bonus and rising with drift up to a hard cap. There is no whitelisted keeper set to petition, and no single operator whose downtime becomes your problem.
Can the engine add leverage I did not ask for?
Only if you let it. Every target carries an autoExtend flag; set it false and the engine deleverages when you drift under the band and does nothing at all when you drift over it. Set it true and it also draws back up to the target after a rally.
Can I still be liquidated?
Yes, in a gap. The engine refuses any target whose band floor does not clear the liquidation ratio with room to spare, and it corrects long before that line — but a move fast enough to outrun every keeper in one block outruns Ratio too. Continuous rebalancing makes liquidation unlikely; it does not make it impossible, and no protocol that tells you otherwise is describing itself honestly.
What happens if an oracle goes wrong?
Prices come from a dual feed with a staleness guard, and each collateral type is isolated behind its own debt ceiling. A bad print on one asset cannot reach into the others, and a guardian can pause deposits and borrows on a single market without touching anyone’s ability to repay or exit.
Is any of this live?
Not yet. The contracts are written and under test — vault, engine, oracle, rebalancer and rUSD — and the Robinhood Chain deployment has not happened. Every price, balance and chart on this page is simulated, and the numbers in the header are illustrative rather than measured.