yyforyongyu 186569c610 contractcourt: skip checkpoint timeout resolver upon mempool spend ...

Previously when a block spend is found for the outpoint, our htlc
timeout resolver will do a checkpoint, which implicitly creates a db
record if there isn't one. Now, if the spend is found in mempool,
the resolver will be deleted once the contract is resolved. Later on
when the spend is found in the block again, the resolver will be created
again, but never gets resolved this time.

2023-04-28 20:38:01 +08:00

..

anchor_resolver.go

…

breach_resolver.go

…

breacharbiter_test.go

…

breacharbiter.go

…

briefcase_test.go

…

briefcase.go

…

chain_arbitrator_test.go

…

chain_arbitrator.go

…

chain_watcher_test.go

…

chain_watcher.go

…

channel_arbitrator_test.go

…

channel_arbitrator.go

…

commit_sweep_resolver_test.go

…

commit_sweep_resolver.go

…

contract_resolvers.go

…

htlc_incoming_contest_resolver.go

…

htlc_incoming_resolver_test.go

…

htlc_lease_resolver.go

…

htlc_outgoing_contest_resolver_test.go

…

htlc_outgoing_contest_resolver.go

…

htlc_success_resolver_test.go

…

htlc_success_resolver.go

…

htlc_timeout_resolver_test.go

…

htlc_timeout_resolver.go

…

interfaces.go

…

log.go

…

mock_htlcnotifier_test.go

…

mock_registry_test.go

…

nursery_store_test.go

…

nursery_store.go

…

setup_test.go

…

utils_test.go

…

utxonursery_test.go

…

utxonursery.go

…