1. Receiving vs. Sending on Phoenix Phoenix Wallet…
1 reactions
1. Receiving vs. Sending on Phoenix
Phoenix Wallet automatically manages Lightning channels. Upon the first receipt, it must open a channel, which incurs fixed fees (channel fees + mining fees). This is why a small payment of 3000 sats can be significantly reduced. On the other hand, sending small amounts (for example, 500 sats) is not a problem, as only the Lightning routing fees apply, and these remain minimal.
2. Fee Evolution After Channel Opening
Once the channel is open, receiving fees become much lower (around 250 sats). This means that Phoenix is best suited for regular or medium-sized payments: the first receipt is expensive, but subsequent ones are proportionally much more advantageous. Micro-payments then become possible without the fees consuming the entire amount.
3. Native SegWit vs. Encapsulated SegWit
The difference in fees between native SegWit (bc1 addresses) and encapsulated SegWit (3 addresses) stems from transaction size. The bech32 (native) format is more compact and optimizes mining fees (~300 sats), while the P2SH (compatibility) format is larger (~400–500 sats). Phoenix prioritizes native SegWit to reduce costs, but depending on the routing, it may sometimes use P2SH, which explains the observed variations.
Phoenix Wallet automatically manages Lightning channels. Upon the first receipt, it must open a channel, which incurs fixed fees (channel fees + mining fees). This is why a small payment of 3000 sats can be significantly reduced. On the other hand, sending small amounts (for example, 500 sats) is not a problem, as only the Lightning routing fees apply, and these remain minimal.
2. Fee Evolution After Channel Opening
Once the channel is open, receiving fees become much lower (around 250 sats). This means that Phoenix is best suited for regular or medium-sized payments: the first receipt is expensive, but subsequent ones are proportionally much more advantageous. Micro-payments then become possible without the fees consuming the entire amount.
3. Native SegWit vs. Encapsulated SegWit
The difference in fees between native SegWit (bc1 addresses) and encapsulated SegWit (3 addresses) stems from transaction size. The bech32 (native) format is more compact and optimizes mining fees (~300 sats), while the P2SH (compatibility) format is larger (~400–500 sats). Phoenix prioritizes native SegWit to reduce costs, but depending on the routing, it may sometimes use P2SH, which explains the observed variations.
1
| 20,000 mlx | |
| 31 | |
| 1 |