Skip to content

Releases: ACINQ/eclair

Eclair v0.13.1

27 Oct 08:50
9830aa6

Choose a tag to compare

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

10 Sep 13:32
992ec8c

Choose a tag to compare

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

11 Mar 15:43
4df8cd0

Choose a tag to compare

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.

Eclair v0.11.0

04 Dec 09:23
7e7ad45

Choose a tag to compare

This release adds official support for Bolt 12 offers and makes progress on liquidity management features (splicing, liquidity ads, on-the-fly funding). We also stop accepting channels that don't support anchor outputs and update our dependency on Bitcoin Core.

We're still actively working with other implementations to finalize the specification for some of these experimental features. You should only activate them if you know what you're doing, and are ready to handle backwards-incompatible changes!

This release also contains various performance improvements, more configuration options and minor bug fixes.

The detailed release notes can be found here.

Verifying signatures

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

To import our signing key:

$ gpg --import drouinf.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 22.04
  • AdoptOpenJDK 11.0.22
  • Maven 3.9.2

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

mvn 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 11, 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.10.0

29 Feb 09:24
a63d2c2

Choose a tag to compare

This release adds official support for the dual-funding feature, an up-to-date implementation of Bolt 12 offers, and a fully working splicing prototype. We're waiting for the specification work to be finalized for some of those features, and other implementations to be ready for cross-compatibility tests. You should only activate them if you know what you're doing, and are ready to handle backwards-incompatible changes!

This release also contains various on-chain fee improvements, more configuration options, performance enhancements and various minor bug fixes.

The detailed release notes can be found here.

Verifying signatures

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

To import our signing key:

$ gpg --import drouinf.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 22.04
  • AdoptOpenJDK 11.0.22
  • Maven 3.9.2

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

mvn 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 11, 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.9.0

19 Jun 08:45
623f7e4

Choose a tag to compare

This release contains a lot of preparatory work for important (and complex) lightning features: dual-funding, splicing and Bolt 12 offers.
These features are now fully implemented in eclair, but we're waiting for the specification work to be finalized and other implementations to be ready for cross-compatibility tests.
You should only activate them if you know what you're doing, and are ready to handle potential backwards-incompatible changes!
We also make plugins more powerful, introduce mitigations against various types of DoS, and improve performance in many areas of the codebase.

The detailed release notes can be found here

Verifying signatures

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

To import our signing key:

$ gpg --import drouinf.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 22.04
  • AdoptOpenJDK 11.0.6
  • Maven 3.9.2

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

mvn 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 11, 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.8.0

01 Dec 14:09
0077471

Choose a tag to compare

This release adds official support for two important lightning features: zero-conf channels and channel aliases. It also adds experimental support for dual-funding and a lot of preparatory work for Bolt 12 offers.

⚠️ we also require at least Bitcoin Core 23.0: make sure to upgrade and reconfigure your node (see detailed instructions in the release notes)

The detailed release notes can be found here

Verifying signatures

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

To import our signing key:

$ gpg --import drouinf.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 20.04
  • AdoptOpenJDK 11.0.6
  • Maven 3.8.1

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

mvn 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 11, 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.7.0-patch-disconnect

18 Jul 11:06
cad88bf

Choose a tag to compare

Eclair v0.7.0-patch-disconnect

This is a patch release which adds two commits:

  • Add option to disable sending remote addr in init (#2285)
  • Resume reading after processing unknown messages (#2332)

It addresses unwanted disconnections with peers that use unknown messages.

Verifying signatures

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

To import our signing key:

$ gpg --import drouinf.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 20.04
  • AdoptOpenJDK 11.0.6
  • Maven 3.8.1

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

mvn clean install -DskipTests

That should generate eclair-node/target/eclair-node-0.7.0-cad88bf-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 11, 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.7.0

01 Feb 09:15
a804905

Choose a tag to compare

Eclair v0.7.0

This release adds official support for two long-awaited lightning features: anchor outputs and onion messages.
Support for the PostreSQL database backend is also now production ready!
This release also includes a few bug fixes and many new (smaller) features.
It is fully compatible with 0.6.2 (and all previous versions of eclair).

Because this release changes the default type of channels that your node will use, make sure you read the release notes carefully!
The release notes can be found here.

Verifying signatures

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

To import our signing key:

$ gpg --import drouinf.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 20.04
  • AdoptOpenJDK 11.0.6
  • Maven 3.8.1

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

mvn clean install -DskipTests

That should generate eclair-node/target/eclair-node-0.7.0-a804905-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 11, 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.6.2

08 Oct 07:52
6817d6f

Choose a tag to compare

Eclair v0.6.2

This releases fixes a known vulnerability, makes several performance improvements, includes a few bug fixes and many new features.
It is fully compatible with 0.6.1 (and all previous versions of eclair).

This release requires a few actions from node operators when upgrading: make sure you read the release notes carefully!

The release notes can be found here.

Verifying signatures

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

To import our signing key:

$ gpg --import drouinf.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 20.04
  • AdoptOpenJDK 11.0.6
  • Maven 3.8.1

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

mvn clean install -DskipTests

That should generate eclair-node/target/eclair-node-0.6.2-6817d6f-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 11, 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.