pull down to refresh

17 sats \ 6 replies \ @k00b OP 10 May freebie \ parent \ on: Atomic Split Lightning Payments, Hold Invoices, and Blinded Paths bitcoin
I'm not making the case for anything succeeding. I'm making a case that I would like for something to work because I like it's properties more than the opposite's. The opposite may work better. I never said the opposite doesn't work, only that it doesn't have the properties that my ideal solution would have.
Thanks so much for the conversation. I really did not appreciate this:
With wrapped invoices, the payer is getting the invoice from the party doing the wrapping. This is a completely trusted step in the process as the wrapper could wrap anything, or nothing.
write
preview
0 sats \ 5 replies \ @justin_shocknet 10 May
My pleasure, happy to have elucidated that.
Just for my edification while I build out our solution, the preferred property referenced is the regulator scammability property?
reply
0 sats \ 4 replies \ @k00b OP 10 May
No. I'm not sure why you think I want to scam anyone, even regulators, or why you would think I'd believe this is a good scam. You could be trying to troll, in which case "ha," or you think I'm dumb, dishonest, or both, in which case you'll probably want to answer your question yourself.
reply
17 sats \ 1 reply \ @ek 10 May
Maybe it's because of my comment
reply
0 sats \ 0 replies \ @justin_shocknet 10 May
Yea, I didn't coin this phrase and don't mean to imply it's nefarious.
reply
0 sats \ 1 reply \ @justin_shocknet 10 May
I'm not using it as a pejorative, cat and mouse with regulators is necessary.
Indulge me as I'm trying to understand what property is being preferred so that I can be sure my solution possess that property.
reply
0 sats \ 0 replies \ @k00b OP 10 May
We've been over every argument I have to make, I think, and by your account I'm wrong (or something like it), so if I'm actually wrong, I reckon there's nothing left for you to understand.
reply