rilluneProtocol guide.
Understand how your policy responds, then make it your own.
Understand your fee policy.
Rillune brings market conditions, fee budgets and reference-data safeguards into one policy workspace. Compare the conditions that matter to you, inspect each rule, and keep your strategy ready to revisit.
Three components. One ceiling.
Fees are expressed in basis points: 1 bp = 0.01%. The base fee is the starting rate. Session adjustments account for stock-market hours, and volatility sensitivity controls how much the fee responds to your selected volatility input.
With a 5 bps base fee and 2% volatility input at sensitivity 6, the open-session fee is 17 bps (0.17%). After-hours adds 8 bps, bringing it to 25 bps. On a planned amount of 1,000 USDC, those fees are 1.70 and 2.50 USDC.
Stock-token policies add 8 bps after hours and 20 bps on weekends. Crypto and stable-asset policies apply no session premium. The fee ceiling caps the total.
Reference freshness
When the reference-age input exceeds the selected freshness limit, the calculation pauses and explains why. The oracle-outage condition produces the same result. A higher fee never overrides the freshness rule.
Find your fee-budget boundary
The Fee Map evaluates five volatility levels across open, after-hours, weekend and reference-outage conditions. A checkmark means the calculated fee is within your budget; an arrow means it is above. Select any cell to load those conditions into the current policy.
Your budget is a comparison threshold in basis points. It does not change the fee ceiling. The boundary calculation checks volatility in 0.01% increments and uses the same upward rounding as the fee engine. A paused quote is never counted as a zero-cost option.
With NVDA’s 5 bps base and sensitivity of 6, an open-session volatility input of 4.16% produces 30 bps. At 4.17%, rounding lifts the fee to 31 bps. The Fee Map identifies that boundary while respecting your chosen ceiling.
Follow a pause all the way to recovery
Guard Replay applies a sequence of calculated inputs to your policy. Reference interruption stops updates at step 8, allowing the reference age to increase until it exceeds your freshness limit. Step 20 supplies a fresh reference. Quotes resume if all reference conditions are valid.
The volatility shock adds four percentage points from step 15, capped at the supported 10% input. The two events can be combined. Select an event to jump to its step, play the sequence, or move the timeline manually. Peach markers identify paused steps; no fee is plotted during a pause.
The readout shows the reference age, volatility and decision at the selected step. Export CSV to inspect every point, elapsed second and event. The replay spans 24 intervals and 25 observations; it represents calculated conditions rather than historical market performance.
Compare and share exact policy settings
Pin a policy, then change its controls to compare the base fee, sensitivity, session, reference limits and fee on the same amount. A lower calculated fee does not by itself establish which policy is better.
Share policy creates a link that restores the market, policy inputs and planned amount in Hook Studio. It excludes wallet addresses, saved strategy names and your workspace. Export policy saves the same settings in JSON, which can be loaded through Import policy. Review shared settings before saving them.
Keep your strategies organized
Give each strategy a name, planned allocation and target price range. Increase or reduce the plan, revise the range or remove it. Strategies and activity are stored in this browser, separate from wallet balances. Export a backup before switching devices.
Read the allocation as a whole
Strategy Check combines allocations for the same market, displays their share of the total plan and identifies allocation attached to paused quotes. The fee average is weighted by planned allocation and includes only strategies whose saved reference conditions permit a quote. If every strategy is paused, no average is shown.
The target-range width is the distance between your upper and lower targets divided by their midpoint. It describes your chosen range; it is not measured against a live market price. Neither this width nor the allocation view forecasts returns.
Common questions
Why did the fee stay unchanged when volatility rose?
Your policy may have reached its ceiling, or sensitivity may be zero. Small changes can also remain within the same integer basis-point rounding step. The fee breakdown makes each case visible.
Why does changing the session leave some markets unchanged?
Stock-token policies apply session premiums. Crypto and stable-asset policies do not. A reference outage pauses quotes for every asset class.
Does increasing the fee ceiling clear a paused quote?
No. Reference freshness is checked independently. Update the reference condition; increasing a fee limit does not override the freshness guard.
Can I move a saved strategy to another device?
Export your workspace from Strategies, then import it on the other device. Import merges new strategy IDs and keeps existing entries. A policy link transfers its rule settings and amount only.
Wallet connection
Connecting a wallet lets you view its public address, selected network and native balance. Connection and network changes use your wallet’s own prompts. Saving or editing a strategy does not sign a transaction or transfer funds.
Contract and execution status
Rillune currently provides policy analysis and strategy planning. Deposits, swaps and funded liquidity positions are not available. No Rillune pool or RILL token contract has been deployed. Asset symbols identify policy categories and do not establish issuer affiliation or the availability of a Rillune trading pool.
Hook Studio uses the inputs you select; it is not connected to a live market-price or verified oracle feed. Fee estimates exclude price impact and network fees.
Hook implementation
The Solidity source uses Uniswap v4’s beforeInitialize and beforeSwap callbacks with dynamic LP fees. Policies are registered once per pool; an immutable reporter supplies timestamped session and volatility signals. The contract trusts that reporter and does not independently validate exchange calendars or oracle signatures. The freshness guard does not enable a liquidity-removal callback.
Contract validation covers policy behavior and callbacks using a mock pool manager. Full pool integration, a verified oracle adapter and independent security review remain required before onchain execution.