Skip to content

Releases: ACINQ/eclair

Eclair v0.14.6

Choose a tag to compare

@sstone sstone released this 27 Oct 17:21
50e046e

This is a patch release that contains security hardening fixes, and a new configuration parameter to control whether splices can spend unconfirmed inputs (default is no).
We highly recommend upgrading, as some of these issues can be exploited by malicious nodes.

The detailed release notes can be found here.

Many thanks to @erickcestari for his responsible disclosures.

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 26.04.1
  • Adoptium OpenJDK 21.0.12.1

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

v0.14.5

Choose a tag to compare

@sstone sstone released this 20 Oct 16:12
01384e9

This is a patch release that contains security hardening fixes.
We highly recommend upgrading, as some of these issues can be exploited by malicious nodes.

The detailed release notes can be found here.

Many thanks to @Nuhiat-Arefin and @mptfire for their responsible disclosures.

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 26.04.1
  • Adoptium OpenJDK 21.0.12.1

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

Eclair v0.14.4

Choose a tag to compare

@sstone sstone released this 15 Oct 19:30
397abfc

This is a patch release that contains security hardening fixes, most originating from @erickcestari and project Loupe.
We highly recommend upgrading, as some of these issues can be exploited by malicious nodes.

The detailed release notes can be found here.

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 26.04.1
  • Adoptium OpenJDK 21.0.12.1

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

Eclair v0.14.3

Choose a tag to compare

@sstone sstone released this 14 Sep 16:03
1de8b2d

This is a patch release that contains security hardening fixes, most originating from project Loupe.
We highly recommend upgrading, as some of these issues can be exploited by malicious nodes.

The detailed release notes can be found here.

Verifying signatures

You will need gpg and our release signing key E434ED292E85643A. Note that you can get it:

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 24.04.1
  • Adoptium OpenJDK 21.0.6

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

Eclair v0.14.2

Choose a tag to compare

@t-bast t-bast released this 26 Aug 14:50
3dd8d2d

This is a patch release that contains several bug fixes.
We highly recommend upgrading, as some of these issues can be exploited by malicious nodes.

We now explicitly document that bitcoind should run on the same machine as eclair, or that a secure tunnel (providing encryption and authentication) must be setup between eclair and bitcoind. If you are running bitcoind on a remote machine without a secure tunnel, you should rework your setup.

The detailed release notes can be found here.

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 24.04.1
  • Adoptium OpenJDK 21.0.6

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

Eclair v.0.14.1

Choose a tag to compare

@t-bast t-bast released this 29 Jul 12:32
d769db0

This is a patch release that contains several bug fixes and performance improvements.
It also updates the minimal version of Bitcoin Core and our bitcoin library.

The detailed release notes can be found here.

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 24.04.1
  • Adoptium OpenJDK 21.0.6

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

Eclair v0.14.0

Choose a tag to compare

@t-bast t-bast released this 21 May 12:46
ec8c63b

This release contains the final version of channel splicing, taproot channels and zero-fee commitments.
We remove support for channels that don't use anchor outputs: see the release notes of eclair v0.13.1 for instructions on how to properly close those channels if needed.
We introduce an experimental peer scoring algorithm to optimize routing.

This release is packed with improvements to the performance of large nodes when restarting: let us know if that helps!
And of course, we also included a few bug fixes.

⚠️ We also update our dependency on Bitcoin Core to v30.x to benefit from v3/TRUC transactions and ephemeral dust.

The detailed release notes can be found here.

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 24.04.1
  • Adoptium OpenJDK 21.0.6

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

Eclair v0.13.1

Choose a tag to compare

@t-bast t-bast released this 27 Oct 08:50
9830aa6

This release contains database changes to prepare for the removal of pre-anchor channels.
Closed channels will be moved to a new table on restart, which may take some time, but will only happen once.

⚠️ Note that you will need to run the v0.13.0 release first to migrate your channel data to the latest internal encoding.

This is the last release of eclair where channels that don't use anchor outputs will be supported.
If you have channels that don't use anchor outputs, you should close them now.
You can list those channels using the following command:

$ eclair-cli channels | jq '.[] | { channelId: .data.commitments.channelParams.channelId, commitmentFormat: .data.commitments.active[].commitmentFormat }' | jq 'select(.["commitmentFormat"] == "legacy")'

If your peer is online, you can then cooperatively close those channels using the following command:

$ eclair-cli close --channelId=<channel_id_from_previous_step>  --preferredFeerateSatByte=<feerate_satoshis_per_byte>

If your peer isn't online, you may want to force-close those channels to recover your funds:

$ eclair-cli forceclose --channelId=<channel_id_from_previous_step>

⚠️ This release also updates the dependency on Bitcoin Core to v29.x (we recommend using v29.2).

The detailed release notes can be found here.

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 24.04.1
  • Adoptium OpenJDK 21.0.6

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

Eclair v0.13.0

Choose a tag to compare

@t-bast t-bast released this 10 Sep 13:32
992ec8c

This release contains a lot of refactoring and an initial implementation of taproot channels.
The specification for taproot channels is still ongoing (lightning/bolts#995) so this cannot be used yet, but it is ready for cross-compatibility tests with other implementations.

This release also contains improvements to splicing based on recent specification updates, and better Bolt 12 support.
Note that the splicing specification is still pending, so it cannot be used with other implementations yet.

This is the last release of eclair where channels that don't use anchor outputs will be supported.
If you have channels that don't use anchor outputs, you should close them (see below for more details).

As usual, this release contains various performance improvements, more configuration options and bug fixes.
In particular, the amount of data stored for each channel has been optimized (especially during force-close), which reduces the size of the channels DB.
Also, the performance of the on-chain watcher during mass force-close has been drastically improved.

The detailed release notes can be found here

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 24.04.1
  • Adoptium OpenJDK 21.0.6

Then use the following command to generate the eclair-node packages:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.

Eclair v0.12.0

Choose a tag to compare

@t-bast t-bast released this 11 Mar 15:43
4df8cd0

This release adds support for creating and managing Bolt 12 offers and a new channel closing protocol (option_simple_close) that supports RBF.
We also add support for storing small amounts of (encrypted) data for our peers (option_provide_storage).

⚠️ This release also starts using Java 21, which means you may need to update your runtime.
⚠️ We also update our dependency on Bitcoin Core to v28.1 to benefit from package relay.

We've also made more progress on splicing, which is getting into the final stage of cross-compatibility tests.
This cannot be used yet with other implementations, but will likely be available in the next release.

This release also contains various performance improvements, more configuration options and bug fixes.
One notable performance improvement is a change in one of our database indexes (see #2946), which may take a few seconds to complete when restarting your node.

The detailed release notes can be found here.

Verifying signatures

You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:

To import our signing key:

$ gpg --import drouinf2.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Building

Eclair builds are deterministic. To reproduce our builds, please use the following environment (*):

  • Ubuntu 24.04.1
  • Adoptium OpenJDK 21.0.4

Use the following command to generate the eclair-node package:

./mvnw clean install -DskipTests

That should generate eclair-node/target/eclair-node-<version>-XXXXXXX-bin.zip with sha256 checksums that match the one we provide and sign in SHA256SUMS.asc

(*) You may be able to build the exact same artefacts with other operating systems or versions of JDK 21, we have not tried everything.

Upgrading

This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.