Reduce Reserve Factor on wstETH

The proposal description details a specific, well-scoped change: reducing the wstETH reserve factor to 5% across seven networks (Ethereum, Polygon, Optimism, Arbitrum, Base, Gnosis, Scroll), consistent with the BGD Labs implementation pattern referenced in the linked GitHub sources for each network. However, the only decoded on-chain action provided is a single call to execute() (decoded as a generic fallback function) on one contract on Ethereum mainnet. This is typical of Aave's cross-chain governance pattern, where a payload contract deployed on L1 encapsulates parameter-setting logic and/or triggers cross-chain messages to update reserve factors on other networks via the CrossChainController. Because the decoded action does not expose any of the underlying function calls, target reserve addresses, or numeric parameters (e.g., the specific 5% = 5e16 value), it is not possible to directly verify from the calldata that the reserve factor is being set to 5% on wstETH, nor that all seven networks are actually updated. There is no evidence of a mismatch — nothing in the calldata contradicts the description — but the calldata's opacity (single execute() call with no decoded arguments) means a rigorous line-by-line verification against the prose is not feasible. Given the absence of any contradicting signal and the well-established pattern this proposal follows, I did not flag any discrepancies, but confidence is marked low since the calldata alone cannot substantiate the specific claims made in the description.