Releases: ACINQ/phoenix
Phoenix Android v2.3.9
Changes
This release fixes a few UI issues, including a fix for #616 which prevented scanning QR codes for Lightning addresses when they used an URI prefix.
Legacy mode and channels closing
Phoenix v2 was released 1 year ago and v1 legacy channels will soon be closed. The v2 upgrade notices in the v1 legacy mode have been updated. Users that are still using the legacy mode should migrate as soon as possible. Note that this migration to v2 is automated, and free.
Users using v2 (that is, most people) are not affected. Check the Settings > About screen to verify what version you are using.
Full changelog
- phoenix: android-v2.3.8...android-v2.3.9
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
Contributors
Assets 4
Android v2.3.8
ℹ️ 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 fixes an issue related to the legacy mode which could crash the app, and improvements to the navigation and the screen lock system.
Full changelog
- phoenix: android-v2.3.7...android-v2.3.8
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
Contributors
Assets 4
Android v2.3.7
ℹ️ 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
Full changelog
- phoenix: android-v2.3.6...android-v2.3.7
- lightning-kmp: ACINQ/lightning-kmp@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
Contributors
Assets 4
Phoenix Android v2.3.6
ℹ️ 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 parsing issues with BIP353 addresses and BIP21 URIs
Full changelog
- phoenix: android-v2.3.5...android-v2.3.6
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
Contributors
Assets 4
Phoenix Android v2.3.5
ℹ️ 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 parsing issue with some BIP353 addresses
Additional parameters in the URI caused parsing issues.
Add new option of 1 hour and 1 day for the invoice expiry
Some services (e.g. the Kucoin CEX) require expiry below 3 days. The default value is still 1 week.
Full changelog
- phoenix: android-v2.3.4...android-v2.3.5
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
Contributors
Assets 4
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
Contributors
Assets 4
Phoenix 2.3.3
ℹ️ 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
Add support for BIP353 DNS addresses
Phoenix now support paying BIP353 DNS addresses. The lookup is done through the google dns resolver, and we'll add other resolvers soon.
For reference, BIP353 DNS addresses can allow users to store their offers as a DNS TXT record on a domain. A wallet can then perform a DNS lookup (DoH) on that domain and get the offer for a given user, without directly contacting the domain.
It allows users to have a user@domain email-like handle, which are much easier to share with friends or on social networks than a BOLT12 offer.
As an experimental feature, Phoenix can also create a random BIP353 address on a domain provided by the LSP (phoenixwallet.me). Users can also self-host their offer on their own domain, or use third-party services.
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.1...android-v2.3.3
- lightning-kmp: ACINQ/lightning-kmp@v1.7.0...v1.7.1
Thanks again @MasterixCZ and @jooray 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
Contributors
Assets 4
Phoenix 2.3.1
ℹ️ 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
Add support for BOLT12 offers
Offers are the Lightning equivalent to a Bitcoin address: it's a reusable, static payment request that can be used for donation use cases, or to easily pay/get paid by your friends.
Since BOLT12 is not yet well supported, Phoenix will keep displaying a BOLT11 invoice by default.
Custom messages
When paying an offer, the user can attach a custom message (max 64 chars) that will be delivered to the offer's recipient along with the funds.
Background processing limitation
Since offers are typically paid without the recipient being active on his device, a few warnings have been added so that users are made aware of limitations.
For example, Phoenix relies on Google FCM to deliver wake-up notifications to the recipient. If FCM is disabled or unavailable on the device (for example, on a GrapheneOS fresh installation), then the user will not be able to receive payments in the background. Same for Tor.
Contacts UI (Android only for now)
A new UI has been added to create, list and manage contacts, which are a way for Phoenix to attach an offer to a name. See #575 for screenshots.
Note : These contacts are isolated from the device's system contacts. If there's demand for it, a later update could let Phoenix link offers to the device's contacts, provided the user grants permissions.
Full changelog
- phoenix: android-v2.2.4...android-v2.3.1
- lightning-kmp: ACINQ/lightning-kmp@v1.6.3...v1.7.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
Contributors
Assets 4
Phoenix Android 2.2.4/iOS 2.2.6
ℹ️ 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:
- phoenix: android-v2.2.3...android-v2.2.4
- lightning-kmp: ACINQ/lightning-kmp@v1.6.2...v1.6.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
Contributors
Assets 4
Phoenix Android v2.2.3
ℹ️ 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:
- phoenix: android-v2.2.2...android-v2.2.3
- lightning-kmp: ACINQ/lightning-kmp@v1.6.1...v1.6.2
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