Core Wallet on Avalanche V3 forces unnecessary Ethereum network switch

I am posting this here because I could not find an existing issue describing this exact Core + Avalanche V3 connection behavior. I am using Aave V3 on Avalanche exclusively , with the Core browser extension . There appears to be an unnecessary network-switch requirement during wallet connection. Steps to reproduce Open the Core browser extension. Set the active network to Avalanche C-Chain . Open app.aave.com . Select Avalanche Market V3 . Confirm that the Aave interface is already displaying the Avalanche market. Select Connect Wallet → Core . During the connection process, Core displays: “ app.aave.com is requesting to switch your active network to Ethereum.” If I reject the Ethereum network switch, the Core/Aave wallet connection fails. If I approve the switch to Ethereum, the wallet connects successfully. When I later initiate an Aave transaction on Avalanche, I then have to switch the wallet back from Ethereum to Avalanche C-Chain . Expected behavior Because: Aave is already set to Avalanche Market V3 Core is already connected to Avalanche C-Chain all of my Aave activity is on Avalanche the wallet connection should initialize directly on Avalanche C-Chain (chain ID 43114) . There should be no need to switch to Ethereum Mainnet during the initial connection and then switch back to Avalanche for the transaction. Actual behavior The current sequence is: Core on Avalanche → Aave Avalanche V3 → Connect Core → forced Ethereum switch → wallet connects → initiate Avalanche transaction → switch back to Avalanche Rejecting the Ethereum switch prevents the wallet from connecting. Additional information Wallet: Core browser extension dApp: app.aave.com Market: Aave V3 Avalanche Intended network: Avalanche C-Chain Ethereum transactions involved: None ETH gas involved: None Issue is reproducible consistently. I have attached a screenshot showing Aave already on the Avalanche V3 market while Core simultaneously reports that app.aave.com is requesting a switch to Ethereum. Could you please confirm whether this Ethereum-first connection behavior is intentional? If not, could the wallet connection logic use the currently selected Aave market / current wallet chain when initializing the Core connection, so Avalanche users can connect directly on chain ID 43114? 2 posts - 2 participants Read full topic