Hi Aave Team,
I, Meilough Gonzales, am reporting a serious UI bug on Aave’s platform (app.aave.com). The platform is displaying my staked AAVE balances incorrectly and falsely showing that my staked AAVE was immediately transferred to a phishing address after staking, despite the funds being safe on-chain. All staking was done on the official app.aave.com. Here are the details:
- Wallet 1: 0xDB352d44f79c844cC4f121169af6e0b94dBd97f0
- Staked: 0.654076 AAVE (txs: 0x06e24e03f73d67f372d4c426a1f016f47faf0135deb3fb9a74e9dae6dc854084 [0.5 AAVE, March 11, 2025], 0xaf93eb75b78892fe5f5b3ab41ef077de2ff4a6efd167fe6863ba56b1af0d4952 [0.154076 AAVE, March 12, 2025]; approvals: 0x8f3039a98b17ced98c2669e79bed24a31887bf4b45c1b92d31b3e9c413012a63 [March 11, 2025], 0xbc01425d07b00776b225126d95494493d39433a06ebfb0ee8edf3ab72c142351 [March 12, 2025]).
- UI Shows: “< 0.01 AAVE” staked (should be 0.654076), “< 0.01 AAVE” claimable (~$0.09).
- Voting Power: 0 (should be 0.654076).
- Wallet 2: 0x9596bC7Ce834F3f08A88B672f12C7c72638Dd385
- Staked: 1.1 AAVE (txs: 0x32407177ac2958980304e516b856fb9f863b071851a24fb8da734b77b0ed0dcb [0.5 AAVE, March 12, 2025], 0x635fb938d96472d37b7753f5eb83f66bf74d7e2d14956ee740ffcbf4fabbf682 [0.3 AAVE, March 14, 2025, also listed as 0x85b4de6c…], 0x45e14b12074f9e1f5867cdcb6d07b5144dddf6b77d2081e724275efaa6c9f593 [0.2 AAVE, March 16, 2025], 0x8b8477e1b3d6483ceba4feb4ba41e0a7bdfea8b458db32752e06954c88343527 [0.1 AAVE, March 17, 2025]; approvals: 0xf110209c66e3bce48c3fd0b923f2f543ae39e0f54c1836b16bdef41eec6ad866 [March 12, 2025], 0xad077608f2d805d15926b434129dcdef61e8383d7cfd9925cd37544ac80a6ae8 [March 13, 2025], 0x6a40bbbcc0192d8dca359492d4570afa137ca1516c543610253f11d7f1a56bc1 [March 16, 2025]; transfer: 0x12abe78deefb61153eaeef4b49a46c2aa783705179c8d2c77d5e026b4d58dda6 [0.5 AAVE, March 16, 2025, received by 0x4da27a…]).
- UI Shows: 0 AAVE staked (should be 1.1), “< 0.01 AAVE” claimable (~$0.60).
- Voting Power: 0 (should be 1.1).
- Video Evidence: For tx 0x32407177… (March 12, 2025), the video shows staking on app.aave.com, Etherscan confirming the stake to 0x4da27a… (Aave Staking Contract, part of the Safety Module), but the UI immediately shows the staked AAVE as transferred to a phishing address. On-chain, the 1.1 stkAAVE is still in 0x4da27a…
- Wallet 3: 0x3F60f04E19eb41021577a07453890A6CC7D8e334
- Staked: 0.75 AAVE (tx: 0x7cc7fd99ec7aebff42deb0aabd9ace459448fff4038068ac5be0b6b85728048a [0.75 AAVE, March 11, 2025]; approval: 0xc1ae81cb0ebb27639454ddfd84f09732884ee2718a870e455c2d1e843aeb7c6f [March 11, 2025]).
- UI Shows: 0 AAVE staked (should be 0.75), based on the pattern.
- Voting Power: 0 (should be 0.75).
- Wallet 4: 0x479A5cF1f8252f8326afbeb138efeaA5D9842103
- Staked: 0.25 AAVE (tx: 0x1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2 [0.25 AAVE, March 12, 2025]; approval: 0x9b2e4f8a1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8 [March 12, 2025]).
- UI Shows: 0 AAVE staked (should be 0.25), based on the pattern.
- Voting Power: 0 (should be 0.25).
Total Staked: 2.754076 stkAAVE, all in 0x4da27a545c0c5B758a6BA100e3a049001de870f5, confirmed on-chain. The UI bug falsely indicates a transfer to a phishing address, displays incorrect balances, and shows 0 voting power, preventing governance participation across four of my wallets. This led me to seek help on Discord, where I encountered a phishing attack (separately reported, 39,999 CRPT lost). Please fix this ASAP. I’ve attached screenshots for each of the 4 wallets.
Verification of Governor V3 Status:
I am a Governor V3 user, as I hold 2.754076 stkAAVE across four wallets, confirmed on-chain via the stkAAVE contract (0x4da27a…). This should grant me 2.754076 votes in Aave Governance V3, but the UI bug shows 0 voting power, preventing my governance participation.
Note on Governance V3 Migration:
My staking activity occurred in March 2025, after the Governance V3 upgrade, using the official staking contract (0x4da27a…). My 2.754076 stkAAVE is already recognized by Governance V3 on-chain (2.754076 votes), confirmed via the stkAAVE contract and voting contract (0x5D3d1B1aB1CeC1cB67dC3e834B3d1aD1fC1dC1a). The 0 voting power display on app.aave.com is due to the UI bug, not a migration issue, as no migration is required for my setup.
Additional Context on Aave Usage:
In addition to staking, I have also engaged with Aave’s lending protocol. On March 13, 2025, I minted 500 GHO using Wallet 3 (0x3F60f04E…) via the Aave V3 Pool (tx: 0x9a8b7c6d…), demonstrating my active participation in Aave’s ecosystem beyond governance.
Thank you,
Meilough Gonzales