ℹ️ 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

Support for custom PIN

The application can now be protected with a custom 6-digits PIN code specific to Phoenix. This PIN can replace or coexist with the user ScreenLock that is attached to the Android user account (and usually using biometrics).

Improved compatibility with BOLT12 payments

See https://github.com/ACINQ/lightning-kmp/pull/694

Full changelog

• phoenix: https://github.com/ACINQ/phoenix/compare/android-v2.3.6...android-v2.3.7
• lightning-kmp: https://github.com/ACINQ/lightning-kmp/compare/v1.7.2...v1.7.3

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