Files
lightning/openingd
niftynei c3a387a6d8 dual-fund: use correct 'last_tx'
We were incorrectly saving the *remote's* commitment transaction as the
'last_tx' for a peer, not our own local one.

When we applied the 'remote_commit_sig' to it, it would fail since the
remote's signature doesn't validate for their commitment transaction.
2021-01-10 13:44:04 +01:00
..
2021-01-10 13:44:04 +01:00
2020-12-09 16:40:13 +10:30
2020-12-09 16:40:13 +10:30