Stake ETH and manage stETH/wstETH positions via Lido. Use when an agent needs to stake, wrap, unwrap, withdraw, or inspect Lido balances, rewards, and queue state.
ETH staking and liquid staking token management via Lido.
lido balancelido balance --wallet 0xYourAddress
Returns ETH, stETH, wstETH, and exchange-rate-aware totals.
lido statslido stats
Returns protocol-level staking and withdrawal queue stats.
lido rewardslido rewards --wallet 0xYourAddress
Returns protocol reward context and, optionally, a wallet-level position summary.
lido stakelido stake --amount 1.0 --wallet 0xYourAddress
Builds an unsigned staking transaction:
{ "to": "0x...", "data": "0x...", "value": "1000000000000000000", "chainId": 1 }
Optional:
--referral <address>lido wraplido wrap --amount 1.0 --wallet 0xYourAddress
Builds the wrap tx. If stETH approval may be needed, use:
lido wrap --amount 1.0 --wallet 0xYourAddress --with-approval
That returns an approval tx followed by the wrap tx.
lido unwraplido unwrap --amount 1.0 --wallet 0xYourAddress
Builds the unwrap tx.
lido withdrawlido withdraw status --wallet 0xYourAddress
lido withdraw request --amount 1.0 --wallet 0xYourAddress
Builds an unsigned tx for entering the withdrawal queue.
Write-oriented commands return unsigned EVM tx JSON:
{ "to": "0x...", "data": "0x...", "value": "0", "chainId": 1 }
These should be signed and broadcast by a signer backend.
If you want to use OWS, do the conversion in a skill/workflow layer rather than expecting the child CLI to emit OWS-specific payloads:
{ to, data, value, chainId, from? }nonce, gas, maxFeePerGas, and maxPriorityFeePerGasows sign tx or ows sign send-txReference:
lido mcp
Representative tools include:
lido_balancelido_statslido_rewardslido_stakelido_wraplido_unwraplido_withdrawal_statuslido_withdraw_requeststETH rebaseswstETH is non-rebasing and better for DeFi composition