We remove the code used to support legacy channels that don't use anchor outputs or taproot. If you still have such channels, eclair won't start: you will need to close those channels, and will only be able to update eclair once they have been successfully closed.
We update our channel jamming mitigation to match the latest draft of the spec. Note that we use a different architecture for channel bucketing and confidence scoring than what is described in the BOLTs. We don't yet fail HTLCs that don't meet these restrictions: we're only collecting data so far to evaluate how the algorithm performs.
If you want to disable this feature entirely, you can set the following values in eclair.conf:
eclair.relay.peer-reputation.enabled = false
eclair.relay.reserved-for-accountable = 0.0You will need gpg and our release signing key E04E48E72C205463. Note that you can get it:
- from our website: https://acinq.co/pgp/drouinf2.asc
- from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys
To import our signing key:
$ gpg --import drouinf2.ascTo verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.strippedEclair 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 -DskipTestsThat 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.
This release is fully compatible with previous eclair versions. You don't need to close your channels, just stop eclair, upgrade and restart.
<fill this section when publishing the release with git log v0.13.1... --format=oneline --reverse>