I don't think so. Other wallets use hosted LSPs. Look into nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5
Discussion
I mean changing Phoenix code so it opens channels to a different hardcoded node instead of the acinq node. They have Apache 2 license, no clue if this would allow it.
It's not as simple as opening a channel to a new node. Phoenix is tightly integrated with the ACINQ LSP which handles liquidity management, splicing, pathfinding, and probably a bunch more stuff I am not even aware of.
Even with all of that functionality the biggest thing you lose out on by forking Phoenix is the accumulated technical expertise at ACINQ.
Try Breez, Mutiny, Zues. Or run your own node. All vastly easier than trying to fork Phoenix and make it work.
I could be wrong tho. Try it out and see how far you can get. 🤷
Ah ok I didn't consider the logic running on the LSP side and thought it just have to be a regular Eclair node. There is probably some non open source secret sauce needed.
In regards to know how I just would pull upstream changes from original phoenix?
Nevertheless this is purely theoretical (for me) as I have neither the skill nor the capital needed to run this infrastructure.
That should absolutely work, but a big part of what makes Phoenix useful to end users is ACINQ's big, well connected node with on-demand liquidity.