Hampus's avatar
Hampus
hampus@nostrplebs.com
npub1v4v5...xwu8
Maker of Blixt Wallet, a non-custodial Lightning Wallet https://blixtwallet.github.io Funded by HRF and OpenSats. ⚡️ hampus@blixtwallet.com
Hampus's avatar
hampus 2 years ago
Is it Lightning's time to shine now when the onchain transaction fee is so high? Well yes, partly. But please understand that Lightning ceases to work if the fees are too high! To understand why, let’s go back to the saying that “Lightning is just Bitcoin transactions”. Yes, this is true. Lightning in the end relies on normal Bitcoin transactions. So by knowing this, you should have already realized why Lightning under a high onchain fee market is fragile, but let me explain: The primary problem I’m referring to is the economical viability to sweep HTLCs. An HTLC is the thing that gets added as an output to your lightning commitment transaction when you are doing Lightning payment. It gets cleared out by making a new commitment transaction once the payment has goes through. But the problem here is that if the onchain transaction fee is $100 and the cost of the sweeping an HTLC output is $100, then that means it’s not actually economically possible to redeem these funds. Under normal circumstances you would never have to force-close and redeem this onchain, but it _can_ happen. How LN circumvents this problem is by giving the payment amount to miners instead as a substitute for a real HTLC output. Giving the sats to miners means no more bytes are added to the commitment transaction, but it also means that if a force-close happens, these sats will just be given to miners instead. This was already the case for all smaller payments (21 sats and so on) including virtually _all_ zaps here on nostr. But for smaller micro-transactions it’s not a big deal if a payments gets lost, because no one would cry over 21 sats. But if it’s about 210 000 sats, then we’re in a BIG problem if this isn’t secure and trustless. We need to find a sweet spot for onchain transaction fees and we need more scaling solutions that work together with LN in order to fix this. My favorite solution is a Lightning Network deployed over multiple Drivechains, fully interoperable, but I’m open for more suggestions. What do you think?
Hampus's avatar
hampus 2 years ago
Blixt Wallet is the tinkerer's wallet. Check out how many things you can do in the settings.
Hampus's avatar
hampus 2 years ago
Gonna watch the Super Mario movie now LFG. ✌️ image
Hampus's avatar
hampus 2 years ago
Epic! Blixt Wallet 0.6.6 has been released, and it's better than ever before. It includes lnd 0.16 with support for bimodal pathfinding (based on Pickhardt Payments). Enjoy potentially speedier payment by enabling it in settings. Happy Blixting! 🟡 ``` ## Common * Updated lnd to v0.16 * Added support for bimodal pathfinding (based on Pickhardt payments). Enable it in Settings! * Added the ability to set a label for a contact in the contact list * Sats amount on Overview screen is now grouped ## Android * Lowered the scheduled sync job interval from 4h to 2h ## macOS * Fixed restoring not working properly ``` image
Hampus's avatar
hampus 2 years ago
Bitcoiners who don't like ordinals & wizards need to understand that the original true meaning of Bitcoin Maximalism is that Bitcoin will cover all use-cases. It's a good thing that we now see higher miner fees, leading to a more healthy and robust network.
Hampus's avatar
hampus 2 years ago
A good rule of thumb is DON’T BREAK USER SPACE. This is something Linus Torvalds constantly repeats regarding the Linux kernel development.
Hampus's avatar
hampus 2 years ago
⚡️ hampus@blixtwallet.com This Lightning Address is special. When you pay to it, my Lightning Box solution will forward the request to the phone, where Blixt Wallet respond with an invoice. This is the first time a self-custodial LN wallet supports Lightning Address. This is part of my on-going work to support receiving via Lightning Address for mobile self-custodial wallets. Android supports foreground services, meaning that Blixt Wallet can stay online all the time to answer incoming requests (no effect on battery). Though the normal mode of operation for Lightning Box is that it'll take the payment on behalf of the user and then next time the user opens wallet, it will auto-withdraw from the Box, thanks to LNURL-withdraw. But if the wallet is online already, it can just forward the request.
Hampus's avatar
hampus 2 years ago
When Satoshi first released Bitcoin, he was out to fix the Byzantime Generals Problem and he did that by PoW and a public ledger (the blockchain). But he put out an imperfect protocol. It's not practically possible to fix everything all at once. The first comment about Bitcoin by another person was about its problematic relationship with scaling. Therefore the idea that Bitcoin is perfect “just the way it is” is a flawed concept. We should strive to improve bitcoin by adding technology that helps for scaling, privacy and other things. Bitcoin is not perfect.
Hampus's avatar
hampus 2 years ago
In the end, all scaling to the Bitcoin mainchain has to come down to "put multiple people on the same UTXO". This is how we achieve mass scaling. My favorite solution for this is Drivechains BIP300/301 + an interoperable Lightning Network. What is your favorite solution?