I still struggle to understands the concepts of inbound and outbound capacities. Say I open a fresh wallet with muun (non-custodial) and somebody want to send me 2 LNBTC. Would that work? Where is the bottleneck?
Discussion
Muun is not a lightning wallet, it's a swap provider.
Could you explain? I was wondering how that works! I always thought you need a node to have a lightning wallet. I assumed there is some light client thing going on, but please enlighten me.
Muun uses submarine swaps with chained HTLCs in zero-conf on-chain transactions (either 0 or both get confirmed, so it's “probably” safe). They run LN node in the middle to handle actual connection to other LN wallets, and handle all channels & liquidity. Your Muun corn are always on-chain, not on LN.
Phoenix is a proper LN node on mobile, but it works by only connecting to ACINQ LN nodes so they can still manage channels and liquidity. Phoenix corn are on LN proper.
If you want to manage own channels and liquidity, you need to run CLN or LND on a computer and manage via CLI, web GUI app, or mobile app (Zeus).
I once ran a raspiblitz but that was a while ago. I couldn't quite follow all of it, so I have to trust a bit more but generally it is fine? I mean LNBTC you use for micro payments, losing a few bucks is not a big deal compared to the convenience.
I don't like Muun personally. It's not Lightning, just plain old on-chain Bitcoin, and there's plenty better wallets for that. Would rather Phoenix (for carrying slightly more sats, say $100 worth), or Blue / Wallet of Satoshi (fully custodial, for carrying slightly less sats, say $10 worth).
interesting. Will probably have to do more research here.