Ernesto Boado

Agree with you @KyleJKistner on the of "liquidation power" (throughput of the liquidation mechanism against the liquidated amounts) as the most basic measurement of liquidity risk, but don't you think...

How is the gas impact of this @miguelmtzinf ?

To recap on what is included here: 1. Return unbacked amount https://github.com/aave/aave-v3-core/pull/683 2. Improvement of CEI, reducing reentrancy risk (even for not covered ERC777) https://github.com/aave/aave-v3-core/pull/704 3. Add config param for...

@The-3D here the cached version `distributionEnd` could be used https://github.com/aave/aave-stake-v2/pull/2/files#diff-d9f8f77b0c4f836543043624fa2db9c3f5d0ea8c788cf8f6563f7331ab300601R36

Could we be more explicit somehow to show that it is an example?

## Gas report diff As expected, slight increase on average in single actions (~200 gas), with the benefit appearing on multiple actions in the same timestamp, same block. **Before fix**...

## Gas report diff As expected, there is a slight increase in gas on the most common actions, mainly because of the added condition to skip updates whenever the timestamp...

## Gas report diff As expected, slight increase on average in single actions (~1k gas), with the benefit appearing on multiple actions in the same timestamp, same block. **Before fix**...

+1 on this, would really improve the developers' experience of interacting with Safe, without going out of Solidity code, which is a quite typical use case. Regarding the API, maybe...

Something important to have is the possibility of creating the Safe tx with DELEGATE_CALL (1) `operation` type when communicating with the Safe tx Service (params [here](https://docs.gnosis-safe.io/tutorials/tutorial_tx_service_initiate_sign#fields-required-for-a-safe-transaction)). Basically to indicate that...