Missing WBTC deposit in Aave V4 Core Hub - not showing on dashboard
Hello Aave Support Team, I am experiencing a critical issue with a recent WBTC deposit on the Aave V4 protocol (Ethereum Mainnet). I deposited 0.00492725 WBTC into the Aave Core Hub, the transaction was successful on-chain, but the funds are not displaying correctly on the pro.aave.com dashboard, and my Health Factor did not increase as expected. Transaction Details: • Wallet Address: `0x8dF87ED1d73eDB9998A81678096Ab0F9A34aB435` • Transaction Hash: `0x946321d3d024e1789f7ddc7d280ddc0d25ea90eefb4b5755808e575f3f25a02a` • Amount: `0.00492725 WBTC` • Contract Interacted With: `0x94e7A5dCbE816e498b89aB752661904E2F56c485` (Aave: Main Spoke) • Event Emitted: `Supply` (Log 218) with `reserveId: 3` The Issue: 1. Before the deposit, I had an active borrow position of ~$1,201 USDC against ~0.03 WBTC. 2. When simulating the deposit of the additional 0.00492725 WBTC, the UI showed my Health Factor would increase to ~1.40. 3. After the transaction was confirmed, my Health Factor remained stuck at ~1.29. 4. The deposited amount of 0.00492725 WBTC is nowhere to be found as a separate balance on the Dashboard, nor did it visibly update the main collateral balance in a way that reflects the expected Health Factor increase. 5. However, when I click “Withdraw”, the max available amount shows `0.03158279 WBTC`, which indicates the funds are in the protocol, but the UI and Health Factor calculation seem bugged or are routing the funds to a different `reserveId` that isn’t properly backing my USDC borrow. Could you please investigate why this deposit is not reflecting correctly on the UI and why it didn’t improve my Health Factor? I need to know how to safely withdraw this specific amount or properly apply it to my main position. Thank you. 1 post - 1 participant Read full topic
DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at Aave_blog.
Want the full article?
Continue reading on Aave_blog →