Onboard Strata srUSDe PT tokens to V3 Core Instance

The proposal follows the standard Aave V3 governance pattern: the on-chain action is a single delegatecall-style execute() to a pre-deployed and audited payload contract (0xc5d3...b75b8), which is the norm for Aave AIPs. All the granular specifics described in the prose (supply/borrow caps, LTV/LT, reserve factor, IR curve, oracle wiring, e-mode categories, emission admin assignment) are expected to be implemented inside that payload's execute() logic, not as separately decoded calldata actions visible here. Because the decoded action set only exposes the top-level execute() call and not the internal Aave Pool/PoolConfigurator calls the payload will make, there is no way to directly verify each numeric parameter or address claim in the description against the calldata provided. This is a routine, expected structure for Aave proposals (referencing the linked Solidity implementation and tests confirms the standard workflow), so it is not treated as a red flag. However, since the calldata itself is opaque at this level of decoding, confidence in a granular comparison is low, and no discrepancies can be substantiated from the data available — the single action is consistent with what the description implies (a governance-approved listing payload being executed).},