Skip to content

@dpad85 dpad85 released this Mar 28, 2019 · 135 commits to mainnet since this release

This is a major release for the mainnet version of the application, which has now caught up with the testnet version and can receive payments over Lightning.

Summary (for the mainnet version)

Enabling receive over Lightning

This feature must be explicitely enabled by the user. To do so, she first may have to close old existing channels (if their remote refund delay is 144 blocks which is not high enough). Enabling the feature will also display a message warning the user that she has to make sure that the app doesn't lose internet connectivity for two weeks straight.

Background watcher

A service periodically runs in the background, starting a light process (see CheckElectrumSetup) that connects to an electrum server and checks the blockchain. In case a cheating attempt is detected, a notification will be displayed to the user, urging her to start the application as soon as possible. If this background watcher cannot run or connect to the internet, after a while, a message will inform the user.

UI update

The left-hand panel in the home page has been updated to also display a lightning payment request, with a QR code. The payment request's description and amount are editable.

The payment items layout in the transaction list has been updated and should be more readable.

A display on top of the channels' list (right-hand panel in the home page) has been added, summarizing the total amount that can currently be received or sent over Lightning. Note that this amount is optimistic, meaning that funds in unconfirmed channels will be taken into account, and that this amount is aggregated and may not be sent/received in a single payment.

A similar display is added on top of each channel's details page.

Liquidity Service

When opening a channel to ACINQ's mainnet node, the user can also request this node to open a channel back for a small fee, using the push mechanism.

See our blog post for more information about this release:


You can find the complete list of changes 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
Assets 3
You can’t perform that action at this time.