Heliox (Core)
Main contract for subscription state, vault wiring, and product controls
Heliox is the protocol entrypoint. It coordinates owner-level subscription state, vault-level execution state, product controls, and supporting modules. Public docs keep this broad on purpose. The shipped product surface is intentionally narrower than the full internal ABI and operator runbook.
Primary Responsibilities
Subscription State
Tracks billing, registration status, and credit-related product state for the owner account.
Vault Coordination
Connects the product to supported vault, pool, and engine-module surfaces.
Execution Governance
Manages engine-family selection, registry wiring, and product-level controls.
Operational Wiring
Connects Heliox to its execution, payment, referral, and history modules.
Constructor Surface
| Argument | Purpose |
|---|---|
| owner_ | Owner address for Heliox governance. |
| configsAddress | Protocol configuration contract. |
| tradeBookAddress | Trade history module. |
| runnerAddress | Execution module used during cycle handling. |
| paymentsAddress | Fee-splitting module. |
| referralTreasuryAddress | Referral treasury wiring. |
| feeToken1Address | Fee token used for billing and credits. |
| routerAddress | Router used by native purchase helpers. |
| maxUsers_ | Onboarding cap enforced at registration. |
App Surface FirstThe shipped app is the source of truth for supported user-facing controls. Public docs describe the supported surface, not the full maintenance and operator toolkit.