# Phoenixd Connection Sync & River Mining CSV Exports | v1.0.0-beta.15

> Clams v1.0.0-beta.15: native phoenixd connection sync with Lightning and on-chain modeling, support for River mining CSV exports, configurable gap limits, and the retirement of the legacy cloud backend.

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

**TL;DR:** Clams now syncs directly from a [phoenixd](/integrations/phoenixd/) server over its HTTP API. This release also adds support for River mining CSV exports, configurable discovery gap limits up to 5000, and retires the legacy cloud backend so Clams runs local or self-hosted only.

## Phoenixd Connection Sync

[phoenixd](https://phoenix.acinq.co/server) is the server build of ACINQ's Phoenix wallet: a self-custodial Lightning wallet with automated channel management that you run on your own infrastructure. Clams now connects to it natively over its HTTP API, no CSV export required.

Point Clams at your server with a read-only credential and it keeps your books current automatically. Under the hood this release models the full picture:

- **Lightning deposits and withdrawals** are booked as incoming and outgoing payments with their amounts, fees, timestamps, and descriptions.
- **On-chain withdrawal txid mapping** ties swap-out payments to their settling Bitcoin transaction, so a Lightning withdrawal that lands on-chain reconciles as one movement instead of two.
- **Liquidity fees are canonicalized** into your journal, so the cost of automated channel management is accounted for rather than lost.
- **Fee credits** are read from the balance API and surfaced as prepaid liquidity, separate from your spendable Lightning balance.
- **Stable event identity** keeps repeat syncs idempotent, so re-running a sync never double-books a payment.
- **Tor proxy routing** lets you reach a remote phoenixd server over an onion address.

Connecting takes one command. Create a JSON config with your server's address and its read-only HTTP password:

<pre><code>{
  "base_url": "http://127.0.0.1:9740",
  "password": "&lt;phoenixd-http-password&gt;",
  "timeout_secs": 30,
  "page_size": 100
}</code></pre>

Then create and sync the connection:

<pre><code>clams connections create --label phoenixd --kind Phoenixd --configuration-file phoenixd.json
clams connections sync phoenixd</code></pre>

The full walkthrough lives in the [phoenixd integration guide](/integrations/phoenixd/).

## River Mining CSV Exports

Clams now imports [River](/integrations/river/) mining CSV exports, covering both Account Activity and Bitcoin Activity reports. Mining payouts and account movements book straight into your journal with accurate cost basis, so mining operations get the same audit-ready treatment as every other source.

## Also in this release

**Wallets and sync**

- **Configurable gap limits.** `clams connections update <CONNECTION> --gap-limit <N>` sets the wallet discovery gap limit for XPub, Descriptor, and LiquidDescriptor connections, accepting values up to 5000 for wallets with sparse or widely spaced activity.

**Deployment**

- **The legacy cloud backend has been removed.** Clams runs local or self-hosted. The `local` backend remains the default, and you can point at any [Clams Server](/server/) you run yourself. See [deployment options](/deployments/).

## 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