Security FAQ

Can the bot withdraw my funds?

No. Aegis uses API keys with trading-only permissions. The required permissions are specifically Futures Trading (and for Binance: Spot Trading for some account types). Withdraw, internal transfers, and bank/fiat withdrawal permissions are explicitly required to be disabled when you add an API key to Aegis.

If an API key has withdrawal permissions enabled, it does not meet the security requirements. See API Keys Overview for the full permission matrix.

How are my API keys stored?

API keys and secrets are encrypted at rest using AES-256-GCM before being stored in the Aegis database. The encryption key is managed at the infrastructure level and is not accessible from the application layer.

Once submitted through the dashboard, an API key is never shown back in plaintext. There is no “reveal key” function.

Is my private key stored anywhere?

LP wallet and main wallet: No. Aegis never requests, stores, or transmits your LP wallet private key or seed phrase. The LP wallet is connected read-only for on-chain position scanning — Aegis never asks for signing authority over it.

HyperLiquid agent wallet: HyperLiquid’s auth model uses a delegated agent wallet instead of a traditional API key. The credential you provide — the HyperLiquid Signing Key (Agent Private Key) — is itself a real ECDSA private key, not a traditional API secret with permission checkboxes. When you add a HyperLiquid execution wallet, Aegis stores that agent private key encrypted with AES-256-GCM at rest and never shows it back after saving, then uses it to sign trading orders server-side, autonomously and without per-transaction confirmation. The agent wallet has no withdrawal or transfer capability by construction — the executor only ever signs order / cancel / modify, never withdraw, usdSend, spotSend, or vaultTransfer — so it can only sign trading orders on your behalf, never move funds. If this key is ever compromised, the exposure is operational (an attacker could place adverse trades), not a withdrawal or custody risk, and it is revocable at any time from your HyperLiquid account by deauthorizing the agent wallet. This is separate from your owner wallet: Aegis never asks for your owner wallet’s private key or seed phrase. See HyperLiquid Signing Key for the full setup.

Binance: Binance uses a conventional API key/secret pair — no private key is involved. Aegis stores only that exchange credential, encrypted at rest.

What happens if my API key is compromised?

If you believe your exchange API key may be compromised:

Log in to your exchange account immediately
Revoke or delete the API key from the exchange API key management page
In Dashboard > Futures Wallets, remove the execution wallet entry that used the compromised key
Create a new API key with the correct permissions
Re-add the execution wallet with the new API key

Revoking the key on the exchange stops any further use immediately. After removal from the dashboard, the Aegis bot will no longer attempt to use those credentials.

For HyperLiquid, step 2 means deauthorizing the agent wallet from your main HyperLiquid account (Settings > Agent Wallets, or API) — there is no “API key” to revoke, only the agent wallet’s authorization. Because the HyperLiquid Signing Key cannot withdraw or transfer funds, a compromised key is an operational risk (adverse trades), not a withdrawal risk.

Does Aegis support two-factor authentication?

For exchange API keys, Aegis does not bypass or interact with your exchange’s own 2FA — API key authentication is handled entirely by the exchange. Enabling 2FA on your exchange account is recommended and does not affect Aegis API key operation.

Who has access to my API keys?

API key data is encrypted with AES-256-GCM at rest. Access to the decryption key is restricted to the Aegis infrastructure. The key is not accessible to dashboard users, including yourself, after submission.