Phoenix Android 2.0.6

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Phoenix Android app (1.x) to 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.5

Fixed several issues related to LNURL

• withdrawals will now offer the user to withdraw the maximum amount available, instead of the minimum;
• LUD-17 urls (starting with lnurlp, lnurlw, keyauth) are now properly parsed.

The Czech translation has been improved

Thanks @MasterixCZ and @margre8 for working on this.

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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.5

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Phoenix Android app (1.x) to 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.4

Added localisation for 🇩🇪 German, 🇪🇸 Spanish, 🇵🇹 Portuguese and 🇨🇿 Czech localisation.

Thanks @myxmaster for the help with German translation!

Spanish, Portuguese, and Czech localisation are partial, and may not be accurate. However, it's still better than just displaying English.

Handle callback action for sucessful LNURL payments

Also, LNURL payments made prior to this version should display the successAction result correctly. See #404.

Add warning regarding legacy swap addresses

For users who migrate from v1.4.x, warnings have been added about reusing legacy swap-in addresses. These addresses should not be used anymore after migration. The new wallet will only support the new address displayed in the receive screen.

If an old legacy address has benn used after the migration is done, contact support: phoenix@acinq.co

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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.4

Migration for existing legacy wallets (v1.x)

For users upgrading from the legacy Android app (1.x) to Android 2.x, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Changes from 2.0.2

This release fixes several issues and brings a few improvements in the app.

Swaps are now attempted at each block

Previous versions required the app to be restarted in order to attempt pending swap-ins. This is not the case anymore, the app will attempt swaps at each new block. System notifications for failed swaps have been reduced to prevent spam.

Added link to scanner in receive screen

Receiving funds over LNURL required users to click on Send in order to open the scanner, which is counterintuitive. This has been fixed by adding back the "Use LNURL link" button in the Receive screen, like in the legacy app.

Other

• Reconnecting to the Peer and the Electrum servers should be snappier
• Fixed an issue where connection to the Peer would not be made (#400)

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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

Android v2.0.2

This release bumps the minimal Android version to android 8+ to prevent installing the app on old, incompatible devices.

Users with Android 7.1 or older can still use version 1.4.27, but we strongly recommend upgrading to a recent Android version that receives security patches.

Migration for existing wallets

For users upgrading from the legacy app (1.x) to the new app, a migration is needed. See the 2.0.0 release notes for details about the migration process.

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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

Android v2.0.1

This release fixes an issue (see #394) with withdrawals/payments done through LNURL affecting the new 2.0.0 version (legacy app is not affected).

Migration for existing wallets

For users upgrading from the legacy app (1.x) to the new app, a migration is needed. See the 2.0.0 release notes for details about the migration process.

All changes:

• android-v2.0.0...android-v2.0.1

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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

Android v2.0.0

This is a major release that reworks most of the application. An automated migration is available for existing users.

Migration

Due to the changes in the LN engine and the switch to splicing (see below), existing channels created with v1.x cannot be used by the new app. A migration process merges them together resulting in a single channel.

Users with existing wallets will remain on the legacy app, until their funds are migrated. This migration is triggered manually by the user from the legacy app.

⚠️ Important notes

• The migration process will only migrate channels that have at least 546 satoshi on the user's side. Channels with less than 546 sat cannot be migrated since their balance is below the Bitcoin dust limit, and funds are swiped by the miners. The app will display a warning when that's the case.
• Once the app has migrated, the legacy swap-in address must not be used ever again. Contact support if you accidentally send funds to the legacy swap-in address.
• The migration process may sometimes be disabled, usually when the mempool is congested. When that happens, the migration button is not available, and users can keep using the legacy app.

Main changes

Switch the LN engine from eclair to lightning-kmp

Both eclair and lightning-kmp are implementations of a Lightning node and are developed by us (ACINQ). However eclair is written in scala, targets server use-cases (relaying payments) and only runs on Android. Lightning-kmp is written in kotlin multiplatform, targets mobile platforms, and can run on iOS and Android.

Phoenix Android used to be powered by eclair, and Phoenix iOS by lightning-kmp. With this new versions, both Android/iOS use lightning-kmp.

Support for splicing and dual-funding

Splicing allows altering channels by adding or removing funds. Instead of managing multiple channels, the app only has one single channel, which will then be modified depending on usage. This brings significant improvements:

• on-chain swaps (swap-in or swap-out) are now trustless.
• the static 1% fee for incoming payments that need new channels has been removed. Instead users pay the mining fee for the splicing operation.
• that fee cannot exceed the maximum fee set by the user (in settings > channels management). Default maximum is 5000 sat.
• a notification is displayed when an incoming payment is rejected because of the fee.
• the fee for outgoing Lightning payments is now static (0.4 %) and is displayed before sending the payment.
• unconfirmed on-chain transactions can be accelerated.

See #356 and https://acinq.co/blog/phoenix-splicing-update for more information, especially the fee comparison.

Improved fiat currencies support

The Android app is now able to convert prices to 150+ currencies, including free market rates (like for the Argentine Peso). Exchange rates should also be more accurate.

Export payments history

Successful payments can now be exported to a CSV file.

Compatibility with iOS

The iOS and Android apps are not compatible yet, since the iOS app does not support splicing yet. Using the same seed on both iOS and Android Phoenix apps will lead to issues.

All changes

android-legacy-v1.4.27...android-v2.0.0

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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 v1.4.27

This release fixes a display issue, where the decimal parts of amounts denominated in Btc/mBtc/bits units were hard to read. These parts are now correctly aligned.

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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 v1.4.26

Add full payment history

A new screen has been added to list the full payment history. The home screen will now only display the last dozen payments, plus a button to open that full history screen.

Support phoenix scheme

Third-party apps that want to specifically open the Android Phoenix app can do so with an intent with the phoenix scheme (e.g. phoenix:lightning:lnbc1...).

• (phoenix-legacy) : android-legacy-v1.4.25...android-legacy-v1.4.26

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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 1.4.25

Fix LNURL-auth for bolt.fun

Phoenix will now use the compatibility scheme when authenticating with bolf.fun, instead of the regular scheme.

• (phoenix-legacy) : android-legacy-v1.4.24...android-legacy-v1.4.25

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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 1.4.24

Use services' full domain name with LNURL-auth

Phoenix is now using the service's full domain name (like in the LUD-04 specifications) when creating the LNURL-auth linking key. For existing services where users may already have accounts on, Phoenix keeps using the etld+1 domain name so that those accounts are still accessible.

• (phoenix-legacy) : android-legacy-v1.4.23...android-legacy-v1.4.24
• (eclair-core) : ACINQ/eclair@v0.4.16-android-phoenix...v0.4.17-android-phoenix

Verifying signatures

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

• from our website: https://acinq.co/pgp/drouinf.asc
• from github user @sstone, a committer on eclair: https://api.github.com/users/sstone/gpg_keys

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