pull down to refresh
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
https://nitter.net/LN_Capital/status/1640008225159274497#m
Thank you for the sane link.
🤙
That's cool. I think they are moving to fedimint solutions now.
so cool
Any wallet already implementing this?
You also have CoinSwap coming with lightning. Another string to the bow.
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
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...
Great thread / write-up. Hadn’t considered that use case from splicing.
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
https://nitter.net/LN_Capital/status/1640008225159274497#m
Thank you for the sane link.
🤙
That's cool. I think they are moving to fedimint solutions now.
so cool
Any wallet already implementing this?
You also have CoinSwap coming with lightning. Another string to the bow.
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
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...
Great thread / write-up. Hadn’t considered that use case from splicing.