# Liquid Accounting & Multi-Descriptor Wallets | v1.0.0-beta.14

> Clams v1.0.0-beta.14: Liquid accounting arrives with peg bridges and issued assets, plus multi-descriptor wallet families and a new chain-sources command.

Published 2026-06-16 at https://clams.tech/blog/release-v1-0-0-beta-14/

**TL;DR:** [Liquid accounting](/blog/aqua-wallet-bitcoin-liquid-accounting-setup-guide/) is now available to everyone. This release also adds multi-descriptor wallet families, a new `clams chain-sources` command, and backend-level streaming sync for Bitcoin connections.

## Liquid Support

Clams now accounts for the [Liquid network](/features/#liquid). Sync a Liquid wallet from its descriptor over Esplora or Electrum, and Clams books on-chain L-BTC, peg movements, and issued assets into the same double-entry journal as your Bitcoin.

Peg-ins and peg-outs settle on two different networks but represent one movement, so Clams reconciles them as a peg bridge: a peg-out isn't booked as a Bitcoin disposal, and a peg-in isn't booked as a Liquid airdrop. While the other side is still unmatched the bridge stays pending rather than guessing, and you can create a manual bridge for the cases automatic matching can't resolve.

Issued assets like USDt are first-class. They carry their own display precision and metadata, so a non-BTC token scales correctly instead of being read as sats, and non-BTC Liquid balances surface as exclusions from your BTC capital gains rather than polluting the number.

## Also in this release

**Wallets and sync**

- **Multi-descriptor wallet families.** Descriptor and LiquidDescriptor connections now take a `descriptors` array, scanning each member independently with its own checkpoint. The legacy single-descriptor shape still works, and descriptor uniqueness is enforced across Bitcoin and Liquid connections.
- **New `clams chain-sources` command** with `list`, `create`, `select`, `update`, and `delete` (`clams onchain` stays as an alias). Source selection is family-scoped: Bitcoin connections use the Bitcoin source, Liquid connections use the Liquid source, and `sync --all` resolves the right one per connection.
- **Backend-level streaming sync** for Descriptor, XPub, and Address connections, replacing the legacy BDK paths. It holds far less in memory, bounds discovery with sparse frontiers that survive repeat and force-full syncs, and emits indexing progress notifications during long syncs.
- Tightened reorg and repeat-sync handling: RPC scans above the node tip persist the tip instead of replaying from genesis, stale records that vanish after a reorg are pruned, and Electrum and Esplora rescan recent activity inside the reorg window.

**Lightning**

- Lightning HTLC continuation outputs no longer quarantine when the proved input and output amounts match exactly.
- Better Core Lightning diagnostics for pending confirmed on-chain lookups, with a retry before deferring.

**Reports, CLI, and machine output**

- The `portfolio_summary` machine-output schema moves to version 2, replacing `asset_code` with richer asset display metadata.
- `clams update --dry-run` now reports the planned upgrade in clean JSON, without human prompts or installer notices.
- Unified the command surface across account, connection, canonical, journal, metadata, profile, workspace, and on-chain commands, with stronger validation.
- Interactive prompts now support normal line editing on Unix terminals.

## Update

<pre><code>clams update</code></pre>

If you've been tracking connections on an earlier build, re-sync them and run **clams journals process** again, then regenerate any exported reports.

Run into issues? Use **clams feedback** or reach out at **support@clams.tech**.

Clams Team