Lightning Terminal v0.17.8

In this release, we rebuild Lightning Terminal and its bundled daemons with Go
1.27.3 to address CVE-2026-111943.
Go's crypto/x509 verifier now rejects certificate chains containing a specific
set of intermediate certificates due to security concerns around their
operation. We recommend that all users upgrade.

This release also fixes integrated sub-server shutdown and SQL error matching,
and updates the bundled LND, Loop, Pool, and Faraday dependencies.

Changes

• Fix integrated sub-server shutdown.
  Runtime error receivers remain active while sub-servers stop, and initialized
  sub-servers are cleaned up even after reporting an error. This prevents
  shutdown from blocking on an undrained error channel or skipping cleanup.
• Fix SQL error matching.
  Mapped SQL errors now implement error only through their pointer types,
  so an incorrect match against a value type fails to compile instead of
  silently failing at runtime.
• Update the Go toolchain and bundled dependencies.
  All bundled services, including Taproot Assets, are compiled with Go 1.27.3.
  Loop and its generated RPC clients use the same source revision, including
  on-chain cost and status fields for static-address deposits and loop-ins.

See the release-specific notes
and full changes since v0.17.7.

Bundled versions

Loop, Pool, and Faraday are pinned to public source commits rather than new
standalone release tags. The exact module versions are recorded in
go.mod.

Database migrations and upgrade notes

Back up your databases before upgrading. There is no new LiT database schema
migration relative to v0.17.7, and LND v0.21.5-beta.rc1 adds no database
migrations. The bundled Loop update does include a
SQL migration
that adds on-chain cost fields to static-address deposits. Loop applies this
migration when it starts and looks up costs for existing deposits after
upgrading.

Instant Out API callers must now set max_swap_fee_sat; requests that omit
the fee cap are rejected. An explicit zero cap is valid. Review the bundled
Loop v0.35.1 notes
and subsequent Loop changes
for the remaining swap fixes and API changes included in this source revision.

Users upgrading from v0.16.1 or earlier must review the
v0.17.0 migration notes
before starting LiT. The first startup with a SQL backend requires explicit
confirmation. For noninteractive deployments, set auto-migrate-to-sql=true
in lit.conf or LIT_AUTO_MIGRATE_TO_SQL=true in the environment. To defer
migration, set databasebackend=bbolt before migration runs. Once migration
completes, the old bbolt database is tombstoned, and a downgrade to a version
before v0.17.0-alpha is unsupported.

If you use Taproot Assets channels, follow the
Taproot Assets operational safety guidelines
and arrange a controlled update of affected nodes.

Verifying the release

Download the archive for your platform, manifest-v0.17.8.txt, and
manifest-roasbeef-v0.17.8.sig from this release. The detached PGP signature
authenticates the manifest, which contains the SHA-256 hashes of the release
archives and binaries.

Download the release signing key
and check that its primary fingerprint is
A5B61896952D9FDA83BC054CDC42612E89237182 before importing it:

gpg --show-keys --with-fingerprint roasbeef.asc
gpg --import roasbeef.asc
gpg --verify manifest-roasbeef-v0.17.8.sig manifest-v0.17.8.txt
shasum -a 256 <downloaded-archive>

Compare the archive hash with its entry in manifest-v0.17.8.txt.

OpenTimestamps proofs are attached for both the manifest and its signature:

ots verify manifest-v0.17.8.txt.ots
ots verify manifest-roasbeef-v0.17.8.sig.ots

Bitcoin confirmation is required to verify the timestamp attestation. If a
proof reports pending confirmation, retry after the confirmations arrive.

Reproducing the release binaries

The release binaries are compiled with Go 1.27.3. Use the same toolchain to
reproduce them. The release script includes the litd, autopilotrpc,
signrpc, walletrpc, chainrpc, invoicesrpc, watchtowerrpc,
neutrinorpc, monitoring, peersrpc, kvdb_postgres, kvdb_etcd, and
kvdb_sqlite build tags.

make docker-release tag=v0.17.8

To build a single platform, add sys=<OS-ARCH> to the command. Compare the
resulting binary hashes with the entries in manifest-v0.17.8.txt.

Verifying Docker images

To verify the litd and litcli binaries in a Docker image, extract the
binaries, compute their SHA-256 hashes with shasum -a 256 <filename>, and
compare them with the corresponding entries in manifest-v0.17.8.txt.

Contributors (alphabetical order)

• Olaoluwa Osuntokun
• Viktor Torstensson