Following the Ethereum Core activation above, the same PT Risk Oracle stack is now deployed on Aave V3 Plasma for PT-sUSDe-22OCT2026 (E-Mode categories 25 and 26). The contracts are byte-equivalent to the Certora-audited Ethereum deployment, all source-verified, and ownership follows the same model: the operational surface sits with the LlamaRisk safe, the registry is owned by the Plasma Executor from construction, and the AgentHub registration that activates the agents remains a governance action. An AIP will follow shortly.
Deployed contracts (Plasma, chainId 9745)
| Contract | Address |
|---|---|
| RiskOracle | 0x4f240E3825e7FD6D834EEb861b1539dF0b43BfD0 |
| PTParameterRegistry | 0xED34a5374FeaaD8Ead024023d2Fc3b844bb9Bb47 |
| LlamaguardRiskOracleRouter | 0xaC8690DE68dcB7068805c0C631004E9894FAFbe0 |
| LlamaGuardOracle (EMA) | 0xfA3187E63d5eEc6189702E24dEAbC82b80853809 |
| AaveDiscountRateAgent | 0x8feb86657dbBbB89B7D2D115263D6927Afeb8bd4 |
| AaveEModeAgent | 0xBcFaBC3ea806d4755ED3F1eA2C5EAE92706Beb29 |
Both agents are stock implementations from aave-dao/aave-risk-agents; the E-Mode agent is built from the current head, which carries the fix preserving the E-Mode isolation flag introduced with Aave 3.7. They are ownerless and inert until governance registers them.
Chainlink CRE workflows
Three workflows, owned by the Aave CRE organisation multisig and pinned as the only accepted author on every Router route: an hourly EMA of the Pendle implied rate, and four-hourly discount-rate and E-Mode risk-parameter oracles acting on categories 25 and 26. The EMA leg writes to its own oracle and activates without governance; the two agent-bearing routes go live only after the AIP executes.
What the AIP will do
Register the two predeployed agents on the Aave-owned AgentHub, grant them RISK_ADMIN, and set the absolute range bounds: 100 bps per injection on the discount rate with a 2-day minimum delay and expiry, and 50 bps per injection on E-Mode LTV, liquidation threshold and liquidation bonus with 3-day delays and expiry. The Router independently enforces a 48-hour minimum delay on the discount route, so that value is rate-limited twice. Governance retains a per-agent kill switch through the protocol guardian, and the payload changes no reserve configuration.
Ownership and controls
Registration is governance-only: registerAgent and setAgentAdmin on the AgentHub are owner-gated, and the owner is the Aave Plasma executor, so no agent can be added or repointed outside a governance vote. The Protocol Guardian is registered as each agent’s admin and can disable a misbehaving agent without waiting on a governance cycle; re-enabling requires a vote. The Router follows the same shape: the Guardian can pause, and unpausing is owner-only.
The publishing path is one-way. The RiskOracle accepts writes only from the Router, and the Router accepts only reports delivered by the Chainlink forwarder for a workflow whose owner and name match a registered route. The Router and RiskOracle are owned by the LlamaRisk operations safe, the PTParameterRegistry is owned by the Plasma executor from construction with the safe as updater, and no LlamaRisk individual holds governance-level permissions. The permissions-book update covering these assignments is open for review.
Auditing
The Router, RiskOracle, parameter registry and EMA oracle are byte-equivalent deployments of the Certora-audited LlamaGuard periphery running on Ethereum Core. The agent implementations are the stock contracts from the DAO-owned aave-dao/aave-risk-agents, audited by Certora; the E-Mode agent is built from the current head, which preserves the E-Mode isolation flag introduced with Aave 3.7.