We have created an on-chain AIP for this proposal.
Voting will start in approximately 24 hours, participate
We have created an on-chain AIP for this proposal.
Voting will start in approximately 24 hours, participate
Proposal to re-enable Aave Proof of Reserve on Avalanche, after temporarily halting the system during the Aave v3.1 upgrade.
With the release of Aave V3.1, it is no longer necessary to set the asset’s LTV to zero before freezing during the execution of an emergency action on a Proof of Reserve alert, as the protocol does both actions in batch.
Moreover, setting LTV to zero that way would break the “rollback” mechanism (pendingLtv
) of LTV back to normal value on unfreeze.
The proposal is separated into two payloads because multiple blocks must pass between canceling the existing Aave Robot automation and withdrawing funds from it. The order of execution is guaranteed by the fact that it is impossible to withdraw funds before the robot is canceled.
The two payloads do the following:
cancel()
on the Aave Robot operator contract.RISK_ADMIN
role to the new PoR executor contract, by calling addRiskAdmin()
on the ACLManager contract.withdrawLink()
on the Robot operator contract.register()
on the Robot operator contract.The new contracts involved are the following:
Contract | Address |
---|---|
Proof Of Reserve Executor V3.1 | 0xB94e515615c244Ab25f7A6e592e3Cb7EE31E99F4 |
Proof Of Reserve Robot | 0x7aE2930B50CFEbc99FE6DB16CE5B9C7D8d09332C |
We have created an on-chain AIP for this proposal.
Voting will start in approximately 24 hours, participate
We have created an on-chain AIP for this proposal.
Voting will start in approximately 24 hours, participate