pull down to refresh
100 sats \ 0 replies \ @sime 3 Oct 2023
FYI the taproot channels are only available for private channels (currently).
reply
0 sats \ 0 replies \ @nikotsla 5 Oct 2023
Updated! looking for those memory fixes and the watchtower improvements.
reply
0 sats \ 0 replies \ @joyepzion 4 Oct 2023
An update to work with
reply
0 sats \ 6 replies \ @fred 3 Oct 2023
Taproot is a different protocol to Lightning so how does it tap into it
reply
110 sats \ 5 replies \ @k00b 3 Oct 2023
They are rebuilding their lightning implementation on top of Taproot, ie their onchain transactions optionally make use of Taproot.
reply
0 sats \ 4 replies \ @BlokchainB 3 Oct 2023
Does this mean existing channels need to be closed and opened as taproot channels to reap the benefits?
reply
1000 sats \ 0 replies \ @031ef7d322 4 Oct 2023
Check out Dynamic Commitments
https://github.com/lightningnetwork/lnd/issues/7878
https://github.com/ProofOfKeags/bolts/blob/extension/dynamic-commitments/ext-dynamic-commitments.md
reply
1256 sats \ 0 replies \ @calaniz 3 Oct 2023
I think it’s fine to take advantage of taproot privacy on a go forward basis to avoid the fee impact of closing channels all at once
reply
161 sats \ 0 replies \ @k00b 3 Oct 2023
It means any new channels you create can be these simple taproot channels. It doesn't sound like you can upgrade existing channels.
Although I wonder if somehow you could splice into an upgrade when lnd has splicing (I don't know enough about splicing).
reply
0 sats \ 0 replies \ @WeAreAllSatoshi 3 Oct 2023
That would make sense to me
reply