mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-03-15 11:59:16 +01:00
onchaind: fix resolution detection of complex outputs.
We shouldn't set out->resolved until we've actually resolved it. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
parent
6deed77d88
commit
e746e9c202
1 changed files with 1 additions and 2 deletions
|
@ -612,8 +612,6 @@ static bool resolved_by_proposal(struct tracked_output *out,
|
|||
if (!out->proposal->tx)
|
||||
return false;
|
||||
|
||||
out->resolved = tal(out, struct resolution);
|
||||
|
||||
/* Our proposal can change as feerates change. Input
|
||||
* comparison (ignoring signatures) works pretty well.
|
||||
*
|
||||
|
@ -628,6 +626,7 @@ static bool resolved_by_proposal(struct tracked_output *out,
|
|||
return false;
|
||||
}
|
||||
|
||||
out->resolved = tal(out, struct resolution);
|
||||
bitcoin_txid(tx, &out->resolved->txid);
|
||||
status_trace("Resolved %s/%s by our proposal %s (%s)",
|
||||
tx_type_name(out->tx_type),
|
||||
|
|
Loading…
Add table
Reference in a new issue