pull down to refresh
30 sats \ 0 replies \ @TonyGiorgio 26 Mar 2023
Most of the terms, concepts, and pictures originated from here in case anyone wants to know more. I'm one of the authors if anyone has any questions.
https://lightningprivacy.com/en/channel-coinjoins
reply
25 sats \ 2 replies \ @runningbitcoin 26 Mar 2023
https://nitter.net/LN_Capital/status/1640008225159274497#m
reply
0 sats \ 1 reply \ @ama 26 Mar 2023
Thank you for the sane link.
reply
0 sats \ 0 replies \ @runningbitcoin 26 Mar 2023
🤙
reply
0 sats \ 0 replies \ @nym 18 Apr
That's cool. I think they are moving to fedimint solutions now.
reply
0 sats \ 0 replies \ @bitgould 27 Mar 2023
so cool
reply
0 sats \ 0 replies \ @BitByBit21 27 Mar 2023
Any wallet already implementing this?
reply
0 sats \ 0 replies \ @nicosey 26 Mar 2023
You also have CoinSwap coming with lightning. Another string to the bow.
reply
0 sats \ 0 replies \ @TheBTCManual 26 Mar 2023
I never considered using splicing like this, but it sure could provide additional privacy and cost benefits as your payment searches both on-chain and LN channels for the best path to settle a payment
reply
0 sats \ 0 replies \ @02ad8239c2 26 Mar 2023
slightly confused by the term balance here - to me, the size of a channel is it's capacity, and it's balance is how much is on either side -
eg - if a channel is 50/50, or 80/20 on either side, that is the balance
the capacity in both cases would be 100
the explanation seems to be(?) using balance to describe both balance AND capacity, arbitrarily - but i could just be misunderstanding...
reply
0 sats \ 0 replies \ @davidw 26 Mar 2023
Great thread / write-up. Hadn’t considered that use case from splicing.
reply