Aave's deployment on the Harmony
Snapshot to deploy V2 on Harmony passed with a success. In anticipation of the Aave Protocol V3 launch, the Aave Protocol v2 deployment on Harmony was dropped in favour of the Aave Protocol V3 deployment.
Due to the Horizon bridge exploit, certain assets on the Harmony network are not at parity with Ethereum, which affects the Aave V3 Harmony market. Per the community, the Harmony market has been frozen.
Aave team do not hold any keys to the multisig controlling Aave V3 markets on Harmony
During an initial bootstrapping phase, the Harmony deployment is controlled by a multisig (keys held by Harmony community) and follows the same security practices implemented during the governance transition period for Aave V1 and V2.