0617690981
If we expect further events for an onchain output (because we can steal it away from the 'external'/rightful owner), we mark them. This prevents us from marking a channel as 'onchain-resolved' before all events that we're interested in have actually hit the chain. Case that this matters: Peer publishes a (cheating) unilateral close and a timeout htlc (which we can steal). We then steal the timeout htlc. W/o the stealable flag, we'd have marked the channel as resolved when the peer published the timeout htlc, which is incorrect as we're still waiting for the resolution of that timeout htlc (b/c we *can* steal it). |
||
|---|---|---|
| .. | ||
| test | ||
| Makefile | ||
| onchain_types.h | ||
| onchaind.c | ||
| onchaind_wire.c | ||
| onchaind_wire.csv | ||
| onchaind_wire.h | ||