Operational Checklists

These checklists summarize prerequisites and review points for Ethereum Network Lending, AAVE GHO Saving, and Hyperliquidity Provider (HLP). Execution remains subject to vault permissions, available liquidity, and external protocol conditions.

Before Opening Deposits

Item	Required
Controller proxy initialized	Yes
Vault deployed with correct asset and controller	Yes
Vault registered in Controller	Yes
Investor role granted to allowlisted depositors	Yes
Vault unpaused by Guardian	Yes
Initial marked values created through registration	Yes
Product, operational vault address, network, and current permissions confirmed against deployment records	Yes
Performance Fee of 0% distinguished from external route costs and gas; deployed fee configuration checked	Yes

Before Investing

Item	Required
Strategy asset equals vault asset	Yes
Strategy receiver equals vault	Yes
Strategy registered in Controller	Yes
Controller proxy has Keeper role on strategy if strategy enforces onlyRole(Roles.KEEPER)	Yes
Vault has enough idle assets	Yes
Strategy valuation, exit restrictions, and synchronous/asynchronous behavior reviewed	Yes

Before Async Redemption Execution

Item	Required
Async vault has pending redeem shares	Yes
Keeper role granted on async vault	Yes
Idle assets cover previewRedeem(pendingRedeemShares)	Yes
Vault is not paused and not shutdown for claims	Yes
Pending requests distinguished from executed, claimable requests	Yes
For HLP, required remote exits and asset returns confirmed rather than inferred from submitted transactions	Yes

The Ethereum vault and HyperEVM allocator have different executeRedeem operations; verify each target's deployed ABI and required parameters before use. A user request is claimable only after its Ethereum vault execution round is complete. The displayed HLP processing estimate is not a guaranteed deadline; see withdrawal timing.

Before HyperStrategy Use

Item	Required
HyperStrategy allocator set exactly once by Admin	Yes
CCTP max fee configured by Keeper if a non-zero fee is required	Yes
Controller/keeper has Keeper role on HyperStrategy depending on the call path	Yes
HyperCoreAllocator configured with source receiver domain/address	Yes
CCTP relay process available to carry invest/divest/state messages	Yes
Underlying HLP unlock status and available liquidity checked before a remote withdrawal	Yes
Resulting HyperCore state confirmed before dependent actions; an EVM receipt alone is insufficient	Yes
Remote state freshness, in-flight assets, and actual source-chain receipts reviewed before NAV confirmation	Yes

Emergency And Revocation Review

HyperStrategy.exit() and a V2 vault shutdown do not guarantee recovery of remote HLP assets. Recovery assessment must account for remote exposure, in-flight transfers, pending and executed claims, registry/accounting changes, and later receipts. Emergency redemption distributes only the applicable idle vault assets; expiry of the seven-day harvest protection does not prove all remaining assets are dust. See the emergency flow.