pull down to refresh
Pineapple is fantastic. It contains great electrolytes that will keep your cum hydrated, tasting great and ready to go!
I will be back with more in the coming days.
focus on bitcoin could imply a slightly self-serving motive in disrupting traditional financial systems
A bit of ai passive aggressiveness - nice
17 sats \ 0 replies \ @Fiatrevelation OP 14 Mar \ parent \ on: Question of trust regarding LSPs lightning
trust smuggling
great terminology!
For example, inviting friends or family to your node is just sending them a link with your nodes nprofile encoded, or use a lightning address for debits not just payments.
Sounds exciting. Haven't tried it out yet, but I'll experiment sometime soon.
10 sats \ 3 replies \ @Fiatrevelation OP 14 Mar \ parent \ on: Question of trust regarding LSPs lightning
So they are broadcast, as a channel-open usually is, but you don't have to wait for the 3 block confirmation before using them. I'm guessing the wrapped invoice includes the channel open fee, paid for by the sender?
you can always just fund an outbound channel to another node directly if you know what you're doing and are inclined to do it.
The preferred way, but can this sustain all users .... #912374 👀
On another note, it would seem that BTCPay and and LNBits both do something similar to Lightning.pub, in terms of 'node sharig.' I'm not as familiar with LNBits, but using BTCPay, I know I can add users who can accept lightning payments into their 'account' using my node. When they want to withdraw, they can make a pull-payment request and then I forward the payment to their external wallet using a private, funded channel.
Do you care to differentiate lightning.pub from this style of 'node sharing?'
17 sats \ 4 replies \ @Fiatrevelation OP 14 Mar \ parent \ on: Question of trust regarding LSPs lightning
I really appreciate that your high level of cynacism is backed up by an extraordinary amount of pow in building lightning.pub.
no different than using a custodial wallet to save and buy a channel when ready,
It's this line of thinking that led me to ask these questions. Unfortunately it feels like lightning relies overwhelmingly on such 'custodians'.
transaction fees before reality set in.
As in routing tx fees?
This is why mobile nodes are a dead-end, they're too costly to maintain for the low volume and online-ness of a mobile device.
Too costly for the users or the service providers? I would guess that LSP market is mainly comprised of people who put a high value on the convenience of not having to self-host. It is a good price for a noob to start learning and is not as steep a learning curve as a self-hosted set-up.
The LSP detects the payment and opens up a 0-conf, just in time, channel to the receiver
Yea, this part is confusing for me. JiT channels allow a receiver to borrow liquidity from an LSP in using a wrapped invoice. At what point does this confirm on-chain?
If its not confirming on-chain at the time the channel is being opened, this sounds trusted. If its not confirming on-chain, then what enforces the LSP to be responsible and not double spend?