Bitcoin Wallet

Bitcoin Wallet

AgentLayer uses a separate local Bitcoin runtime built on Tether WDK.

The Bitcoin path stays deliberately isolated from the Solana and EVM signers.

Current model

The BTC backend is built around:

• encrypted local vault storage
• localhost-only service access
• host-managed password entry
• local bearer-token auth between trusted components
• seed phrase recovery kept outside the normal agent path

Current BTC functionality

The active BTC tool surface is intentionally small:

• get_wallet_capabilities
• get_wallet_address
• get_wallet_balance
• get_btc_transfer_history
• get_btc_fee_rates
• get_btc_max_spendable
• transfer_btc

This gives the agent enough coverage for:

• inspecting the connected BTC wallet
• reading transaction history
• estimating spendable amounts and fees
• preparing and sending BTC transfers with approval

Safety boundary

BTC transfers follow the same approval pattern as the rest of the wallet stack:

1. preview
2. prepare
3. execute

The user still owns:

• the wallet password
• any recovery flow
• final approval for sending funds