pull down to refresh

I recently got recommended Phoenix Wallet.
Please tell me I'm overlooking something. The complete lack of control over lightning/onchain is baffling. And expensive, it can become accidentally expensive. Can I open channels to people I know somehow?
deleted by author
reply
192 sats \ 1 reply \ @Scoresby 12 May
I concur. Use Phoenix a lot. It's very simple LN with a focus on ease of use.
accidentally expensive
Because you have only the one channel with acinq's node, if you receive more than your inbound, it will automatically splice for you (even if on chain fees are high). If you aren't paying attention a small LN receive can cause an on chain txn. They have a setting for limiting how much you are willing to pay in fees, but it can be a footgun if you aren't careful.
Also, because they allow you to send out to on chain from your LN channel (via splicing) you might wreck your inbound if you don't understand LN liquidity.
I've seen people pay for inbound liquidity, receive maybe half, and then send out to on chain not understanding that the splice will resize their channel and decrease their inbound. They could explain it better in the app.
Overall though, its a good wallet that rarely has issues with failed payments. Highly recommend.
reply
deleted by author
reply
I understand the simplicity of a single channel.
Buuut a single channel is a dead end. You need at least 2 channels for sats to have the ability to be moving at all. Otherwise someone is investing in my channel with no return. It's wasted and locked up money.
reply
deleted by author
reply
It's not about me and not about "earning". A word I did not use but it says a lot about you that that's where your mind goes.
Sats in channels that are a dead end are a waste for the network.
reply
127 sats \ 1 reply \ @orthwyrm 12 May
deleted by author
reply
I literally have a masters degree in IT sec. What are you talking about.
reply
Are you using Phoenix for sending and receiving here once they do the switch-over?
reply
Switch-over?
reply
deleted by author
reply