Releases: ACINQ/phoenix
Phoenix v1.4.5
Main changes
Closing logic is cooperative when we have nothing at stake
More information here: ACINQ/eclair#1633
Add links to terms
A link to the terms (explaining how the wallet works and what can be expected) has been added to the about and initialization screens.
Complete list of changes
Thanks @bitcoinuser for updating the Portuguese-Brazilian translation.
Verifying signatures
You will need gpg and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Contributors
Assets 4
Phoenix 1.4.4
Main changes
Support for lightning parameters in BIP21 invoices
BIP21 URIs can contain a lightning field if the recipient also accepts lightning payments. In that case the wallet now lets the user choose how he wants to pay the invoice.
Improve swapout feerate
Minimum feerate for swapout is now dynamic and should adjust with the state of the mempool.
Complete list of changes
- app: v1.4.3...v1.4.4
Verifying signatures
You will need gpg and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Contributors
Assets 4
Phoenix 1.4.3
Main changes
Fixed some connection issues with peer
Use ip address instead of domain name to connect to the trampoline node. This caused connectivity issues in some cases, due to IPv6 conversion.
Complete list of changes
Verifying signatures
You will need gpg and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Contributors
Assets 4
Phoenix 1.4.2
Main changes
Fixed some "route not found" errors
There was an issue where channels with less than 15 000 satoshis were ignored by the path-finding algorithm, which could prevent payments from going through and incorrectly trigger a "Route not found" error.
Complete list of changes
Thanks @bitcoinuser for updating PT-BR translation.
Verifying signatures
You will need gpg and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Contributors
Assets 4
Phoenix 1.4.1
Main changes
Customizable max fees for outgoing Lightning payments
Users can now change the maximum fees that the trampoline node can use for outgoing LN payments. In some cases, the default setting may not be sufficient so the user can try higher fees. Note that the trampoline node will always try to use as low fee as possible. Also, setting a super high fee will not help if the recipient is simply not reachable (no channels/no connection) or does not have enough inbound liquidity.
This setting is available in Setting > Payment settings
Better error messages for failed payments
Some error messages are rewritten to be more explicit and provide guidance to users.
Small channels are more resilient to high fee environment
Channels inbound capacity is also displayed in the wallet's channels list.
Complete list of changes
Thanks @bitcoinuser for updating PT-BR translation.
Verifying signatures
You will need gpg and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Contributors
Assets 4
Phoenix 1.4.0
Main changes
Background payment reception
The app can now wake up to process an incoming payment or a fulfilled HTLC. Users do not have to start their app manually to receive a payment, thus removing the synchronization requirement between sender and receiver. This feature uses Firebase Cloud Messaging. Messages relayed by FCM do not contain any details about payments.
When the wake up message arrives, a sticky notification is displayed. The peer will pause the payment and wait ~20/30 seconds for the app to accept the payment, or fail the payment downstream. If the payment succeeds, the notification will show the amount received.
Access control changes
The seed is now encrypted using a new improved format leveraging the Android Keystore to protect the seed and allowing the node to run background tasks. The device's TEE/SE will be used when possible. The legacy PIN used on existing wallets is deprecated and migrated to the new format after updating the app. Wallet is locked with the system screen lock (schema/PIN/fingerprint...).
An additional security setting is available, requiring users to authenticate with fingerprint each time the seed is decrypted. This setting may improve security on rooted device (*) but obviously disables background processing features.
(*) We don't recommend using Bitcoin wallets (except on Testnet) on a rooted phone.
Automatic channel creation
Channels are now created automatically. A setting lets users revert to the existing behaviour and manually confirm channel creation on a case-by-case basis. An Android notification is displayed if needed to let users react in time.
Custom default description
Default payment description is now empty, and can be changed by users.
Intro screens
A short intro has been added for new installs, with 3 screens containing information about the automatic channel creation mechanism (including price) and the seed.
Payment metadata
Payments for swap-in/swap-out, or payments that open/close channels will now contain a bit more information, like the on-chain address, or the fee cost for opening a channel.
Mempool.space on-chain explorer
Users can now use either Blockstream.info or Mempool.space (now the default explorer).
Faster start
Wallet will use its last known feerates when bootstrapping.
Complete list of changes
Thanks @ibertario @mautematico @bitcoinuser @fiatjaf for their contributions.
Verifying signatures
You will need gpg and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped
Contributors
Assets 4
Phoenix 1.3.2
Changes
Custom feerates for swapout (lightning -> on-chain address)
The app lets the user change the fee rate used when requesting a swapout to the peer, instead of using a hardcoded 6 blocks target. The user can now enter a sat/bytes fee rate after clicking on an Edit fees button, and the app estimates an ETA in hours when the fee rate changes.
Support for LNURL authentication
The app can now leverage its key to sign-in to services supporting LNURL-auth. More details are available here: https://xn--57h.bigsun.xyz/lnurl-auth.html
Note that the node key is not leaked by LNURL auth. See this PR for implementation details: #74
Opt-in SSL for electrum over Tor
When connecting to an .onion electrum server, the user can also force the app to check the server's certificate. This is opt-in.
Deterministic build
The APK is built deterministically using Docker. Follow these instructions to build the APK. This build system has been upgraded from v1.3.1 and is easier to user. Only Docker is required.
Note that it's strongly recommended on Windows at least to increase the memory allocated to Docker.
Complete list of changes
- app: v1.3.1...v1.3.2
- eclair-core: ACINQ/eclair@v0.3.8-android-phoenix...v0.3.10-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
Contributors
Assets 4
Phoenix 1.3.1
This release fixes several issues with the app startup that could trigger crashes.
Translations
This release also adds translations to Brazilian Portuguese and Dutch. Thanks @bitcoinuser, @M-BTC and @mautematico .
Deterministic build
The APK is built deterministically using Ubuntu 19.10. Follow these instructions to build the APK locally: https://github.com/ACINQ/phoenix/blob/master/BUILD.md
You should find this hash for the (unsigned) universal release:
bb0306f8f71b06fe4280152137fd9689c25e3e5d9706d5943cdd8a9611690787 outputs/apk/release/phoenix-11-1.3.1-mainnet-universal-release.apk
Complete list of changes
- app: v1.3.0...v1.3.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
Contributors
Assets 4
Phoenix 1.3.0
TOR support
The user can now connect to its Lightning peer/Electrum server over TOR. This feature is available from the Settings page. Note that some API calls (for example the API to retrieve the bitcoin/fiat exchange rate) will not use TOR. By default TOR is disabled.
The packaged tor libs (v0.4.2.5) are added to the project with the following checksum:
- arm64-v8a/libtor.so
9129f5184ac5b7da51345ca820c3bacd5fbe0e3586179028b186a4ea07de7e9a
- armeabi-v7a/libtor.so
9a33eeaeddd388f069bf39dd60c676e6016c39cbe1922a3fc19dd768a1814964
- x86/libtor.so
ecdf6d50989d0eb80aab7473430c06ca06df8aaefb9a0ac9e9761079a4df7129
- x86_64/libtor.so
4c4acd116985762e21438f2bd3168f506c7a5a250fd32e2619eda525b4b9d97c
Translations
This also brings translations to Czech, French, Italian, and Spanish. Thanks @pajasevi, @elkimek, @Mc33k, @simi, @Kixunil, @araspitzu and Javier L.M.
Deterministic build
The APK is built deterministically using Ubuntu 19.10. Follow these instructions to build the APK locally: https://github.com/ACINQ/phoenix/blob/master/BUILD.md
You should find this hash for the (unsigned) universal release:
8710aea2b1e90e4887464815495e5f0cf98146eb3e6db98a09e6168ff5c7b689 outputs/apk/release/phoenix-9-1.3.0-mainnet-universal-release.apk
Complete list of changes
- app: v1.2.0...v1.3.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 1.2.0
This release changes the fees mechanism used by the application to make it less expensive for smaller payments.
Lowered fees for on-the-fly channel opening and swap-in
The fees have been lowered down to 0.1%. This was made possible because we have:
- Increased the target confirmation for the funding tx from 6 blocks to 144 blocks. Note that this is a trust trade-off: funding tx will take more time to confirm, increasing the window during which we would be able to double spend it. However, note that during that window, you are still able to spend your entire balance with a LN transaction.
- Reduced the additional liquidity allocated on our side from 50% of the received amount to 30%.
Lightning fee retry mechanism
The app has switched from a pessimistic fee estimation to an optimistic one with a retry mechanism. Phoenix will now try to use as low fees as possible (1sat + 0.01%) when sending a payment, and if no route can be found on the network for this price, Phoenix will try again with a slightly increased fees, until reaching a maximum of 5sat + 0.12%.
Note that the given value may change in the future.
Complete list of changes
Verifying signatures
You will need gpg and our release signing key E434ED292E85643A. Note that you can get it:
- from our website: https://acinq.co/pgp/padioupm.asc
- from github user @pm47, a committer on eclair: https://api.github.com/users/pm47/gpg_keys
To import our signing key:
$ gpg --import padioupm.asc
To verify the release file checksums and signatures:
$ gpg -d SHA256SUMS.asc > SHA256SUMS.stripped
$ sha256sum -c SHA256SUMS.stripped