Glossary

Key terms and concepts used in the Heliox documentation

Terms

17
TermDefinition
TOKEN0The first token in the configured Heliox trading pair.
TOKEN1The second token in the configured Heliox trading pair.
feeToken1The fee token used for plan purchases and cycle credits in the current deployment.
CycleA state machine that starts (consuming 1 credit), rebalances through multiple calls, and closes when the secured NAV threshold is met.
Secured NAVAn internal confirmation metric Heliox checks before a cycle is allowed to close.
EqualizationThe balancing trade used at cycle start or rollover to move the pair closer to an even starting state.
Engine FamilyA versioned engine line that vaults select explicitly and roll forward within over time.
Engine VersionA specific deployable module within an engine family. New cycles and rollovers can move to newer enabled versions.
CONFIG_DELAYThe 1-hour mandatory delay used for queued config changes. Engine registry upgrades have their own activation delay.
Check ModeUser setting (1/2/3) that defines which positive side change can trigger a close: TOKEN0, TOKEN1, or both.
RolloverWhen a cycle threshold is met and credits remain, the old cycle closes and a new one starts automatically.
Terminal CloseWhen rollover is not possible, the active cycle closes permanently. Mode 1 settles to TOKEN0, mode 2 settles to TOKEN1, and mode 3 closes in place.
maxTradePctBpsUser-set maximum trade size as percentage of portfolio, in basis points (1000–10000 = 10%–100%).
maxSlippageBpsMaximum allowed slippage for swaps, in basis points. Enforced per-swap.
cycleThresholdBpsThe minimum secured NAV gain, in basis points, required for a triggered cycle to actually close.
CooldownMinimum time between consecutive reBalance calls for a cycle, sourced from the selected engine version rather than one global contract value.
Basis Points (bps)1 bps = 0.01%. Used throughout for fees, slippage, thresholds, and commission rates.