EVM Withdraw

Queue withdrawal of vault shares from DeFi protocols.

---

Overview

The EVM Withdraw action queues a withdrawal of vault shares from DeFi protocols (currently Veda vaults). Unlike immediate redemptions, withdrawals enter a queue and are processed according to the protocol's withdrawal schedule.

Flow: LBTCv (Vault Shares) → Queued Withdrawal → LBTC

Supported Chains: Ethereum, Base, BSC, Corn (production only)

Note: This action queues a withdrawal request. The protocol processes queued withdrawals on its own schedule—this is not an instant operation.

---

Queue Behavior

Important: Only one withdrawal request can be active at a time per address. Submitting a new withdrawal request replaces the existing one—amounts are updated, not added.

If you need to withdraw additional shares while a request is pending:

1. Submit a new withdrawal for the total amount desired

2. The new request replaces the previous one

3. The 14-day queue timer resets

To check for existing pending withdrawals before creating a new request, use sdk.api.vaultWithdrawals(address).

---

Basic Usage

import { createLombardSDK, Chain, Env } from '@lombard.finance/sdk';

const sdk = await createLombardSDK({
  env: Env.prod,
  providers: { evm: () => window.ethereum },
});

const withdraw = sdk.chain.evm.withdraw({
  sourceChain: Chain.ETHEREUM,
  protocol: 'veda',
  recipient: '0x1234567890abcdef1234567890abcdef12345678',
});

await withdraw.prepare({
  amount: '0.001',
});

if (withdraw.needsApproval) {
  await withdraw.approve();
}

const result = await withdraw.execute();
// result.txHash: '0x...'

---

Parameters

Withdraw Options

Parameter	Type	Required	Description
sourceChain	Chain	Yes	EVM chain where vault shares are held
protocol	DeployProtocol	Yes	DeFi protocol (currently 'veda')
recipient	string	Yes	Address to receive withdrawn assets

Prepare Parameters

Parameter	Type	Required	Description
amount	string	Yes	Amount of vault shares to withdraw

Important: Minimum withdrawal amount is 0.00010001 vault shares.

---

Status Flow

IDLE → NEEDS_APPROVAL → READY → COMPLETED
              ↓           ↓
        (approve)    (execute)

The action may skip NEEDS_APPROVAL if the withdraw queue contract already has sufficient allowance.

Status	Description
IDLE	Initial state, ready for prepare
NEEDS_APPROVAL	Vault shares require approval for withdraw queue contract
READY	Approved and ready to queue withdrawal
COMPLETED	Withdrawal successfully queued

---

Checking Approval Status

After calling prepare(), check the needsApproval property to determine the next step:

await withdraw.prepare({ amount: '0.001' });

if (withdraw.needsApproval) {
  // User must approve the withdraw queue contract
  await withdraw.approve();
}

// Now ready to execute
await withdraw.execute();

---

Events

withdraw.on('status-change', (status) => {
  // status: 'IDLE' | 'NEEDS_APPROVAL' | 'READY' | 'COMPLETED'
});

withdraw.on('progress', (progress) => {
  // progress.status: current status
  // progress.steps.approval: 'IDLE' | 'PENDING' | 'COMPLETE'
  // progress.steps.queueing: 'IDLE' | 'PENDING' | 'COMPLETE'
});

withdraw.on('completed', () => {
  // Withdrawal successfully queued
});

---

Error Handling

Common errors when withdrawing:

Error Code	Description
INSUFFICIENT_SHARES	Requested amount exceeds available vault shares
PROTOCOL_NOT_SUPPORTED	Protocol not available on the specified chain
PROVIDER_MISSING	EVM wallet provider not connected

import { LombardError, WithdrawErrorCode } from '@lombard.finance/sdk';

try {
  await withdraw.prepare({ amount: '100' });
} catch (error) {
  if (error instanceof LombardError) {
    if (error.code === WithdrawErrorCode.INSUFFICIENT_SHARES) {
      // Handle insufficient balance
    }
  }
}

---

Viewing Pending Withdrawals

To view queued withdrawals, use the vault withdrawals data API:

import { getVaultWithdrawals } from '@lombard.finance/sdk';

const withdrawals = await getVaultWithdrawals({
  address: '0x...',
  env: Env.prod,
});
// Returns pending and completed withdrawal requests