Gho Base Launch

[DhairyaSethi]

Goal

https://governance.aave.com/t/arfc-launch-gho-on-base-set-aci-as-emissions-manager-for-rewards/19338

This AIP aims to expand GHO token to base using CCIP, through lanes between existing ETH & ARB chains. It also aims to list GHO as a borrowable asset on Aave V3 Base.
The AIP includes two proposals for base (launch, listing), to be executed separately (hence two payloads are generated for base) since GHO will be bridged to Executor on Base after launch to initiate listing.

Launch Steps:

• ARB:
  • Configure new BASE lane (while retaining existing ETH lane) with rate limit (300k capacity, 60 rate; same as ETH).
  • Update ProxyAdmin of GHO token to oz 5.1 style ProxyAdmin.
• ETH: Configure new BASE lane (while retaining existing ARB lane) with rate limit (300k capacity, 60 rate; same as ARB).
• BASE:
  • Configure new ETH & ARB lanes with rate limit (300k capacity, 60 rate).
  • Configure all stewards.

Listing Steps:

• BASE:
  • List GHO on V3, with system configurations as specified in the ARFC, and supply + burn an initial seed amount (1 GHO).
  • Set ACI multisig as Emissions Manager for rewards (as specified in the ARFC).

Notes

• after launch payload is executed (and base lane is active), seed amount will be bridged to the executor such that listing payload can be run. it is expected aave robot will only initiate execution of the listing payload when it simulates successful execution.
• proposal 236 is a pre-requisite to this proposal.
• base token is now predeployed and initialized with executor as owner.
• all new proxies (for token pool and base gho token) are OZ v5.1