Futures Wallets
The Futures Wallets panel is where you manage execution wallets — the exchange API credentials that the Aegis bot uses to open and close hedge positions on centralized futures exchanges.
Adding an execution wallet
Section titled “Adding an execution wallet”To add a new execution wallet, use the Add Wallet form. The fields common to every venue are:
| Field | Description |
|---|---|
| Exchange | Select the exchange: Binance Futures or HyperLiquid (BingX: Coming soon) |
| Bot type | Select the bot type: Bastion, Vanguard, or Orbit. Mandatory and fixed at creation. |
| Name / label | A descriptive name for this wallet entry (e.g., “ETH/USDC Bastion — Binance”) |
| Wallet address | The owner/exchange account public address associated with these API credentials. For HyperLiquid: your main account address (not the agent wallet address, not the LP wallet address). Distinct from your LP wallet — see Wallet-Bot Binding. |
The credential fields differ by venue:
- Binance Futures: an API key field and an API secret field — the two strings issued by Binance API Management.
- HyperLiquid: no manual “API key” field is shown. You enter only the API Key Secret — the agent wallet private key (64 hex characters). On save, Aegis derives the agent wallet address server-side from that secret and shows it back on the confirmation screen; you never type the agent wallet address.
After saving, the Binance API key + secret (encrypted together) or the HyperLiquid API Key Secret are encrypted with AES-256-GCM at rest and are never shown back in the dashboard.
Bot type is immutable
Section titled “Bot type is immutable”The bot type (botType) you select when creating an execution wallet cannot be
changed afterward. If you need a different bot type for the same wallet address,
you must delete the existing execution wallet entry and create a new one with the
correct bot type.
Running multiple bots
Section titled “Running multiple bots”To run more than one bot type, create separate execution wallet entries — one per bot type. Each execution wallet is bound to exactly one bot type. See Wallet-Bot Binding for the one-wallet-per-symbol constraint and multi-bot usage patterns.
API key permissions
Section titled “API key permissions”Ensure your API key has the required trading permissions and that withdrawal permissions are explicitly disabled. See API Keys Overview for the per-exchange permission matrix.
Removing an execution wallet
Section titled “Removing an execution wallet”To remove an execution wallet entry, locate it in the Futures Wallets list and use the remove/delete action. Removing an execution wallet deletes the stored API credentials from the Aegis database. Active strategies bound to that wallet will stop executing.
Before removing, close or pause any active strategies that use the wallet to avoid unexpected position states.