As both #option 1 and #option 2 presented here include stETH I’d like to draw attention to the original blog post. BGD. Aave v3 Ethereum. New deployment vs Aave v2 Upgrade
- It gives the possibility for the community to reassess the risk configuration of the assets currently listed on v2. With an upgrade v2→v3, everything will remain the same as currently, that is not possible. It is important to highlight that this also allows for the listing of for example fewer Aave-custom implementations for some assets, like wstETH, instead of the current stETH version listed on v2.
stETH has some issues Account's `stETH` balance getting lower on 1 or 2 wei due to rounding down integer math · Issue #442 · lidofinance/lido-dao · GitHub which cause contracts that rely on exact precision (e.g. liquiditySwap / repayWithCollateral features) to fail. From a technical perspective, I would highly recommend to consider listing wstETH instead as it’s not affected by this balance inaccuracy. Also it would allow listing wstETH with the default a/s/v implementations.