Gho Mantle Activation
01Summary
Deploy GHO stablecoin on Mantle blockchain to leverage Bybit's 30 million active users and expand GHO adoption. Includes configuring Chainlink CCIP lanes, GhoCcipSteward, and GhoBucketSteward with rate limits of 1.5M GHO capacity and 300 GHO per second.
- Type
- protocol addition
Key changes
- Deploy GHO token and infrastructure on Mantle blockchain(high)
- Configure Chainlink CCIP lanes between Mantle and existing GHO chains with 1.5M GHO capacity and 300 GHO per second rate limit(high)
- Configure GhoCcipSteward for cross-chain message handling(medium)
- Configure GhoBucketSteward for bucket management on Mantle(medium)
Notable concerns
- GHO peg stability historically at maximum 20 basis points displacement on Ethereum suggests execution risk on new chain
- Rate limiting parameters (1.5M capacity, 300/second) require monitoring for adequacy on Mantle
- Integration with Bybit ecosystem success depends on external partnerships and adoption
Generated by Kvorum
02Description
Simple Summary
This AIP proposes deploying GHO on the Mantle blockchain. By deploying on Mantle, Aave can take advantage of Mantle’s integration with Bybit products, enabling seamless access to Bybit’s 30 million active users. This creates a significant opportunity to broaden GHO's user base and make the stablecoin more accessible to a wider audience.
Motivation
Considering the substantial amount of lending activity projected for the instance, the strategic placement of GHO in the list of initial assets paves the way to broader expansion and adoption of the stablecoin.
GHO’s price performance has been strong on the Ethereum network, as empirically observed pricing data extracted from the GHO/USDC Uniswap v3 pool indicates high peg stability, with maximum dislocations of only 20 basis points compared to its anchor price of $1.
Specification
This AIP includes a series of actions required to launch GHO on Mantle:
- Configure new Chainlink CCIP lanes between Mantle and the chains where GHO is launched with a rate limit of 1.5M GHO capacity and 300 GHO per second rate.
- Configure GhoCcipSteward.
- Configure GhoBucketSteward
The table below lists the address of the new Mantle deployments
| Contract | Address |
|---|---|
| GhoToken | 0xfc421aD3C883Bf9E7C4f42dE845C4e4405799e73 |
| GhoTokenPool | 0xDe6539018B095353A40753Dc54C91C68c9487D4E |
| GhoBucketSteward | 0x2Ce400703dAcc37b7edFA99D228b8E70a4d3831B |
| GhoCcipSteward | 0x20fd5f3FCac8883a3A0A2bBcD658A2d2c6EFa6B6 |
| GhoAavecoreSteward | 0xA5Ba213867E175A182a5dd6A9193C6158738105A |
References
- Implementation: AaveV3Mantle
- Tests: AaveV3Mantle
- Snapshot
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The decoded calldata contains only one action: a generic execute() call to an executor/payload contract on mainnet. This matches the standard Aave governance proposal pattern, where the actual granular logic (CCIP lane configuration, steward configuration, contract deployments on Mantle) is implemented inside the linked Solidity payload contract (referenced in the 'Implementation' link) that gets delegatecalled by this execute() trigger. Because the calldata does not expose the internal parameters (rate limits, addresses, steward configs) in a decodable way, it is not possible to directly verify specific numeric values (1.5M GHO capacity, 300 GHO/sec) or contract addresses against the decoded action. However, there is no evidence of contradiction, extra hidden actions, or target mismatch based on what is decodable — the single action targets the expected governance executor contract on Ethereum mainnet, consistent with an Aave cross-chain deployment proposal. Given the opacity of the single execute() call, confidence in a full line-by-line comparison is low, but nothing in the available data suggests a discrepancy between the stated intent and the executed action pattern.
Generated by Kvorum
04Actions
- Target
- 0x49e6…ec38
- 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 X-Layer Activation86%
- aaveexecutedGHO Gnosis Launch85%
- aaveexecutedGHO Avalanche Launch84%
- aaveexecutedGHO Mainnet Launch83%
- aaveexecutedGho Plasma Launch83%
- aaveexecutedCreate Allowance GHO Mantle83%
- aaveexecutedGHO Base Launch83%
- aaveexecutedDeploy 10M GHO into Aave v3 Lido Instance82%
- aaveexecutedGHO Ink Launch79%
- aaveexecutedGHO Cross-Chain - Part 179%