Vaults (Actions)
Vault deposit/withdraw (ERC-4626 + ERC-7540/7575/HyperCore) and the LST, savings, and GMX action builders
Vault deposit
The **single deposit entry point** for every share-token vault. The protocol, interface, and underlying are resolved from the `vault` (share token), so a deposit needs only `vault` + `amount` + `operator`.
Vault withdraw
Build calldata for an ERC-4626 vault withdraw. When the user wants the underlying back (no native unwrap), the dispatcher calls `vault.withdraw` / `vault.redeem` directly with no approval needed. When the receiver wants native ETH, falls back to the composer (unwraps WETH).
Vault withdraw (with caller-supplied share balance)
POST variant for `isAll=true` when the worker can't read the operator's share balance against its own RPC — fork tests, custom RPCs, sandbox endpoints. Same query params as GET; the body supplies the balance.
LST / LRT mint · withdraw-request · claim · cancel
Build calldata for **LST / LRT** (and Lagoon) actions — mint, withdraw-request, claim, and cancel — via the unified LST dispatchers. The protocol is resolved from the calldata-sdk registry by `(chainId, shareToken)`, or forced with `kind=` (required for Lagoon — `kind=lagoon&mode=sync|async` — and any unregistered vault).
Savings-vault request-withdraw · claim · deposit · cancel
Build calldata for **savings-vault** exits — the cooldown / async-redeem mechanics that plain ERC-4626 `withdraw` can't express (Ethena `sUSDe`, `erc7540` async vaults, instant `erc4626` redeem, and Native Credit Pool `wNLP`) — plus the deposit leg for the one family that isn't ERC-4626. The protocol is resolved from the calldata-sdk savings registry by `(chainId, shareToken)`, or forced with `kind=ethena|erc7540|erc4626|native-wnlp`.
GMX V2 GM / GLV deposit · withdraw · cancel
Build calldata for **GMX V2** GM-market / GLV liquidity actions (Arbitrum `42161`, Avalanche `43114`). These are **async**: each call returns a single `ExchangeRouter` (GM) / `GlvRouter` (GLV) `multicall` transaction (plus any ERC-20 approval to the GMX Router), and a **keeper** executes the request a few seconds later. The deposit/withdraw tx must carry a native `executionFee` (the keeper's gas reimbursement) — GMX reverts if it's underpaid.