Hello everyone, I am sharing my topic again, since I had shared it in Spanish and it is a forum in English, sorry for my ignorance, but I need to be able to resolve this.
I am facing a problem with an unexpected liquidation on my Aave account and I hope the community can help me understand what happened.
Context:
My initial position was configured with a health factor of 1.71, a collateral of 0.896 ETH and a debt of 1,100 USDT.
The price of the oracle for ETH at that time was $2,700 approximately (14/2)
Then, I noticed that part of my position was liquidated, although the price of ETH never fell enough to reach a critical health factor.
When I see that my health factor fell to 1.01, I added more collateral to the position, 0.35 ETH
But when checking in the morning, the same thing happened again my liquid practically the position, leaving a health factor at 1.25
Problem:
When reviewing my transactions, I noticed that there was a withdrawal of 0.42 ETH (approximately $1,146) that was not initiated by me (I understand that it is from the smart contract that executes the settlements)
Currently, my health factor is 1.25 and my collateral has decreased significantly.
I think there could have been an error in the calculation of the price of the oracle at the time of the liquidation or a failure in the logic of the smart contract that manages the settlements.
What I have tried so far:
Review the relevant transactions:
Liquidation 1: 0x620caa1e0cb6604ac14cc8e6432aee17c3da3503cfc508c1914aab42015e4e61
Liquidation 2: 0xc8ad97561614074268260124f50f3af0e8f6af3c0510f30aed96c3115a502147
Validate the current metrics in Aave and check that the price of ETH never fell enough to justify these settlements.
Doubts and help I need:
Is it possible that the price of the oracle has delivered incorrect data for a short period?
Could it be a problem with the smart settlement contract?
Has anyone else faced a similar situation and could guide me on how to proceed to get my money back?
Any suggestion, clarification or guide on how to escalate this problem to the Aave team would be more than welcome.
Below I attach screenshots, checking what happened.
