aave-umbrella: initialize() likely exceeds per-transaction complexity

[eugypalu]

Summary

While porting Aave Umbrella to PolkaVM, I observed that some contracts consistently revert during their initialize() calls — most notably RewardsController and Umbrella.

---

Observations

These contracts follow the typical OpenZeppelin upgradeable pattern and include, within a single initialize() call:

• AccessControl role setup
• EIP712 domain separator computation
• multiple _grantRole() operations
• initialization of inherited modules with storage writes

On PolkaVM, these calls revert, whereas the exact same logic works on EVM. Through bisecting and simplification, it seems that the failure correlates with the combined complexity or weight of the initializer, rather than any specific component.

---

Workaround

Splitting the initialization logic across multiple smaller functions (e.g. initializeStep1(), initializeStep2(), …) appears to avoid the issue — allowing the contracts to initialize successfully and pass tests on PolkaVM.

---

[pgherveou]

can you add repro steps? might be related to the contract size exceeding the limit in pvm