mirror of https://github.com/ACINQ/eclair.git synced 2025-03-13 03:14:26 +01:00

Reject new static_remote_key channels (#2881 )

* Reject new static_remote_key channels

We will still load and use existing static_remote_key channels, we can still open static_remote_key channels, but we will not accept new static_remote_key channels.
This behaviour can be overridden by setting `eclair.channel.accept-incoming-static-remote-key-channels` to `true`.

* Reject new obsolete incoming channels

We reject new incoming channels that don't even support `option_static_remotekey` (which is assumed to be on in the BOLTs).
Unit tests have been modified to use static_remote_key or anchor channels (default used to be the obsolete "standard" channel).

---------

Co-authored-by: Bastien Teinturier <31281497+t-bast@users.noreply.github.com>

2024-07-16 17:11:41 +02:00

2.6 KiB

Raw Blame History

Eclair vnext

Major changes

Update minimal version of Bitcoin Core

With this release, eclair requires using Bitcoin Core 27.1. Newer versions of Bitcoin Core may be used, but have not been extensively tested.

This version introduces a new coin selection algorithm called CoinGrinder that will reduce on-chain transaction costs when feerates are high.

To enable CoinGrinder at all fee rates and prevent the automatic consolidation of UTXOs, add the following line to your bitcoin.conf file:

consolidatefeerate=0

Incoming obsolete channels will be rejected

Eclair will not allow remote peers to open new static_remote_key channels. These channels are obsolete, node operators should use option_anchors channels now. Existing static_remote_key channels will continue to work. You can override this behaviour by setting eclair.channel.accept-incoming-static-remote-key-channels to true.

Eclair will not allow remote peers to open new obsolete channels that do not support option_static_remotekey.

API changes

Miscellaneous improvements and bug fixes

Verifying signatures

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

from our website: https://acinq.co/pgp/drouinf.asc
from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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.

Changelog

2.6 KiB Raw Blame History