A recurring friction point has surfaced in the Aave ecosystem: users attempting to connect their Core browser extension wallet to Aave V3 on Avalanche encounter an unexpected and illogical requirement to switch networks to Ethereum before completing the connection handshake. The issue appears systematic and reproducible—when users have already configured both their wallet and the Aave interface for Avalanche C-Chain activity, the protocol inexplicably requests approval to default to Ethereum Mainnet instead.
The technical mechanics reveal a deeper integration problem between wallet connection initialization and chain-specific market selection. When a user navigates to app.aave.com, selects the Avalanche Market V3, and initiates wallet connection, the application should theoretically recognize that the target chain has already been specified and match the wallet's active network accordingly. Instead, the current behavior forces a network switch request to Ethereum—one that cannot be rejected without breaking the connection entirely. Only after approving this unnecessary switch can the user successfully connect their Core wallet. The sequence then requires a manual switch back to Avalanche C-Chain before executing any transactions, creating unnecessary friction and potential for user error.
This represents a usability gap rather than a security concern, yet the implications matter for adoption. Users managing positions exclusively on Avalanche—attracted to the network's lower fees and faster confirmation times—face repeated manual intervention steps that undermine the streamlined experience that cross-chain composability should deliver. The root cause likely stems from how Aave's frontend initializes default network logic, possibly defaulting to Ethereum regardless of which market interface the user explicitly selected. Given that Aave V3 operates across multiple chains including Polygon, Arbitrum, Optimism, and Avalanche, the connection logic should respect the user's explicit market selection and pre-configured wallet state.
The Core development team and Aave's frontend engineering should coordinate on a fix that either respects the user's active chain during wallet connection or eliminates the unnecessary network-switch prompt entirely when the target chain is already selected. As multi-chain protocols mature, these friction points become competitive liabilities—particularly for chains positioned as efficiency alternatives to Ethereum. Resolving this class of UX issue will be essential as DeFi scales across ecosystems.