Connect Wallet
Aegis supports two paths for associating an LP wallet with your account. Both paths result in the same outcome: your wallet address is used for on-chain LP position scanning.
Path 1: Dashboard Connect Wallet Flow
Section titled “Path 1: Dashboard Connect Wallet Flow”The Connect Wallet button in the dashboard header opens a connector modal. Aegis uses wagmi and supports the following connectors:
| Connector | Description |
|---|---|
| Injected / MetaMask-compatible | Any browser extension wallet (MetaMask, Rabby, Frame, etc.) |
| WalletConnect | QR-code / deep-link pairing with mobile or desktop wallets |
| Coinbase Wallet | Coinbase Wallet browser extension or mobile app |
| Safe | Safe (formerly Gnosis Safe) multisig smart contract wallet |
- Click the Connect Wallet button in the dashboard header.
- The connector modal opens. Select your preferred connector.
- Approve the connection request in your wallet (signature only — no transaction is submitted, no funds are moved).
- Your wallet address is synced to your Aegis account (
POST /api/user-wallets).
Your connected address is now visible in the Wallets panel and is used to scan for active Uniswap V3/V4 and PancakeSwap V3 LP positions on supported chains.
Path 2: Read-Only Public Address Entry
Section titled “Path 2: Read-Only Public Address Entry”If you prefer not to connect a wallet via the modal, you can enter your LP wallet’s public address directly in the Wallets panel. Aegis will scan that address on-chain for LP positions.
In this path, the LP wallet is never “connected” to the bot in any programmatic sense — only the public address string is stored and used for scanning.
Supported Chains
Section titled “Supported Chains”Aegis scans LP positions on the following networks:
| Chain | Support level |
|---|---|
| Ethereum (mainnet) | Full support |
| Arbitrum | Full support |
| Base | Full support |
| Optimism | Full support |
| BNB Smart Chain (BSC) | Partial support |
Solana is not supported.
Pair Filter Rule
Section titled “Pair Filter Rule”Not all LP positions are eligible for Aegis hedging. Aegis applies a pair filter:
Valid pairs: native USDC or USDT must be one side of the pair.
| Example | Eligible? |
|---|---|
| ETH / USDC | Yes |
| WBTC / USDT | Yes |
| ETH / DAI | No (DAI is not native USDC/USDT) |
| USDC / USDT | No (stablecoin-only pair, no delta exposure) |
Token ID Scanning
Section titled “Token ID Scanning”For advanced use cases, Aegis supports scanning by NFT Token ID. Uniswap V3, Uniswap V4, and PancakeSwap V3 represent LP positions as non-fungible tokens minted by the NonfungiblePositionManager contract.
If you know your position’s Token ID, you can enter it directly in the Wallets panel to target a specific LP position rather than scanning all positions for an address.
Cross-references
Section titled “Cross-references”- Approvals — token approval model and security education
- Wallet-Bot Binding — how execution wallets bind to bot strategies
- API Keys — adding CEX execution keys for hedging