::: faq-entry
# Can I run two Phoenix apps with the same seed?

Running simultaneously two apps on the same seed is not recommended, because channels will be shared between the two instances. This could cause issues and payment channels might close.

Note: to recover funds from force-closed channels, follow [these instructions](#my-channels-got-force-closed-how-do-i-recover-my-funds).
:::

::: faq-entry
# Can I connect to any node? Can I connect to my own node?

Phoenix has been designed for less technical users, who don't know or want to run an always-on Lightning node on a server or to manage channels, with sensible trade-offs for those users.

There is [some trust involved](#is-phoenix-trustless) with Phoenix, which would make connecting to random nodes on the internet unsafe.

On the other hand, if you have the technical knowledge to run your own always-on Lightning node (therefore removing the trust assumption), then you do not need other trade-offs made with Phoenix and would be better off with a "remote-control" app to your Lightning node. This is a valid setup for more advanced users, who are not the target audience for Phoenix.
:::

::: faq-entry
# Is Phoenix affected by high on-chain fees?

Sending payments over Lightning is not affected by high on-chain fees.

However, there are some features of the wallet that require on-chain transactions:

- Incoming on-chain payments (and some incoming off-chain payments) may be more expensive than usual. They may even be rejected to avoid excessive cost, depending on your configuration. See [this entry for details](#incoming-payments-are-rejected-because-of-fees-what-can-i-do).
- Paying on-chain addresses may be more expensive than usual, but you can set [you own feerate](#can-i-set-the-feerate-when-sending-on-chain) when paying.
:::

::: faq-entry
# Why do I need Google services on GrapheneOS?

Phoenix relies on Google Firebase Cloud Messaging (FCM) to deliver wake-up notifications to Phoenix. This allows you to receive payments even when Phoenix is in the background, or closed. It is also used to [settle pending payments](#can-i-cancel-an-outgoing-pending-payment) and prevent force-closures.

On GrapheneOS, by default there's no Google services, so these notifications won't work as-is. To fix that, GrapheneOS provides a sandboxed Google Play Services app that [must be installed manually](https://grapheneos.org/usage#sandboxed-google-play).

If you do not want to install this sandboxed app, then Phoenix will not receive the wake-up notifications. Phoenix will work fine as long as the app is active, but if it's in the background or closed, payments might fail. As a workaround, you can tweak the battery settings for Phoenix, so that it's not eagerly killed by the OS. With some luck, it's possible to avoid most issues with background payments (though that won't help if Phoenix is closed).
:::