LBTC and eBTC Price Feeds Update

The proposal follows Aave's standard governance execution pattern: the on-chain action is a single execute() call into a dedicated payload contract (0x399d...086ac) rather than individually decoded parameter-setting calls. Because the payload's internal logic (oracle addresses, ratio providers, growth caps) is not exposed in the decoded_arguments, I cannot directly verify the specific numeric parameters (e.g., 2.00%/1.90% maxYearlyRatioGrowthPercent, oracle addresses) claimed in the description against on-chain state — this is typical for BGD/Aave payload proposals where implementation detail lives in verified, linked source code (referenced in the proposal) rather than in the top-level calldata. I also note the description covers both an Ethereum mainnet payload and a Base payload, but only one action (mainnet) appears in the decoded actions list; this is common when cross-chain execution is bundled inside the mainnet payload's cross-chain controller call, so it is not treated as a discrepancy absent evidence of omission. Given the opacity of the single execute() call, I found no evidence of a mismatch, but also cannot fully confirm parameter-level accuracy, so confidence is set to low rather than flagging unconfirmed concerns as high-severity issues.