Historical balance sheets, more reliable Lightning and on-chain syncs, testnet4 support, and a long list of fixes.
Historical Balance Sheets
The balance sheet report now accepts an --as-of flag, so you can produce a balance sheet for any point in the past:
clams reports balance-sheet --as-of 2026-03-31T23:59:59ZThe output itself has been cleaned up. Assets, Liabilities, and Equity each get their own section with totals and a balance check. Timestamps render in your local timezone, and amounts are comma-grouped. Connection labels are more stable across saved reports, holding up better across renames and deletions.
More Reliable Lightning Syncs
Core Lightning syncs now handle Esplora rate limits gracefully, work cleanly over Tor-backed Commando connections, and process closed channels and long-running syncs more reliably. CLN and LND syncs are also faster: independent node requests overlap where it's safe to do so.
LND pending-invoice handling has been improved. Nodes with many open invoices, or sync runs that were interrupted, now complete more reliably.
Force Full Sync
When a checkpoint looks stale or suspect, you can force a full re-sync from scratch:
clams connections sync --all --force-full-syncUseful after reconnecting an old node, restoring from backup, or when you want to rule out checkpoint corruption.
On-Chain Wallet Improvements
Descriptor and XPub connections pick up several improvements: faster incremental syncs after the first scan, recovery from older checkpoint formats, and more complete handling of historical wallet-owned outputs.
Testnet4 is now a supported network for Address, Descriptor, and XPub connections.
Journals
A new clams journals events count subcommand summarizes journal activity by event type and connection, giving you a fast way to sanity-check what your journal contains.
Journal processing is faster on large Lightning-heavy profiles. If a previous run crashed, an abandoned journals.lock no longer blocks future runs.
Reporting Fixes
Capital gains and portfolio summary calculations have been corrected in edge cases involving stale fiat rates, metadata account overrides, and same-timestamp buys and sells.
Aliased Lightning channel-open accounting now attributes funding to the correct connection. Balance sheets no longer show inflated residual on-chain fees from these channel opens.
CLI Changes
A few command surfaces have changed:
- clams connections create now requires configuration up front for Nwc and Address connections. CoreLn and Lnd can still be created without config for manual import workflows.
- Explicit CLI commands no longer auto-run clams init when config is missing. The CLI now plays cleanly with state created by the desktop app.
- Paginated list commands include has_more in JSON and YAML output, so scripting pagination is simpler.
- clams metadata records excluded set --excluded false now works as documented, letting you un-exclude records using the boolean form.
- clams profiles set --onchain-source-id rejects invalid source IDs before the setting is saved.
Connection setup and sync error messages are clearer, especially for malformed configs, NWC wallet errors, and timeouts.
Installation
The install and update examples now download scripts before executing them, instead of piping network responses directly into a shell. The Windows clams update fallback also handles a few previously-broken edge cases.
Update
clams updateRun into issues? Use clams feedback or reach out at support@clams.tech.
Clams Team