KVORUM
aaveSource: Aave governance v3 · #361

Horizon RWA Instance Activation

executedAug 26, 2025, 06:35 PM UTCby660x66a2…73ff

01Summary

AISummary by Kvorumclaude-haiku-4-5

Activate the Horizon RWA instance by unpausing the pool, setting emission admins for stablecoins (GHO, RLUSD, USDC) and RWA tokens (USTB, USCC, USYC, JAAA, JTRSY), enabling GHO minting through a direct minter with 1M GHO bucket capacity, and seeding 1M GHO liquidity into the protocol.

Type
protocol addition
Funding
$1000000

Key changes

  • Unpause Horizon Pool to enable deposits and borrows(high)
  • Set emission admins for stablecoins (GHO, RLUSD, USDC) and their aTokens to enable reward configuration(high)
  • Set emission admins for RWA tokens (USTB, USCC, USYC, JAAA, JTRSY) to configure liquidity mining programs(high)
  • Grant RISK_ADMIN_ROLE to GHO_DIRECT_MINTER(medium)
  • Register GHO_DIRECT_MINTER as facilitator with 1M GHO bucket capacity(high)
  • Register GHO_DIRECT_MINTER as controlled facilitator on GHO_BUCKET_STEWARD(medium)
  • Seed 1M GHO liquidity into the protocol(high)

Notable concerns

  • Pool was previously paused and uninitialized with reward configurations, indicating this is completing a deployment process
  • GHO minting capability is being granted to a new direct minter contract in the Horizon instance
Contracts0x83Cb1B4af26EEf6463aC20AFbAC9c0e2E017202F0x53519c32f73fE1797d10210c4950fFeBa3b215040xEFD5df7b87d2dCe6DD454b4240b3e0A4db5623210xC2201708289b2C6A1d461A227A7E5ee3e7fE9A2F0x40D16FC0246aD3160Ccc09B8D0D3A2cD28aE6C2f0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB480x43415eB6ff9DB7E26A15b704e7A3eDCe97d31C4e0x14d60E7FDC0D71d8611742720E4C50E7a974020c0x136471a34f6ef19fE571EFFC1CA711fdb8E49f2b0x8c213ee79581Ff4984583C6a801e5263418C4b860x5a0F93D040De44e78F251b03c43be9CF317Dcf640xe10C78A3AC7f016eD2DE1A89c5479b1039EAB9eA
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

393 words

Simple Summary

Proposal to activate the Horizon RWA instance, a friendly fork which launches a white label instance of the Aave Protocol, enabling the Aave DAO to capture new revenue from RWAs.

Motivation

Horizon’s RWA instance on Ethereum is deployed but currently the pool is paused, rewards and its admin roles are unset for the onboarded tokens, and GHO cannot be minted via a Horizon facilitator. This AIP activates the instance so integrators and users can begin interacting with the pool.

Concretely, the proposal:

  1. Unpauses the deployed Horizon Pool so deposits/borrows can proceed.
  2. Assigns the Horizon Emission Admin to all supported assets (and their aTokens where applicable) so incentives can be configured and adjusted via EmissionManager without further governance actions.
  3. Enables GHO utility within the instance by granting the direct minter the RISK_ADMIN role, registering it as a facilitator with a 1M GHO bucket capacity, and registering this new direct minter as a controlled facilitator on the existing Gho Bucket Steward.
  4. Seeds 1M GHO liquidity into the protocol as defined in the ARFC through GhoDirectMinter.

These steps finalize the operational setup for the Horizon instance.

Specification

This proposal executes the following actions:

  • Unpause the Pool

    • Call IPoolConfigurator.setPoolPause(false)
    • Enables all standard pool operations per current reserve configurations.

  • Set Emission Admins

    • For stablecoins (GHO, RLUSD, USDC):
      • Fetch aToken via IPoolDataProvider.getReserveTokensAddresses(token)
      • Set emission admin for both the underlying token and its aToken to EMISSION_ADMIN using IEmissionManager.setEmissionAdmin.
    • For RWA tokens (USTB, USCC, USYC, JAAA, JTRSY):
      • Set emission admin for each token to EMISSION_ADMIN using IEmissionManager.setEmissionAdmin.
      • Configures and updates liquidity mining / rewards programs across assets.

  • Enable GHO Facilitator

    • Grant RISK_ADMIN_ROLE to GHO_DIRECT_MINTER via IACLManager.grantRole.
    • Register facilitator: IGhoToken.addFacilitator(GHO_DIRECT_MINTER, "HorizonGhoDirectMinter", 1M GHO).
    • Set GHO_DIRECT_MINTER as a controlled facilitator on GHO_BUCKET_STEWARD.

  • Seed GHO Liquidity

    • Supply 1M GHO through GHO_DIRECT_MINTER.mintAndSupply

References

  • Horizon addresses

    • POOL_CONFIGURATOR: 0x83Cb1B4af26EEf6463aC20AFbAC9c0e2E017202F
    • PROTOCOL_DATA_PROVIDER: 0x53519c32f73fE1797d10210c4950fFeBa3b21504
    • ACL_MANAGER: 0xEFD5df7b87d2dCe6DD454b4240b3e0A4db562321
    • EMISSION_MANAGER: 0xC2201708289b2C6A1d461A227A7E5ee3e7fE9A2F
    • EMISSION_ADMIN: 0xac140648435d03f784879cd789130F22Ef588Fcd

  • Tokens

    • Stablecoins:

      • GHO: 0x40D16FC0246aD3160Ccc09B8D0D3A2cD28aE6C2f
      • RLUSD: 0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD
      • USDC: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

    • RWA:

      • USTB: 0x43415eB6ff9DB7E26A15b704e7A3eDCe97d31C4e
      • USCC: 0x14d60E7FDC0D71d8611742720E4C50E7a974020c
      • USYC: 0x136471a34f6ef19fE571EFFC1CA711fdb8E49f2b
      • JTRSY: 0x8c213ee79581Ff4984583C6a801e5263418C4b86
      • JAAA: 0x5a0F93D040De44e78F251b03c43be9CF317Dcf64

  • GHO Roles

    • GHO_DIRECT_MINTER: 0xe10C78A3AC7f016eD2DE1A89c5479b1039EAB9eA
    • BUCKET_CAPACITY: 1_000_000e18

  • Implementation: AaveV3Ethereum

  • Tests: AaveV3Ethereum

  • Snapshot

  • Discussion

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal description lists several concrete, detailed sub-actions (unpausing the pool, setting emission admins for multiple tokens, granting RISK_ADMIN_ROLE, registering a GHO facilitator, and seeding GHO liquidity). However, the decoded on-chain calldata contains only a single top-level action: a call to execute() on a payload contract address, decoded generically as fallback(). This is the standard pattern used by Aave governance proposals, where the DAO's governor calls execute() on a purpose-built payload contract, and the actual granular logic (the steps described in the prose) lives inside that payload contract's bytecode rather than being individually encoded as separate governor-level actions. Because only this wrapper call is visible in the decoded actions, there is no way to directly verify each individual claim (pool pause state, emission admin addresses, GHO bucket capacity, etc.) against on-chain calldata at this level of decoding. I found no explicit contradiction between the description and the single decoded action — the target address is consistent with an Aave payload deployment, and the call type (execute) matches the expected governance execution pattern. However, since the specific numeric values, target addresses for sub-calls, and role grants referenced in the description cannot be cross-checked against decoded arguments, my confidence in this assessment is low. No discrepancy is flagged because there is no conflicting information, only insufficient decoded detail to fully confirm alignment.

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0fallback()chain 0x1
Target
0x2082…74dd
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.