PhoenixD use cases #28
Replies: 4 comments 2 replies
-
|
The use case is to make it easy for a service/business to receive/send LN payments, while being self-custodial, and never have to manage liquidity/channels. It's a different product than Phoenix Wallet - even though it's based on the same stack, and use some of the same concepts. Take a look at the phoenixd FAQ for details, as well as the Auto liquidity page.
No, see: https://phoenix.acinq.co/server/faq#can-i-share-the-same-seed-between-several-instances-of-phoenix |
Beta Was this translation helpful? Give feedback.
-
|
I know you say you cannot reuse on a diff instance but if you completely remove the original instance and only have one instance on a lets say a diff server can you at that point reuse the seed? |
Beta Was this translation helpful? Give feedback.
-
|
If you could control PhoenixD from the Mobile App, then you would have an awesome experience. Transfer the phone instance to a PhoenixD instance and then switch to controller mode in the Phone App. |
Beta Was this translation helpful? Give feedback.
-
|
Anyway to build this multiple times on the same server serving different end users on a shared server? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello.
Is PhoenixD's main use case for enterprise to setup a standalone server based always available Phoenix Wallet?
Can you run PhoenixD and the Phoenix mobile application simultaneously, essentially making your Phoenix mobile application always online? Or like most implementations will issues arise from having the same Lightning wallet open on two different devices?
Beta Was this translation helpful? Give feedback.
All reactions