ℹ️ Migration for existing legacy wallets (v1.x)
Users upgrading from the legacy 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
Request inbound liquidity from your peer (#489)
If you keep receiving funds over Lightning, you'll consume your inbound liquidity fast and may end up having to splice-in every incoming LN payments, which can be expensive because each splice is an on-chain transaction. By requesting liquidity from the peer, you can plan ahead and avoid future on-chain fees. This is now supported in Phoenix starting from 2.1.0, thanks to liquidity-ads (a new feature in the Lightning protocol).
Requesting liquidity is done manually (for now at least). A button to the liquidity screen has been added in the Home screen. Your inbound liquidity is also displayed in the channels view.
Full changelog:
- phoenix: android-v2.0.15...android-v2.1.0
- lightning-kmp: ACINQ/lightning-kmp@v1.5.12...v1.5.14
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