Bitcoin Wallet (BTC)

Generate and use a dedicated Bitcoin hot wallet.

# Bitcoin Wallet Skillpack

Use this tool family for wallet-like actions on Bitcoin.

## What it is

- A dedicated per-user Bitcoin hot wallet managed by Clono.
- Supports both legacy and SegWit receive addresses.
- Uses public Bitcoin APIs for UTXO, fee, and broadcast flows (balance / tx history can use a block explorer or HTTP from the address in `get_wallet`).
- Supports PSBT-based send flows and message signing.

## Core wallet operations

- `bitcoin_wallet.get_wallet`
- `bitcoin_wallet.get_wallet_insight_guide`
- `bitcoin_wallet.list_utxos`
- `bitcoin_wallet.get_fee_recommendations`
- `bitcoin_wallet.build_psbt_send`
- `bitcoin_wallet.sign_psbt`
- `bitcoin_wallet.finalize_psbt`
- `bitcoin_wallet.broadcast_transaction`
- `bitcoin_wallet.send_native`
- `bitcoin_wallet.sign_message`

## Recommended workflow

1. Use `bitcoin_wallet.get_wallet` to get the receive addresses.
2. Use `bitcoin_wallet.get_wallet_insight_guide` when the user wants wallet balance or explorer-based wallet insight.
3. Use `bitcoin_wallet.list_utxos` before building manual sends.
4. Use `bitcoin_wallet.get_fee_recommendations` if you want explicit fee control.
5. Use `bitcoin_wallet.build_psbt_send` for PSBT-based transaction construction.
6. Use `bitcoin_wallet.sign_psbt` then `bitcoin_wallet.finalize_psbt` then `bitcoin_wallet.broadcast_transaction` for manual flow.
7. Use `bitcoin_wallet.send_native` for the simple end-to-end send path.

## Important guidance

- For balance and transaction history, use `get_wallet` (addresses + `viewerUrl`) or any HTTP client against mempool.space, block explorers, etc.
- Prefer the PSBT flow when you want to inspect or control transaction construction.
- `bitcoin_wallet.send_native` is the simplest path for a direct BTC transfer.