validate_closed_deposit_request_with_guard
Documentation for eth_defi.vault.deposit_redeem.validate_closed_deposit_request_with_guard function.
- validate_closed_deposit_request_with_guard(request, closure, guard, asset_manager)
Validate manager-generated closed-deposit calls through GuardV0.
The request must come from
VaultDepositManager.create_deposit_request_for_guard_validation()after a typed closure preflight. Each manager-generated call is encoded and passed separately to the supplied GuardV0-compatible contract using a static call. The helper neither creates an ERC-20 approval nor broadcasts a transaction, so it cannot establish approval ordering or prove that the closed vault would accept a deposit.- Parameters
request (eth_defi.vault.deposit_redeem.DepositRequest) – Validation-only deposit request generated by the selected manager.
closure (eth_defi.vault.deposit_redeem.VaultFlowUnavailable) – Original typed deposit closure which authorised this diagnostic path.
guard (web3.contract.contract.Contract) – Configured GuardV0-compatible contract exposing
validateCall().asset_manager (eth_typing.evm.HexAddress) – Non-governance delegated asset-manager address to validate as.
- Returns
Closure context plus every independently GuardV0-accepted target and selector, suitable for a consumer’s persisted outcome evidence.
- Raises
ValueError – If
closureis not a matching typed closed or paused deposit result.- Return type