... That's one of the reasons I like Phoenix Wallet so much: when I sent 420,000 sat, I got a channel with 420,000 sat (minus 0.1%) outgoing capacity, and also more than 200,000 sat incoming capacity. I didn't have to do anything. ...
OK... I'd heard of Phoenix LN Wallet a while ago, but hadn't done anything to investigate it until now. Not long after the above post I followed the github link and downloaded the Android APK, installed it
on a 7" tablet and then sent the bc1... wallet address
BTC 0.01
from my mobile phone's Eclair Wallet as I'd briefly read that Phoenix is based on Eclair LN Wallet which I have been using for some time now.
(Just as an aside, none of the Eclair LN channels values on my mobile phone have changed for many weeks).
I'd paid 20sats/byte TX fee and not long later I discovered 999,000 sats had been created into a channel
(The channel connects where to? No idea at this point) with ~3,750 INBOUND capacity inbuilt into the single channel.
Having probably misread the above post, I waited 24 hours and no additional channels (with inbound capacity) were created, so I sent 100,000 to a LN wallet on another device.
Another 24 hours went by and still no inbound channels were created, so I sent via LN (from a secondary LN source) ~2,500 sats bringing the balance just above 902,000 sats. But no secondary LN channel was forthcoming.
The next day, I sent the Phoenix Wallet
BTC 0.001 from a different wallet to all previous sources thus far to a bc1... wallet address rolled by the App. After generating the wallet address, I shut the program down and left it closed until after the funds had had a number of confirmations.
12 hours ago, roughly 12 hours after sending the
BTC 0.001 I opened the Phoenix Wallet and got a near instant message stating the funds had arrived via the bc1... wallet address.
However, when I went into the channel list I discovered a second LN channel has been opened but with 99,900 sats outbound AND ~122,000 sats inbound capacity in the one channel.
on reviewing the wallet address in mempool.space (their linked block explorer) I can only see one inbound and one out bound transaction
cancelling my theory the other side sends funds to jointly open a channel then sends funds out to create inbound capacityHowever #2 the outbound TX has three wallet addresses sending funds to another (two) addresses. I suspect one very close to the combined inbound/outbound/TX fee is "my" transaction which then lends me to suspecting Phoenix co-creates it's channels using your and their funds.
Which makes me wonder just how "custodial" Phoenix really is?
Unfortunately, as with the Eclair LN Wallet I seem to be in the same predicament in that as soon as the screen goes dark, the program goes into hybernation and the channels effectively go off-line (so I can't run Phoenix as a node on my tablet)
I also can't open channels to whomever I want to either, so (if my five week (and counting!!) TX from one Zap wallet to another Zap wallet ever gets confirmed) I'll be back to creating a series of Zap LN channels which I can keep open on my PC.
(mumble Now that I have a working PC again... mumble)