Wallet-Bot Binding
Execution wallets are the venue accounts that Aegis uses to place futures hedges. Each execution wallet is created in the dashboard and stores venue-specific credential material, encrypted at rest with AES-256-GCM:
- Binance Futures: an API key + API secret pair (two exchange-issued strings).
- HyperLiquid: the agent wallet private key, entered as the API Key Secret — there is no separate “API key” field; Aegis derives the agent wallet address server-side from that secret on save.
Execution wallets are separate from your LP wallet. The LP wallet is the on-chain public address Aegis scans (read-only) for your concentrated-liquidity positions; the execution wallet is the venue account plus its trading credentials.
The Wallet address field when creating an execution wallet refers to the owner/exchange account public address associated with the credentials — for HyperLiquid, this is your main account address (not the agent wallet address). This is distinct from the LP wallet address used for on-chain position scanning (see Connect Wallet).
Bot Type Binding
Section titled “Bot Type Binding”When you create an execution wallet in the dashboard, you must select a bot type:
| Bot type | Strategy |
|---|---|
bastion | LP protection (lower_short, upper_short legs) |
vanguard | Breakout (upper_long leg) |
orbit | Mean-reversion (configurable direction) |
The botType field is mandatory and fixed at the time the execution wallet is saved. This design exists to enforce:
- Exposure separation — each bot type has a distinct risk profile and leg structure.
- Clean audit trail — each execution wallet’s trade history is associated with a single strategy type.
One-Wallet-Per-Perp-Symbol Constraint
Section titled “One-Wallet-Per-Perp-Symbol Constraint”Each execution wallet can only have one active strategy per perpetual symbol. You cannot run two Bastion strategies simultaneously on the same ETH/USDC perp using the same execution wallet.
Numeric example
Section titled “Numeric example”Suppose you have 5 active ETH/USDC concentrated liquidity positions on Uniswap V3 across 5 different tick ranges, and you want Bastion to hedge each one independently. You must create 5 separate execution wallets, one for each strategy instance.
| LP position | Execution wallet |
|---|---|
| ETH/USDC position #1 (tight range) | Execution wallet A (Bastion) |
| ETH/USDC position #2 (wide range) | Execution wallet B (Bastion) |
| ETH/USDC position #3 | Execution wallet C (Bastion) |
| ETH/USDC position #4 | Execution wallet D (Bastion) |
| ETH/USDC position #5 | Execution wallet E (Bastion) |
Multi-Bot Usage
Section titled “Multi-Bot Usage”To run multiple bot types (for example, Bastion and Orbit on the same LP pool), you must create separate execution wallets — one for each bot type.
| Goal | Execution wallets required |
|---|---|
| Bastion + Orbit on the same ETH/USDC pool | 2 wallets (one per bot type) |
| Vanguard on BTC/USDC and Orbit on ETH/USDC | 2 wallets (one per bot type and symbol) |
| Three Bastion strategies on different pools | 3 wallets (one per symbol) |
Adding an Execution Wallet
Section titled “Adding an Execution Wallet”See API Keys — Add to Dashboard for the step-by-step guide to creating an execution wallet, including all form fields and the encryption model.
Cross-references
Section titled “Cross-references”- Connect Wallet — LP wallet association (read-only)
- Approvals — token approvals and current beta scope
- API Keys — Add to Dashboard — execution wallet creation guide
- Dashboard — Futures Wallets — managing execution wallets in the UI