We are grateful to @bgdlabs for their review of the code and their efforts to review the proposed GHO cross-chain system for alignment with other technical areas of the Aave Protocol. We concur with the findings and points addressed in the review and would like to offer some insights regarding some of the issues raised.
Firstly, a new section dedicated to the GHO cross-chain implementation is being developed to be included in the GHO docs. The purpose is to include a guide to developers, covering a range of topics including governance updates, bridge limits, and emergency procedures for a comprehensive understanding of the system.
Secondly, in relation to the GHO integration with the Chainlink Cross-Chain Interoperability Protocol (CCIP), a limit mechanism on Ethereum is included as a first step solution to limit compromising the user experience. Nevertheless, the DAO and the CCIP team should consider having the ability to rollback operations for token transfers. We recommend that the CCIP team prioritizes the support for this feature, allowing GHO to fully leverage it.
We wish to share information about the input received from the CCIP team during the process. We also invite the CCIP team to contribute with further details:
- Proof-of-Reserves Oracle: Considering the design and model of cross-chain GHO, setting up an oracle to monitor and verify the backing of GHO’s remote liquidity is feasible. This oracle would not only enhance the security of the Aave Protocol by guarding against potential bridge-related attacks but would also foster collaboration with other protocols. Implementing such an oracle would offer an added layer of security for protocols integrating GHO on remote chains.
- GHO as a CCIP Fee Token: Facilitating the use of GHO as a universal fee token across chains is crucial for its adoption as a payment currency. We request that the CCIP team reconsider integrating GHO as an acceptable fee token. This would eliminate the need for users to hold other assets for bridging GHO across chains, streamlining transactions and enhancing user experience.
We are actively engaged in discussions with the CCIP team to explore ideas that could improve the system’s utility, security, and user experience.
The AIP will be submitted, following the implementation of all recommended fixes from the reviews conducted by BGD Labs and Cetora. We want to express our gratitude once again for their diligent efforts in reviewing the proposal by the community and DAO service providers.
If the vote is successful, GHO cross-chain functionality will be enabled from the Aave DAO perspective. However, further configuration will be required on the CCIP side to activate the Ethereum-Arbitrum lane, which is expected to take some additional time for the system to be operational.
Updates on the progress will be shared here. Please stay tuned for updates, GHO is on its way to going live cross-chain.