feat(defi): add Aave V3 vault deposits - #9674
Conversation
491f65c to
77c23bd
Compare
|
|
ef37c25 to
9fb23bd
Compare
a27029a to
aaf7b8d
Compare
|
@claude review |
|
Claude finished @sachinBitgo's task —— View job Code Review for Aave V3 Vault DepositsTodo List:
Overall Assessment ✅This PR successfully adds Aave V3 vault deposit support by reusing the existing ERC-4626 flow. The implementation is clean, well-tested, and follows established patterns in the codebase. Detailed Review1. Dependency Update (
|
danielpeng1
left a comment
There was a problem hiding this comment.
small merge conflict
763301f to
8ba396e
Compare
9c48520
8ba396e to
9c48520
Compare
ee8ae61
9c48520 to
ee8ae61
Compare
ee8ae61 to
0b38575
Compare
What
@bitgo/public-typesto6.69.0insdk-core, which includesVaultProtocol.AAVE_V3and its codec union.aave_v3SDK vault dispatch. Morpho and Aave V3 share the sameERC-4626 approve/deposit flow, so both dispatch to a single
depositToErc4626Vaultpath that creates the existingdefiApproveand
defiDeposittxRequest pair.DepositResultand add full/lite operation ID, missing ID, andfailure-propagation coverage.
Why
The SDK rejected Aave StataTokenV2 vaults as an unsupported protocol before
it could create deposit txRequests. Reusing the existing ERC-4626 flow lets
SDK clients deposit into Aave vaults without introducing new calldata or
wallet intent types.
Ticket: DEFI-857