Get Started

Install WDK CLI globally:

npm install -g --allow-scripts=@tetherto/wdk-cli @tetherto/wdk-cli@1.0.0-beta.1

The current release is 1.0.0-beta.1. Beta releases can change before the stable release.

Prerequisites

• Node.js 22.18.0 or later
• npm
• Enough ETH on Ethereum mainnet to fund the new wallet and pay the example transaction fee
• A second Ethereum mainnet address you control to receive the example transfer

Verify the installation:

wdk --version
wdk --help

The package installs the wdk, wdk-mcp, and wdk-daemon binaries. Use wdk for the steps below.

1. Create A Wallet

Create a named 12-word wallet:

wdk wallet create --name quickstart --words 12

The CLI then asks for the wallet-encryption passphrase:

1. At Passphrase (empty for none):, enter a strong, unique passphrase. The input is hidden.
2. At Confirm passphrase:, enter the same passphrase again.
3. After the wallet is stored, the CLI displays the generated seed phrase once. Record it offline before continuing.

Store the seed phrase and passphrase separately. Do not put either value in a terminal command, source file, screenshot, agent transcript, or online note. The current CLI permits an empty passphrase, but an empty value provides no meaningful protection for the encrypted seed file.

If this is your first wallet, it becomes the default automatically. You do not need to change an existing default wallet because the wallet-dependent commands below select quickstart explicitly.

2. Unlock The Wallet

Unlock the wallet for five minutes:

wdk wallet unlock --name quickstart --ttl 5

At Enter passphrase of 'quickstart' wallet to unlock:, enter the wallet passphrase. The input is hidden.

The TTL starts at unlock and does not restart when you use the wallet. Unlock it again if the session expires while you complete this guide.

Set --ttl 0 to disable automatic expiry:

wdk wallet unlock --name quickstart --ttl 0

An unlimited session remains unlocked until you explicitly lock it, the daemon stops, its process fails, or the machine restarts. Any process running as the same operating-system user that can connect to the daemon can use an unlocked wallet without entering the passphrase again. Prefer a finite TTL and use --ttl 0 only in a controlled local environment.

3. Get The Ethereum Address

Derive the wallet's Ethereum mainnet address:

wdk get address --network ethereum --wallet quickstart

Copy the returned address and verify every character before using it as the funding destination.

4. Fund The Wallet

From another wallet or exchange you trust:

1. Select Ethereum mainnet.
2. Paste the address from step 3 as the destination.
3. Send more than 0.0001 ETH so the new wallet can send 0.0001 ETH and pay the Ethereum gas fee in step 6.
4. Account for any separate withdrawal or network fee charged by the sending wallet or exchange.
5. Verify the network, destination, and amount, then submit the transfer.

Wait for the funding transaction to confirm before checking the balance. The five-minute session may expire while you wait.

5. Check The Balance

Read the wallet's native Ethereum balance:

wdk get balance --network ethereum --wallet quickstart

If the command reports that the wallet is locked, unlock it again and repeat the balance check.

6. Send ETH

Use an Ethereum address you control as the recipient.

wdk send \
  --network ethereum \
  --to YOUR_ETHEREUM_ADDRESS \
  --amount 0.0001 \
  --wallet quickstart

The command broadcasts immediately and prints the resulting transaction identifier.

Optional: Estimate Without Broadcasting

Add --dry-run to estimate the fee and return a transaction summary without broadcasting:

wdk send \
  --network ethereum \
  --to YOUR_ETHEREUM_ADDRESS \
  --amount 0.0001 \
  --wallet quickstart \
  --dry-run

7. Lock The Wallet

End the wallet session when you finish:

wdk wallet lock --name quickstart

Lock every unlocked wallet with:

wdk wallet lock --all

Next Steps

• Manage Wallets - Import, export, rename, unlock, and delete wallets
• Manage Tokens - Inspect and extend the token registry
• Use the MCP Server - Connect an MCP-compatible AI client
• Security Model - Understand the daemon trust boundary and session trade-offs

Need Help?