Skip to content

Releases: ACINQ/phoenix

Phoenix Android 2.2.4/iOS 2.2.6

18 Jun 15:57
801e1b3
Compare
Choose a tag to compare

ℹ️ Migration for existing Android legacy wallets (v1.x)

Users upgrading from the legacy Android app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

This release is a bug fix release, no new features have been added.

Fixed regression causing payment failures when on-the-fly liquidity is needed

This prevented receiving payments over Lightning with low liquidity, because the on-the-fly channel creation would fail.
See ACINQ/lightning-kmp#672 for details

Bug fix on connection establishment

Fixed a rare race-condition during connection establishment causing the app to stay disconnected. See ACINQ/lightning-kmp#668.

Full changelog:

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

Phoenix Android v2.2.3

11 Jun 11:43
0179adf
Compare
Choose a tag to compare

ℹ️ Migration for existing Android legacy wallets (v1.x)

Users upgrading from the legacy Android app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

Added +-5% buttons to easily add a tip when paying over Lightning

The user can also enable/disable overpayments in the app settings. See #541.

Improve payment error messages

See ACINQ/lightning-kmp#634 & ACINQ/lightning-kmp#616

Added new messages regarding liquidity

New disclaimers and confirmation messages have been added to detail how liquidity works (e.g., when sending a payment on-chain).

Also, the sanity check warning displayed when the total fee is more than 25% of the liquidity requested is more prominent.

See #539.

Added a screen to spend expired swap-ins

On-chain deposits that have not been swapped in time (~4 months) can now be recovered from within Phoenix, instead of having to perform a manual recovery. See #564.

Several improvements and fixes

A fee warning visible in the Receive screen is now also shown when performing a withdrawal over LNURL.

Thanks @MasterixCZ for updating the Czech translation.

Full changelog:

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

Phoenix Android/iOS v2.2.2

10 Apr 14:15
97a7532
Compare
Choose a tag to compare

ℹ️ Migration for existing Android legacy wallets (v1.x)

Users upgrading from the legacy Android app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

Update fee estimation for on-the-fly channel

The fee for on-the-fly channel is now 1% + mining fee, same as the fee for the manual liquidity request.

(ios) Support for importing localised seed

Phoenix can now import seeds in English, French, Spanish, Czech. Default is English. Using an alternative language for the seed is experimental, we recommend sticking to English for now.

(ios) Fix for background reception payment

Receiving payments with the app in the background has been improved, success rate should be higher.

Full changelog:

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

Phoenix Android v2.2.1

07 Mar 09:58
a1e5663
Compare
Choose a tag to compare

ℹ️ Migration for existing Android legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

This is mostly a bug fix release, with also some UI improvements and new localisations.

🇸🇰 Slovak and 🇻🇳 Vietnamese localisation

Thanks @jooray and Vân for their contribution.

Settle in-flight payments in the background

When needed, Phoenix will run a background job to try to settle in-flight payments (incoming or outgoing). The objective is to avoid payment timeouts when the wake-up push notification from the ACINQ node fails. This is especially useful for devices that don't support FCM notifications.

See #522 for details.

Full changelog:

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

Phoenix Android/iOS v2.2.0

23 Feb 18:37
43bd103
Compare
Choose a tag to compare

ℹ️ Migration for existing Android legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

Use taproot addresses by default, and rotate addresses

The address displayed by Phoenix for on-chain to Lightning swaps is now a Taproot address. This address is not static anymore. Phoenix will generate a new swap-in address upon receiving a transaction. This improves privacy, and also makes deposits cheaper.

See our blog post for more information: http://acinq.co/blog/phoenix-swaproot

Already used address are listed in Settings > Wallet info > Swap-in addresses.

If need be, users can switch back to the static, native segwit legacy address in Settings > Payment options (on Android) or Receive > on-chain > Edit (on iOS).

Support for quiescence

Phoenix can now splice (in/out) a channel while a Lightning payment is in-progress.

See ACINQ/lightning-kmp#568 and ACINQ/eclair@47e0b83 for details.

Upgrade of internal tools

This is not visible to the users but the app (and all the lightning/bitcoin dependency suite) has been upgraded to kotlin 1.9, and a new logging framework.

Full changelog:

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

Phoenix Android v2.1.3

09 Feb 12:24
eacb4f0
Compare
Choose a tag to compare

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Minor changes

  • The fee warning displayed in the Receive screen when creating a LN invoice is more prominent (see issue #507).
  • The feerate warning when sending an on-chain payment is skipped when the feerate is high enough.

Full changelog:

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

Phoenix Android v2.1.2

24 Jan 18:51
0713f1b
Compare
Choose a tag to compare

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

This is a bug fix release, containing mostly fixes in lightning-kmp, except for a new message displayed when sending an on-chain transaction while using a low feerate.

Full changelog:

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

Phoenix Android v2.1.1

20 Dec 13:15
7d338cd
Compare
Choose a tag to compare

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

This minor release fixes the Czech translation (#490, thanks @MasterixCZ) and English typos (#491 thanks @dluvian). It also bumps the feerate used for liquidity requests to help with the current high fees environment.

Full changelog:

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

Phoenix Android v2.1.0

15 Dec 16:45
36d7baa
Compare
Choose a tag to compare

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Changes

Request inbound liquidity from your peer (#489)
If you keep receiving funds over Lightning, you'll consume your inbound liquidity fast and may end up having to splice-in every incoming LN payments, which can be expensive because each splice is an on-chain transaction. By requesting liquidity from the peer, you can plan ahead and avoid future on-chain fees. This is now supported in Phoenix starting from 2.1.0, thanks to liquidity-ads (a new feature in the Lightning protocol).

Requesting liquidity is done manually (for now at least). A button to the liquidity screen has been added in the Home screen. Your inbound liquidity is also displayed in the channels view.

Full changelog:

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

Phoenix Android v2.0.15

12 Dec 14:56
b662f03
Compare
Choose a tag to compare

ℹ️ Migration for existing legacy wallets (v1.x)

Users upgrading from the legacy app (1.x) to 2.x will need to migrate to be able to use 2.x features. See the 2.0.0 release notes for details about the migration process. You can see what version you are currently using in Settings > About.

Hotfix release

This release fixes an incorrect error message displayed when opening the Send screen (#487).

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