Olaoluwa Osuntokun 5dc0d669a6

contractcourt: watch proper output within htlcOutgoingContestResolver ...

In this commit, we fix an existing bug in the implementation of the
resolution of the htlcOutgoingContestResolver. Before this commit, we
would _always_ watch the claim outpoint. However, if this is on the
remote party’s commitment transaction, then we would end up watching
the wrong output. We’ll now properly detect this by modifying which
output we watch, based on if we have a second level transaction or not.

2018-01-23 14:16:22 -08:00

..

briefcase_test.go

contractcourt: add new briefcase.go file to house persistent arbitrator state

2018-01-22 19:19:35 -08:00

briefcase.go

multi: fix linter warnings

2018-01-22 19:19:56 -08:00

chain_arbitrator_test.go

contractcourt: add new ChainArbitrator struct as central coordinator of package

2018-01-22 19:19:36 -08:00

chain_arbitrator.go

contractcourt: make synchronous chain watcher notifications optional

2018-01-22 19:19:58 -08:00

chain_watcher.go

contractcourt: properly use the broadcast state number during breach remedy

2018-01-22 19:19:58 -08:00

channel_arbitrator_test.go

contractcourt: add new ChannelArbitrator struct

2018-01-22 19:19:34 -08:00

channel_arbitrator.go

contractcourt: make synchronous chain watcher notifications optional

2018-01-22 19:19:58 -08:00

contract_resolvers_test.go

contractcourt: add complete ContractResolver implementations

2018-01-22 19:19:36 -08:00

contract_resolvers.go

contractcourt: watch proper output within htlcOutgoingContestResolver

2018-01-23 14:16:22 -08:00

log.go

contractcourt: create new package, add logger

2018-01-22 19:19:34 -08:00