You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
|
#ifndef LIGHTNING_LIGHTNINGD_GOSSIP_CONTROL_H
|
|
|
|
|
#define LIGHTNING_LIGHTNINGD_GOSSIP_CONTROL_H
|
|
|
|
|
#include "config.h"
|
|
|
|
|
#include <bitcoin/short_channel_id.h>
|
gossipd: rewrite to do the handshake internally.
Now the flow is much simpler from a lightningd POV:
1. If we want to connect to a peer, just send gossipd `gossipctl_reach_peer`.
2. Every new peer, gossipd hands up to lightningd, with global/local features
and the peer fd and a gossip fd using `gossip_peer_connected`
3. If lightningd doesn't want it, it just hands the peerfd and global/local
features back to gossipd using `gossipctl_handle_peer`
4. If a peer sends a non-gossip msg (eg `open_channel`) the gossipd sends
it up using `gossip_peer_nongossip`.
5. If lightningd wants to fund a channel, it simply calls `release_channel`.
Notes:
* There's no more "unique_id": we use the peer id.
* For the moment, we don't ask gossipd when we're told to list peers, so
connected peers without a channel don't appear in the JSON getpeers API.
* We add a `gossipctl_peer_addrhint` for the moment, so you can connect to
a specific ip/port, but using other sources is a TODO.
* We now (correctly) only give up on reaching a peer after we exchange init
messages, which changes the test_disconnect case.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
7 years ago
|
|
|
#include <ccan/short_types/short_types.h>
|
|
|
|
|
#include <stdbool.h>
|
|
|
|
|
|
|
|
|
|
struct lightningd;
|
|
|
|
|
|
|
|
|
|
void gossip_init(struct lightningd *ld);
|
|
|
|
|
|
|
|
|
|
void gossipd_notify_spend(struct lightningd *ld,
|
|
|
|
|
const struct short_channel_id *scid);
|
|
|
|
|
|
|
|
|
|
#endif /* LIGHTNING_LIGHTNINGD_GOSSIP_CONTROL_H */
|
