Jonathan Underwood [ARCHIVE] on Nostr: 📅 Original date posted:2018-01-13 📝 Original message: Hey everybody. Say that ...
📅 Original date posted:2018-01-13
📝 Original message:
Hey everybody.
Say that the last time we updated channel state, we assumed 40 satoshi/byte
was enough to get confirmed, then I leave the channel for a few weeks, come
back to find my partner fell off the face of the internet.
I perform unilateral close with my output on CSV timelock... but it turns
out there’s 500 MB of txes at around 100 satoshi/byte and lets say my
transaction will never get confirmed at 40 sat/byte.
What course of action can I take?
1. to_local output can't be redeemed until the commitment transaction
(which will "never confirm") is confirmed + the CSV timeout.
2. to_remote output probably won't be redeemed as the other person is
offline.
The only remedy I can think of is hope that the other person comes back
online and CPFPs your to_remote output for you... but at that point it
would be better for them to just amicably close with normal outputs... so
basically your only hope is wait for other person to come online.
Since CSV will cause script verification to fail, a CPFP transaction will
not be propagated.
If we can't CPFP, the CSV timer won't start (it starts once the CSV
containing output is confirmed).
Seems like a problem.
Anyone have any solutions?
Thanks,
Jon
--
-----------------
Jonathan Underwood
ビットバンク社 チーフビットコインオフィサー
-----------------
暗号化したメッセージをお送りの方は下記の公開鍵をご利用下さい。
指紋: 0xCE5EA9476DE7D3E45EBC3FDAD998682F3590FEA3
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180114/0fc7a441/attachment.html>;
📝 Original message:
Hey everybody.
Say that the last time we updated channel state, we assumed 40 satoshi/byte
was enough to get confirmed, then I leave the channel for a few weeks, come
back to find my partner fell off the face of the internet.
I perform unilateral close with my output on CSV timelock... but it turns
out there’s 500 MB of txes at around 100 satoshi/byte and lets say my
transaction will never get confirmed at 40 sat/byte.
What course of action can I take?
1. to_local output can't be redeemed until the commitment transaction
(which will "never confirm") is confirmed + the CSV timeout.
2. to_remote output probably won't be redeemed as the other person is
offline.
The only remedy I can think of is hope that the other person comes back
online and CPFPs your to_remote output for you... but at that point it
would be better for them to just amicably close with normal outputs... so
basically your only hope is wait for other person to come online.
Since CSV will cause script verification to fail, a CPFP transaction will
not be propagated.
If we can't CPFP, the CSV timer won't start (it starts once the CSV
containing output is confirmed).
Seems like a problem.
Anyone have any solutions?
Thanks,
Jon
--
-----------------
Jonathan Underwood
ビットバンク社 チーフビットコインオフィサー
-----------------
暗号化したメッセージをお送りの方は下記の公開鍵をご利用下さい。
指紋: 0xCE5EA9476DE7D3E45EBC3FDAD998682F3590FEA3
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180114/0fc7a441/attachment.html>;