All Versions
25
Latest Version
Avg Release Cycle
35 days
Latest Release
374 days ago

Changelog History
Page 1

  • v0.4.6-android

    November 30, 2020
  • v0.4.5-android

    November 13, 2020
  • v0.4.4-android

    November 12, 2020
  • v0.4.3-android

    November 10, 2020
  • v0.4.2 Changes

    October 19, 2020

    ๐Ÿš€ This release includes many exciting new features, API changes as well as several bug fixes and improvements.
    Its is fully compatible with 0.4.1 (and all previous versions of eclair).

    Major changes

    ๐Ÿ”Œ Plugins

    ๐Ÿ”Œ Third-party plugins are now able to add new feature bits to eclair and handle unknown custom messages.
    ๐Ÿ”Œ This lets plugin developers offer services to their customers that are not available in the Lightning specification (e.g. swap-in/swap-out), while staying fully compatible with the network.

    ๐Ÿ‘€ See #1528 for more details.

    Anchor Outputs

    ๐Ÿš€ This release adds experimental support for anchor outputs channels.
    The main benefit of this type of channels is that it is possible to bump the on-chain fees of commitment transactions and htlc transactions once they are in the mempool to speed up their confirmation.

    Eclair is fully compatible with the anchor output specification, but automatic fee bumping has not been implemented yet, hence we do not recommend activating the feature.
    ๐Ÿš€ Some attacks that are specific to anchor outputs have also been discovered recently and haven't been fully addressed yet, but will be fixed in future releases.

    Keysend

    ๐Ÿš€ This release adds support for spontaneous payments using keysend.
    It is fully compatible with lnd and c-lightning and makes it easy for public LN nodes to receive donations.

    API changes

    ๐Ÿš€ This release contains many new APIs and improvements to existing ones:

    • โž• Add signmessage/verifymessage APIs: this allows signing arbitrary messages with the node's key and is compatible with lnd and c-lightning
    • We publish new channel events to the websocket (channel-opened, channel-state-changed and channel-closed)
    • The sendtoroute API now lets you choose the channels that must be used, making it easy to rebalance your local channels

    ๐Ÿ“š Head over to our API documentation for more details.

    ๐Ÿ›  Miscellaneous improvements and bug fixes

    • โ™ป๏ธ Many actors have been refactored to use Akka Typed instead of classic actors.
      ๐Ÿ‘ This leads to a cleaner design, better types and more help from the compiler to detect unhandled messages.
    • ๐Ÿ‘ We added support for Bitcoin Core 0.20.1.
    • ๐Ÿ‘€ We added support for non-default Bitcoin Core wallets (see #1540 for details)
    • ๐Ÿ”ง We fixed the override-features configuration parameter, which wasn't overriding features everywhere. This parameter can be very useful for example to sync only from specific nodes, or advertize wumbo support only to nodes that you trust.

    ๐Ÿ‘Œ 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 19.10
    • AdoptOpenJDK 11.0.6
    • Maven 3.6.3

    ๐Ÿ“ฆ Use the following command to generate the eclair-node package:

    mvn clean install -DskipTests
    

    That should generate eclair-node/target/eclair-node-0.4.2-XXXXXXX-bin.zip with sha256 checksums that matches 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 Eclair v0.4.1. You don't need to close your channels, just stop eclair, upgrade and restart.

    ๐Ÿ”„ Changelog

  • v0.4.2-android

    October 14, 2020
  • v0.4.1 Changes

    July 15, 2020

    ๐Ÿš€ This release includes many exciting new features, API changes as well as several bug fixes and improvements.
    Its is fully compatible with 0.4 (and all previous versions of eclair).

    Major changes

    Static Remote Key

    This release adds support for option_static_remotekey.
    โšก๏ธ This removes the key rotation at each update of the commitment, and allows simpler funds recovery in case of backup loss: channel outputs will directly pay to one of your bitcoin wallet addresses.

    0๏ธโƒฃ This option is disabled by default, and will only be available for new channels when both peers activate the feature.
    To enable it, add the following lines to your eclair.conf:

    eclair.features {
        option_static_remotekey = optional
    }
    

    You can verify that this is activated with the getinfo API, which now returns the list of features:

    "features": { "activated": [{ "name": "basic\_mpp", "support": "optional" }, { "name": "initial\_routing\_sync", "support": "optional" }, { "name": "option\_data\_loss\_protect", "support": "optional" }, { "name": "gossip\_queries\_ex", "support": "optional" }, { "name": "payment\_secret", "support": "optional" }, { "name": "var\_onion\_optin", "support": "optional" }, { "name": "gossip\_queries", "support": "optional" }], "unknown": [] }
    

    ๐Ÿ‘Œ Improvements to path-finding and MPP

    We've made several improvements to the path-finding algorithm. It now takes into account your channel's current balance more accurately when selecting a route.

    ๐Ÿš€ The MPP split algorithm has been rewritten from the ground up, inspired by flow algorithms (see #1427 for details). MPP is now enabled by default (it was introduced in eclair v0.3.3 but was opt-in) for all eclair nodes and will soon be available on eclair-mobile (note that Phoenix has had MPP support since its first release).

    MPP synergizes well with trampoline: trampoline nodes aggregate incoming MPP and re-split them more efficiently on outgoing channels.

    ๐Ÿ‘ PostgreSQL beta support

    ๐Ÿ‘ Thanks to @rorp, eclair now supports PostgreSQL as a database backend!

    0๏ธโƒฃ By default eclair still uses SQLite, but you can follow the instructions here to use PostgreSQL instead.

    We're looking for feedback on how well this is working for you, so don't hesitate to try it out and let us know!

    Human-readable features

    Say goodbye to hex-encoded features: we've changed the format to be human-readable.

    ๐Ÿ”ง Here is how they are configured by default:

    eclair.features {
      initial_routing_sync = optional
      option_data_loss_protect = optional
      gossip_queries = optional
      gossip_queries_ex = optional
      var_onion_optin = optional
      payment_secret = optional
      basic_mpp = optional
    }
    

    Note that if you want to disable features, there is a trick. You need to first set the features to null and then provide your set of chosen features, for example (in your eclair.conf):

    eclair.features : null
    eclair.features {
      option_data_loss_protect = optional
      var_onion_optin = optional
      payment_secret = optional
      basic_mpp = optional
      option_static_remotekey = optional
    }
    

    You can verify what features have been set with the getinfo API:

    eclair-cli getinfo { "version": "0.4.1-SNAPSHOT-xxxxxxx", "nodeId": "...", "alias": "...", "color": "...", "features": { "activated": [{ "name": "basic\_mpp", "support": "optional" }, { "name": "initial\_routing\_sync", "support": "optional" }, { "name": "option\_data\_loss\_protect", "support": "optional" }, { "name": "gossip\_queries\_ex", "support": "optional" }, { "name": "payment\_secret", "support": "optional" }, { "name": "var\_onion\_optin", "support": "optional" }, { "name": "gossip\_queries", "support": "optional" }], "unknown": [] }, "chainHash": "...", "network": "...", "blockHeight": 1, "publicAddresses": [], "instanceId": "..."}
    

    Feerate mismatch

    When you disagree with your peer about on-chain fee rates, your funds may be at risk if your peer is malicious.
    For this reason, eclair has always been closing channels on your behalf before the situation gets too dangerous.

    ๐Ÿ”ง Your tolerance to fee rate mismatch was previously configured via eclair.on-chain-fees.max-feerate-mismatch.
    ๐Ÿ”ง You can now independently configure your tolerance to either lower or higher fee rates:

    eclair.on-chain-fees.feerate-tolerance {
      ratio-low = 0.5 // will allow remote fee rates as low as half our local feerate
      ratio-high = 10.0 // will allow remote fee rates as high as 10 times our local feerate
    }
    

    0๏ธโƒฃ It's less dangerous if your peer overestimates the fees than if she underestimates it, hence the different default values.

    We've also made changes to reduce the number of unnecessary close, by only closing channels when there are funds at risk in pending HTLCs. If your channel doesn't have pending HTLCs, eclair will safely ignore the remote fee rate and won't close the channel.

    API changes

    ๐Ÿš€ This release is packed with new APIs and improvements to existing ones:

    • โšก๏ธ batch channel updates (updaterelayfee, close, forceclose)
    • nodes to lookup node announcements
    • ๐Ÿ‘ better channelstats
    • onchainbalance, sendonchain and onchaintransactions to interact with layer-1
    • more data returned in most API responses

    ๐Ÿ“š Head over to our API documentation for more details.

    ๐Ÿ›  Miscellaneous improvements and bug fixes

    • ๐Ÿ‘ More metrics for an even better monitoring experience with Kamon.
    • Various improvements to connection handling and reconnection logic.
    • โšก๏ธ Updates to security parameters default values.
    • Various improvements on fee estimation.
    • ๐Ÿ‘ Better errors for trampoline payments.
    • ๐ŸŒฒ Logging improvements.

    ๐Ÿ‘Œ 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 19.10
    • AdoptOpenJDK 11.0.6
    • Maven 3.6.3

    ๐Ÿ“ฆ Use the following command to generate the eclair-node package:

    mvn clean install -DskipTests
    

    That should generate eclair-node/target/eclair-node-0.4.1-XXXXXXX-bin.zip with sha256 checksums that matches 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 Eclair v0.4. You don't need to close your channels, just stop eclair, upgrade and restart.

    ๐Ÿ”„ Changelog

  • v0.4 Changes

    July 15, 2020

    ๐Ÿš€ This release includes major upgrades to our core libraries (Scala and Akka), as well as several bug fixes and improvements.
    Its is fully compatible with 0.3.4 (and all previous versions of eclair).

    Major changes

    Scala 2.13, Akka 2.6

    โšก๏ธ Update from Scala 2.11 and Akka 2.4 to Scala 2.13 and Akka 2.6.

    Scala 2.13 brings a lot of improvements, among which:

    • ๐Ÿ‘ better performance
    • tons of improvements for standard collections
    • faster compile times
    • ๐Ÿ‘ better support for deterministic builds

    Akka 2.6 contains a couple years of steady improvements over Akka 2.4:

    • ๐Ÿ‘ better performance
    • ๐Ÿ‘ better APIs and the introduction of typed actors
    • production-ready akka-cluster

    โšก๏ธ Eclair will incrementally take advantage of the new features these updates have to offer.

    Bitcoin 0.19.1

    โž• Add support for Bitcoin Core 0.19.1.

    The most notable change impacting eclair is that fundrawtransaction does not fail when providing a too low feerate, but instead bitcoin will fail when broadcasting the transaction with sendrawtransaction. This is correctly handled by eclair v0.4.

    ๐Ÿ—„ GUI deprecation

    ๐Ÿš€ eclair-node-gui is being deprecated and will is not published with this release. Source code will still remain available for some time, and building the GUI is very easy (check BUILD.md for more details, but basically mvn install -DskipTests is enough to build eclair-node and eclair-node-gui).

    ๐Ÿ We strongly encourage people to use the API instead, see here for more information (it works on Windows too). We also added instructions on how to setup a monitoring endpoint, where you can create your own graphs and alerts.

    โœ… Our GUI was built for demonstration and testing purposes, typically with a few nodes on single machine and in regtest mode. Using it as a Lightning wallet or to run routing nodes on mainnet is a very bad fit:

    • if you're looking for a Lightning wallet, consider using Phoenix or Eclair Mobile instead.
    • if you want to run a routing node, then it should be running on a machine that is reliable, secure, maintained, reachable from the internet and online most of the time, i.e probably not your desktop PC.
    • having a "bitcoin-like" GUI is misleading: if your Bitcoin node is offline it has a minimal impact on the Bitcoin network and you can still "receive" funds. When you start it again it catches up on the blocks and transactions that it has missed, so having a Bitcoin wallet or node that is often offline is fine. But when your Lightning node is offline it cannot send, receive or relay transactions. Your channels will be tagged as disabled and other nodes will have to route around you and will likely avoid you in the future because of your unreliability.

    ๐Ÿ›  Miscellaneous improvements and bug fixes

    • ๐Ÿ‘ More metrics for an even better monitoring experience with Kamon.
    • ๐Ÿ‘Œ Improvements to our p2p handling of incoming and outgoing connections.
    • ๐Ÿ›  Fixed some race conditions in tests that were leading to random build failures.
    • โž• Added more tests around mempool introspection to extract preimages early.
    • ๐Ÿ›  UTXOs weren't always correctly unlocked in the Bitcoin Core wallet in case funding failed (fixed in #1404)

    ๐Ÿ‘Œ 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 19.10
    • AdoptOpenJDK 11.0.6
    • Maven 3.6.3

    ๐Ÿ“ฆ Use the following command to generate the eclair-node package:

    mvn clean install -DskipTests
    

    That should generate eclair-node/target/eclair-node-0.4-XXXXXXX-bin.zip with sha256 checksums that matches 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 Eclair v0.3.4. You don't need to close your channels, just stop eclair, upgrade and restart.

    ๐Ÿ”„ Changelog

    • ๐Ÿ‘‰ Use correct type for parameters in ExtendedBitcoinClient (#1248)
    • ๐Ÿ‘Œ Support additional TLV records in SendPayentRequest (#1367)
    • ๐Ÿšš Move router handlers to separate files (#1352)
    • Do not reconnect immediately if we keep getting disconnected (#1371)
    • ๐Ÿ‘ Better tracking of channels count metric (#1369)
    • โช Revert Electrum Tor disabling SSL check (#1376)
    • โž• Add logback config for eclair-node tests (#1377)
    • Gossip metrics (#1372)
    • โž• Add a rejection for update when channel is pruned (#1378)
    • ๐Ÿ‘‰ Use sender instead of providing actor refs (#1379)
    • โšก๏ธ Send update_fee on reconnection (#1383)
    • โ™ป๏ธ Refactor transaction generation errors (#1366)
    • ๐Ÿ›  fixup! Use sender instead of providing actor refs (#1379) (#1386)
    • Router channel balance (#1382)
    • โฌ†๏ธ Prepare upgrade to scala 2.13 and akka 2.6 (#1389)
    • โช Revert "Use sender instead of providing actor refs (#1379)" (#1391)
    • ๐Ÿ›  Fix race condition in router tests (#1392)
    • โšก๏ธ Update to scala 2.13 and akka 2.6 (incremental) (#1390)
    • โฌ‡๏ธ Downgrade to scala 2.13.1 (#1394)
    • ๐Ÿ‘Œ Support bitcoin-0.19.1 (#1380)
    • โœ… Test preimage extraction from mempool (#1387)
    • โœ‚ Remove unused attribute in Peer (#1397)
    • โœ… Disable backup handler in tests (#1399)
    • ๐Ÿ›  Fix BitcoinCoreWalletSpec (#1401)
    • Platform.currentTime->System.currentTimeMillis (#1403)
    • Delegate client creation to a specialized actor (#1400)
    • ๐Ÿ“š Monitoring documentation (#1402)
    • Validate channel_announcement sigs early (#1406)
    • Unlock transaction inputs if tx cannot be published (#1404)
    • โšก๏ธ Update README (#1405)
    • Minor: catch harmless unhandled events (#1407)
  • v0.3.10-android

    July 16, 2020
  • v0.3.9-android

    June 24, 2020