core-lightning/gossipd
Christian Decker 0e0ad1aa4d gossip: Check that we have a node before applying changes
This was a tricky one to find, it turns out that some nodes are sending
node_announcements even if they don't have a channel announced yet. If they are
a peer and the channel is currently verifying then we'll have a local channel in
the network view, hence accept the node_announcement, but when replaying, the
node_announcement will be replayed and we won't have a channel yet. This just
skips node_announcements, which is always safe.

Reported-by: @laszlohanyecz
Signed-off-by: Christian Decker <decker.christian@gmail.com>
2018-03-29 23:15:33 +02:00
..
test gossip: Wrap node_announcements in gossip_store messages 2018-03-25 23:56:59 +00:00
broadcast.c gossipd: make struct queued_message private. 2018-03-14 02:19:37 +00:00
broadcast.h Use expected LIGHTNING_DIR_FILE_H define 2018-03-25 23:54:21 +00:00
gossip_store.c gossip: Make gossip_store_append private 2018-03-25 23:56:59 +00:00
gossip_store.h gossipd/gossip_store.h: fix check-source for new source file header guards 2018-03-26 00:20:01 +00:00
gossip_wire.csv gossip: Add message types to store gossip msgs and associate data 2018-03-25 23:56:59 +00:00
gossip.c gossip: Replay the entire store on init instead of when idle 2018-03-25 23:56:59 +00:00
handshake.c status: remove trc context now we have tmpctx. 2018-03-16 00:16:10 +00:00
handshake.h Use expected LIGHTNING_DIR_FILE_H define 2018-03-25 23:54:21 +00:00
Makefile gossip: Added gossip store primitives 2018-03-25 23:56:59 +00:00
routing.c gossip: Check that we have a node before applying changes 2018-03-29 23:15:33 +02:00
routing.h gossip: Check that we have a node before applying changes 2018-03-29 23:15:33 +02:00