You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Track HTLC-Success/HTLC-Timeout claims of revoked outputs
When a counterparty broadcasts a revoked commitment transaction,
followed immediately by HTLC-Success/-Timeout spends thereof, we'd
like to have an `onchain_events_awaiting_threshold_conf` entry
for them.
This does so using the `HTLCSpendConfirmation` entry, giving it
(slightly) new meaning. Because all existing uses of
`HTLCSpendConfirmation` already check if the relevant commitment
transaction is revoked first, this should be trivially backwards
compatible.
Because we ultimately figure out if something is being spent via
the `OnchainTxHandler` we could skip this, but it allows us to
use the post-HTLC-transaction value instead of the original HTLC
value for claimable outputs.
if outbound_htlc {"outbound"} else {"inbound"}, log_bytes!($htlc.payment_hash.0),
2950
-
if revocation_sig_claim {"revocation sig"} else {"preimage claim after we'd passed the HTLC resolution back"});
2953
+
if revocation_sig_claim {"revocation sig"} else {"preimage claim after we'd passed the HTLC resolution back. We can likely claim the HTLC output with a revocation claim"});
2951
2954
} else {
2952
2955
log_info!(logger,"Input spending {} ({}:{}) in {} resolves {} HTLC with payment hash {} with {}",
0 commit comments