dpad85

@robbiehanson this should be fixed by 58d67c8c614d05ad95a4f3d67b0106eae7dbcc27 (we should not fallback to LNURL if there's a `₿` prefix).

Testnet4 support is not ready yet. It should be available soon™. For now, you will not be able to make Testnet4 payments on Phoenix. Testnet3 still kinda works, though you...

We do plan to use testnet4. We are waiting for https://github.com/bitcoin/bitcoin/pull/29775 to be merged and the update formalised, then we'll switch.

Regarding the feerate, it's been fixed with commit 081e5898. You can download the APK here: https://acinq.co/pub/phoenix/phoenix-testnet-latest.apk @robbiehanson The iOS app will keep using the mainnet feerate in some places (cf...

There are several ways to do that: **option 1** 1 seed with customisable derivation paths or a passphrase. It sounds good because you only have to remember 1 seed, but...

The "send" view is going to be reworked. It was designed around a bolt11 payment flow where most of the time you had to scan a QR code to do...

These two URIs are rejected because they mix a `lightning:` prefix with a LNURL-based address. This seems the correct behaviour to me, the expected format is `@`. The whole point...

> The reason why we prefer to prefix `lightning:` to Lightning addresses is that otherwise, when people scan a Lightning address with their phone's integrated camera, they get directed to...

You can do that on Android : Settings > My contacts > `+`, and tap the QR code icon in the Offer input. On iOS, you can't open the scanner...

Choosing to pay with Lightning or on-chain is not just about the fees. Lightning is not just a cheaper on-chain, it brings valuable features: a payment made over Lightning is...