Sunday, December 22, 2024

Why my lightning node does RBF onchain of a tx that doesn’t exists? (after a pressured shut channel with an expired HTLC)

I’m utilizing lightning core and I had a drive shut channel with an lively HTLC, funds had been despatched from this handle bc1qca5lwlfv8qzkchcfqdryfl89szuk2n0c3x2p7vt4gst04keygkns4x68hh to myself (bc1qf7nh8pwt30nxueqekrhapa3wyz98zxu58rfl8l and have been spent) and after the expired HTLC (3 days later) funds had been despatched to the identical handle of drive shut (bc1qca5lwlfv8qzkchcfqdryfl89szuk2n0c3x2p7vt4gst04keygkns4x68hh).

Since then funds are caught and I see in logs that’s doing a RBF onchain of txid that I cannot discover and retains rising the payment (simply displaying two examples on logs charges going from 2728 to 14841):

Apr 10 15:59:39 nixos lightningd[1311]: INFO 021cb32426ed1a6be9533801e7c56a70ffc1c360a3a31819c3ae0a72e141d78000-chan#6: RBF onchain txid 7114510a6756715ddbed679f3c3f5787033780a800a3ef402033ee09d82630e0 (payment 2707sat) with txid ea512e00228263f53ae143416324a04b28e9381217400191ea7a031e343441c0 (payment 2728sat)

Apr 10 18:35:54 nixos lightningd[1311]: INFO 021cb32426ed1a6be9533801e7c56a70ffc1c360a3a31819c3ae0a72e141d78000-chan#6: RBF onchain txid 8d83a77b59a36f893d693e467f6e64434bf205337176113a9b569c27c0f12c78 (payment 14840sat) with txid 51eb15bc8541358912d23493b16ad9d38cac48f9a41f72ba2c05c83d6da29152 (payment 14841sat)

I might recognize if somebody can clarify me why my node is doing this.

Thanks

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles