Phoenix Android 2.3.4
ℹ️ 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
Fixed compatibility issue with some BOLT12 offers
See ACINQ/lightning-kmp#686 #593
Improve Bip353 and Bip21 support
Several issues regarding Bip353 compliance have been fixed, including displaying or copying the ₿ prefix when relevant. When an address is prefixed with ₿ Phoenix will not fallback to LNURL.
Error messages for invalid bip353 addresses have been improved.
Also fixed support for Bip21 URIs containing a lno offer parameter. Behaviour now matches Bip21 URIs containing a lightning parameter (for Bolt11 invoices).
Payer-key behaviour is now set per contact
When creating (or editing) a contact, users can now choose whether a random payer key or their offer key should be used to pay this contact. The global option payer key in Settings > Payment options has been removed.
When paying an unknown offer, Phoenix always uses a random payer key.
Compatibility with Lightning address
Phoenix can still pay LNURL-based lightning addresses. If the user tries to pay an email-like address, Phoenix will first perform a DNS lookup, then if it fails, attempt a LNURL request.
Full changelog
- phoenix: android-v2.3.3...android-v2.3.4
- lightning-kmp: ACINQ/lightning-kmp@v1.7.1...v1.7.2
Thanks @MasterixCZ and @escapedcat for the localisation update.
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
