GHO CCIP Integration Maintenance (CCIP v1.5 upgrade)
01Summary
Proposal to upgrade GHO CCIP Token Pools to ensure compatibility with Chainlink's CCIP 1.5 protocol launching in Q4 2024. Updates include configuring an intermediary contract to translate between protocol versions, upgrading existing token pools, and setting a temporary rate limit of 300,000 GHO capacity with 60 GHO/second refill for Ethereum-Arbitrum lanes.
- Type
- protocol addition
Key changes
- Configure intermediary contract to translate execution calls between CCIP 1.4 and 1.5 OnRamps and OffRamps(high)
- Upgrade existing GHO Token Pools to accept calls from both old and new CCIP protocol versions through intermediary contract(high)
- Establish token rate limit of 300,000 GHO capacity and 60 GHO per second refill rate for both directions on Ethereum-Arbitrum lane(medium)
Notable concerns
- Rate limit is temporary security measure and may need adjustment as CCIP 1.5 matures
- Aave Labs provides technical support for maintaining pool functionality post-upgrade
Generated by Kvorum
02Description
Simple Summary
Proposal to update GHO CCIP Token Pools to ensure GHO’s CCIP integration remains functional during and after the upcoming migration to CCIP version 1.5.
Motivation
The Chainlink Cross-Chain Interoperability Protocol (CCIP) is upgrading to version 1.5 in Q4 2024, introducing several new features and enhancements. We are expecting that a detailed description of this new version will be announced by Chainlink soon. Currently, GHO CCIP Token Pools are based on version 1.4, and they are not compatible in their current form with CCIP 1.5. The Chainlink CCIP team cannot migrate the GHO CCIP Token Pools as part of the system-wide upgrade, as these are fully controlled by the Aave DAO. Aave Labs will provide technical support to ensure that GHO CCIP Token Pools remain functional, secure, and aligned with the latest updates, enabling GHO to expand to other networks if needed.
Specification
Below actions are taken in order to make GHO token pools work with the new CCIP 1.5 protocol by allowing the "Intermediary Contract" (proxyPool) to translate the interface between 1.4 & 1.5 OnRamps and OffRamps:
- Configure an Intermediary Contract: This contract translates execution calls between the new OnRamp and the existing GHO Token Pools. It was developed and deployed by the Chainlink CCIP team on behalf of the Aave DAO.
- Upgrade the Existing GHO Token Pools: The existing Token Pools are adjusted to allow calls from both the old and new versions of the OnRamp and OffRamp, through the intermediary contract.
- Setup a Token Rate Limit: A token rate limit of 300,000 GHO as limit capacity and 60 GHO per second as refill rate is set for both directions of Ethereum <> Arbitrum lane. This is a temporary security measure that can be lifted later via AIP or by GHO Stewards.
References
- Implementation: AaveV3Ethereum, AaveV3Arbitrum
- Tests: AaveV3Ethereum, AaveV3Arbitrum
- Snapshot - Direct-to-AIP
- Discussion
- Token Pool Contracts - UpgradeableLockReleaseTokenPool, UpgradeableBurnMintTokenPool
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal follows Aave's standard governance pattern where a single generic execute() call is made to a dedicated payload contract that was deployed specifically for this proposal (referenced in the description's GitHub links as AaveV3Ethereum_GHOCCIP150Upgrade). This is normal practice for Aave DAO proposals: the detailed logic (configuring the intermediary contract, upgrading token pools, setting rate limits) lives inside the payload contract's code rather than being passed as decoded calldata arguments in the governance action itself. Because the decoded action only shows an opaque execute() call with no arguments, there is nothing in the calldata that contradicts the description, but there is also no way to independently verify the specific numeric values (300,000 GHO limit, 60 GHO/sec refill) or the exact configuration steps from the calldata alone. This is a common and accepted limitation of on-chain action decoding for Aave-style payload proposals, so I do not flag it as a discrepancy, but confidence is low because the decoded action doesn't provide granular detail to cross-check against the prose's specific claims. No target mismatches, value mismatches, or omissions were identifiable given the information available.'
Generated by Kvorum
04Actions
- Target
- 0x375e…18a0
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedGHO Risk Stewards Update and GHO CCIP Integration Upgrade90%
- aaveexecutedGHO update on Aave V3 Ethereum Pool78%
- aaveexecutedGHO Steward v2 Upgrade77%
- aaveexecutedGHO Facilitator Replacement75%
- aaveexecutedGHO update on Aave V3 Ethereum Pool for 13/11/2023 Report73%
- aaveexecutedActivate Gho Stewards71%
- aaveexecutedExtend GHO Steward on Aave Prime Instance70%
- aaveexecutedGho Steward Update70%
- aaveexecutedGho unpause and freezing67%
- aaveexecutedGrant Claim Helper Role to StkGhoMigrator64%