The best Sundays are for long reads and deep conversations. Earlier this week, the Let's Talk Bitcoin! Show gathered to discuss Lightning Network technology and two innovative approaches at the wallet level which simplify the new-user experience at a tangible, but seemingly minimal cost.
In today's podcast we zero in on the challenge of "Channel Management", an until-recently-mandatory and manually-managed part of connecting to and utilizing the still-nascent Lightning Network.
A little context: The way Andreas (someone already using Lightning) sends a payment to Stephanie through Lightning is either through a direct channel to her or through a route of hops that can eventually reach Stephanie.
But if a user is brand new to the Lightning network, how do they go about receiving their first payment? - This question has been answered by both ZAP wallet and Phoenix wallet, using different techniques.
This episode of Let's Talk Bitcoin! is sponsored by Brave.com, eToro.com and Purse.io.
Lightning Topic Notes:
Phoenix wallet is made by ACINQ, the makers of Eclair wallet. Eclair offers more advanced/technical users a deeper look behind the hood of the inner workings with channel management being a manual operation.
With Phoenix, ACINQ has taken this away, with the aim of it being a more user friendly wallet for the end user - A more Mom and Pop style wallet.
When Stephanie, a new user of Phoenix wants to be paid by Andreas, she will create an invoice on her phone, just like any other wallet. Andreas will then scan that QR code, send the payment, and it will look just like any other Lightning transaction to Andreas.
If Stephanie currently has channels open with enough inbound capacity - Then it will complete successfully. But what happens when there is not enough inbound capacity, or no channels at all?
This is where Phoenix differs. Phoenix wallet offers no channel management to the end user, it is all done under the hood. The wallet ONLY connects to the ACINQ node, initially through a ‘fake channel’ and when an incoming payment is detected by ACINQ, the ‘routing hint’ that was contained in the QR code points to Stephanie’s wallet through this fake channel.
[Andreas → Node X → Node Y → ACINQ Node -*-*-> Stephanie]
Stephanie will then get notified that she has an incoming payment and be asked if she would like ACINQ to open a channel with her and push her the balance due (Turbo Channel). This comes at a cost though, 0.5% of the amount received. [Phoenix state that this is to cover the cost of opening the channel and allocating additional liquidity on their side]
A Final Discussion
Update 6/19/2022
SOB #502 When the Referees Play Favorites (Part 1)
SOB #501 When More Is Less
SOB #500 Three Rules to Remember After Mailchimp Breach
SOB #503 The Check Engine Light and the Space Shuttle
SOB #499 New Lessons From the Island of Stone Bitcoins
SOB #498 Rights Versus Privileges in a Global Financial System
Quick SOB Update (More frequent episodes coming... now)
SOB #496 The Ups and Downs of Crypto Loans
SOB #497 A Brief Look at Bitcoin Maximalism
SOB # 495 First Practices Aren’t Best Practices
SOB #494 Bitcoin Security and a Rogue Power Plant
SOB #493 The Endowment Effect, HODLing and the Impossible Self-Appraisal
SOB #492 Can Stablecoins Survive?
SOB #491 The Jokes Wear Thin as Inflation Becomes Normal
SOB #490 Checking in on Bitcoin’s Lightning Network
SOB #489 Big Gaming Signals NFTS Are Closer to Mainstream
SOB #488 How Far We've Come (And How Much Stayed the Same)
SOB #487 If Facebook Can't Run A Global Currency, Who Could?
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
A Prairie Home Companion: News from Lake Wobegon