Skip to content

Releases: ACINQ/phoenix

Phoenix v1.4.8

04 Mar 15:20
92479ef
Compare
Choose a tag to compare

Main changes

The channel creation fee for pay-to-open has been increased: it's still 0.1% but there is now a 1000 sat minimum. The manual confirmation dialog and asynchronous pay-to-open logic have been removed. The FTUE page regarding the channel opening cost has been updated as well as the swap-in dialog so that we can display this new fee minimum value.

Complete list of changes

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix 1.4.7

04 Mar 15:20
0f37ee5
Compare
Choose a tag to compare

Main changes

Improve LNURL error feedback

Errors returned by LNURL services were not properly handled and information was lost, causing confusion, especially for LNURL-withdraw.

Notify user when channel opening is rejected

If a new channel must be created to receive an incoming payment but the amount is below the channel creation threshold, a notification is displayed. Note that this is not enabled yet because changes on the peer side are also needed.

-- edit: this is now enabled.

Complete list of changes

Thanks again @bitcoinuser for updating the Portuguese-Brazilian translation.

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix 1.4.6

02 Feb 16:40
b8a3249
Compare
Choose a tag to compare

Display min amount for pay-to-open

The minimum amount that the wallet can receive is now displayed when the wallet does not have any channels. It is also displayed for swap-ins. This minimum amount prevents creating new channels for very small amounts.

Complete list of changes

Thanks @bitcoinuser for updating the Portuguese-Brazilian translation.

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix v1.4.5

02 Feb 16:39
92f8fc6
Compare
Choose a tag to compare

Main changes

Closing logic is cooperative when we have nothing at stake

More information here: ACINQ/eclair#1633

Add links to terms

A link to the terms (explaining how the wallet works and what can be expected) has been added to the about and initialization screens.

Complete list of changes

Thanks @bitcoinuser for updating the Portuguese-Brazilian translation.

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix 1.4.4

15 Dec 13:09
f1dc438
Compare
Choose a tag to compare

Main changes

Support for lightning parameters in BIP21 invoices

BIP21 URIs can contain a lightning field if the recipient also accepts lightning payments. In that case the wallet now lets the user choose how he wants to pay the invoice.

Improve swapout feerate

Minimum feerate for swapout is now dynamic and should adjust with the state of the mempool.

Complete list of changes

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix 1.4.3

07 Dec 14:22
547e9e6
Compare
Choose a tag to compare

Main changes

Fixed some connection issues with peer

Use ip address instead of domain name to connect to the trampoline node. This caused connectivity issues in some cases, due to IPv6 conversion.

Complete list of changes

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix 1.4.2

17 Nov 14:37
02025a9
Compare
Choose a tag to compare

Main changes

Fixed some "route not found" errors

There was an issue where channels with less than 15 000 satoshis were ignored by the path-finding algorithm, which could prevent payments from going through and incorrectly trigger a "Route not found" error.

Complete list of changes

Thanks @bitcoinuser for updating PT-BR translation.

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix 1.4.1

13 Nov 10:45
3640b06
Compare
Choose a tag to compare

Main changes

Customizable max fees for outgoing Lightning payments

Users can now change the maximum fees that the trampoline node can use for outgoing LN payments. In some cases, the default setting may not be sufficient so the user can try higher fees. Note that the trampoline node will always try to use as low fee as possible. Also, setting a super high fee will not help if the recipient is simply not reachable (no channels/no connection) or does not have enough inbound liquidity.

This setting is available in Setting > Payment settings

Better error messages for failed payments

Some error messages are rewritten to be more explicit and provide guidance to users.

Small channels are more resilient to high fee environment

Channels inbound capacity is also displayed in the wallet's channels list.

Complete list of changes

Thanks @bitcoinuser for updating PT-BR translation.

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix 1.4.0

20 Oct 15:05
c10e59b
Compare
Choose a tag to compare

Main changes

Background payment reception

The app can now wake up to process an incoming payment or a fulfilled HTLC. Users do not have to start their app manually to receive a payment, thus removing the synchronization requirement between sender and receiver. This feature uses Firebase Cloud Messaging. Messages relayed by FCM do not contain any details about payments.

When the wake up message arrives, a sticky notification is displayed. The peer will pause the payment and wait ~20/30 seconds for the app to accept the payment, or fail the payment downstream. If the payment succeeds, the notification will show the amount received.

Access control changes

The seed is now encrypted using a new improved format leveraging the Android Keystore to protect the seed and allowing the node to run background tasks. The device's TEE/SE will be used when possible. The legacy PIN used on existing wallets is deprecated and migrated to the new format after updating the app. Wallet is locked with the system screen lock (schema/PIN/fingerprint...).

An additional security setting is available, requiring users to authenticate with fingerprint each time the seed is decrypted. This setting may improve security on rooted device (*) but obviously disables background processing features.

(*) We don't recommend using Bitcoin wallets (except on Testnet) on a rooted phone.

Automatic channel creation

Channels are now created automatically. A setting lets users revert to the existing behaviour and manually confirm channel creation on a case-by-case basis. An Android notification is displayed if needed to let users react in time.

Custom default description

Default payment description is now empty, and can be changed by users.

Intro screens

A short intro has been added for new installs, with 3 screens containing information about the automatic channel creation mechanism (including price) and the seed.

Payment metadata

Payments for swap-in/swap-out, or payments that open/close channels will now contain a bit more information, like the on-chain address, or the fee cost for opening a channel.

Mempool.space on-chain explorer

Users can now use either Blockstream.info or Mempool.space (now the default explorer).

Faster start

Wallet will use its last known feerates when bootstrapping.

Complete list of changes

Thanks @ibertario @mautematico @bitcoinuser @fiatjaf for their contributions.

Verifying signatures

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

To import our signing key:

$ gpg --import padioupm.asc

To verify the release file checksums and signatures:

$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped

Phoenix 1.3.2

01 Aug 13:22
6f42e54
Compare
Choose a tag to compare

Changes

Custom feerates for swapout (lightning -> on-chain address)

The app lets the user change the fee rate used when requesting a swapout to the peer, instead of using a hardcoded 6 blocks target. The user can now enter a sat/bytes fee rate after clicking on an Edit fees button, and the app estimates an ETA in hours when the fee rate changes.

Support for LNURL authentication

The app can now leverage its key to sign-in to services supporting LNURL-auth. More details are available here: https://xn--57h.bigsun.xyz/lnurl-auth.html

Note that the node key is not leaked by LNURL auth. See this PR for implementation details: #74

Opt-in SSL for electrum over Tor

When connecting to an .onion electrum server, the user can also force the app to check the server's certificate. This is opt-in.

Deterministic build

The APK is built deterministically using Docker. Follow these instructions to build the APK. This build system has been upgraded from v1.3.1 and is easier to user. Only Docker is required.

Note that it's strongly recommended on Windows at least to increase the memory allocated to Docker.

Complete list of changes

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