Wilmer Paulino 57b69e3b1a discovery: check ChainHash in QueryChannelRange messages ...

If the provided ChainHash in a QueryChannelRange message does not match
that of our current chain, then we should send a blank response, rather
than reply with channels for the wrong chain.

2020-01-17 11:51:09 -08:00

..

bootstrapper.go

discovery: error string lint fixes

2019-09-25 18:42:38 +00:00

chan_series.go

multi: move Route to sub-pkg routing/route

2019-04-29 14:52:33 +02:00

gossiper_test.go

routing+discovery: extract local channel manager

2019-09-23 13:07:08 +02:00

gossiper.go

multi: remove LocalFeatures and GlobalFeatures

2019-11-08 05:32:00 -08:00

log.go

multi: init subsystem loggers via build pkg

2018-10-05 13:04:45 +09:00

message_store_test.go

discovery/message_store: add gossip message store

2019-02-14 18:29:39 -08:00

message_store.go

discovery/message_store: add gossip message store

2019-02-14 18:29:39 -08:00

mock_test.go

multi: merge local+global features from remote peer

2019-11-08 05:31:47 -08:00

reliable_sender_test.go

multi: move WaitPredicate, WaitNoError, WaitInvariant to lntest/wait

2019-09-19 12:46:29 -07:00

reliable_sender.go

discovery,fundingmanager: avoid serialization in NotifyWhenOnline

2019-06-04 16:36:21 -03:00

sync_manager_test.go

discovery: interpret block range from ReplyChannelRange messages

2020-01-06 14:03:13 -08:00

sync_manager.go

multi: remove dead code

2019-09-10 17:21:59 +02:00

syncer_test.go

discovery: check ChainHash in QueryChannelRange messages

2020-01-17 11:51:09 -08:00

syncer.go

discovery: check ChainHash in QueryChannelRange messages

2020-01-17 11:51:09 -08:00

utils.go

multi: remove dead code

2019-09-10 17:21:59 +02:00