Oof... I get the delemna. I agree, there's some work to do. Lots to unpack there. First, I will say, that strike is a great option. They do a great job of abstracting most of the Bitcoin confusion away from the user and just let them use the payment rails seamlessly. It's beautiful. It's the app that I use to onboard people to Bitcoin.
But, the ethos of Bitcoin is self-custody and strike is custodial. You can't get into self-custody until you take the time to understand how Bitcoin works. Many of the apps that are built can't abstract that piece because users need the ability to connect to their set-ups (nodes).
As far as L1/ L2... "Lightning" is basically a smart contract between two parties. It creates a relationship on L1 for a fixed amount. This is why with most wallets, you first fund the wallet, then you open a channel. Once the channel is opened, you'll have outbound liquidity. It's like opening a tab at the bar. You can make payments to the bar, but you can't really receive payments that way.
You don't really "fund L2" as much as you are opening a payment channel using L1. I guess people say "funded" because the funds are now locked into a payment channel. That network of payment channels is the lightning network.
There's no getting around the fact that once you get into self-custody, the waters get very deep, very fast. Personally, I do believe that custodial services will be a must in this space as much as it pains me. The average user is just not going to go through all of this.
GrumpyG / GrumpyGardener
npub159w…csm3
2024-05-30 11:41:07
in reply to nevent1q…2z4f
Author Public Key
npub159wczz79n0x95p4vq5rggdkhz36u3852n8xfwv3u4ehdylrnr97qnpcsm3Published at
2024-05-30 11:41:07Event JSON
{
"id": "25d47272c2fdfd69ed4bb48da0978049b64bf560cb300eb3b52dca3187ab66ac",
"pubkey": "a15d810bc59bcc5a06ac05068436d71475c89e8a99cc97323cae6ed27c73197c",
"created_at": 1717062067,
"kind": 1,
"tags": [
[
"e",
"f3d808641f77b97d2725f1e9afbc33e8cd0f4c7a7734076ae0b0a16d97a8a9df",
"",
"root"
],
[
"e",
"129ed2fbae1320eefd558f9b7301c6269e68b9aee6b8303306e8424ab404fdbc"
],
[
"e",
"04dc5f5970b5f1cc057a45a7e88da0c3f8c81d9ce685514ce98e391acd1c56db",
"",
"reply"
],
[
"p",
"ba40a9197ddc4cf2e900beb4ec625093033d78a5d8b40f9e4d0756f4d1ca8326"
],
[
"p",
"1d23da07a20f1df185a9a7b5c150e201c07a4ae42620631767771ef4b3291d97"
]
],
"content": "Oof... I get the delemna. I agree, there's some work to do. Lots to unpack there. First, I will say, that strike is a great option. They do a great job of abstracting most of the Bitcoin confusion away from the user and just let them use the payment rails seamlessly. It's beautiful. It's the app that I use to onboard people to Bitcoin. \n\nBut, the ethos of Bitcoin is self-custody and strike is custodial. You can't get into self-custody until you take the time to understand how Bitcoin works. Many of the apps that are built can't abstract that piece because users need the ability to connect to their set-ups (nodes). \n\nAs far as L1/ L2... \"Lightning\" is basically a smart contract between two parties. It creates a relationship on L1 for a fixed amount. This is why with most wallets, you first fund the wallet, then you open a channel. Once the channel is opened, you'll have outbound liquidity. It's like opening a tab at the bar. You can make payments to the bar, but you can't really receive payments that way.\n\nYou don't really \"fund L2\" as much as you are opening a payment channel using L1. I guess people say \"funded\" because the funds are now locked into a payment channel. That network of payment channels is the lightning network. \n\nThere's no getting around the fact that once you get into self-custody, the waters get very deep, very fast. Personally, I do believe that custodial services will be a must in this space as much as it pains me. The average user is just not going to go through all of this. ",
"sig": "83b891e6426ed5644478f86e06214a84867600074d76e10c543d8661cb3e95b049744de8d7bc05184c702f8841e243bc7ec8c65586a0e93d3018010338348781"
}