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
