lukechilds/lightning - lightning - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Christian Decker	c17848a3f3	gossip: Disable local channels after loading the gossip_store We don't have any connection yet, so how could they be active? Disable both sides to avoid trying to route through them or telling others to use them as `contact_points` in invoices. Signed-off-by: Christian Decker <decker.christian@gmail.com>	7 years ago
Rusty Russell	edf1b3cec9	More option cleanups. Because we have too many which are never used and I don't want to document them. 1. Remove unused anchor_onchain_wait. When implemented, it should be hardcoded to 100 or more. 2. Remove anchor_confirms_max. 10 always reasonable, and we can readd an override option should someone need it. 3. max_htlc_expiry should be the same as locktime_max (which increases from 3 to 5 days by default): they're both a limit on how long funds can be locked up. 4. channel_update_interval should always be a dev option. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	7 years ago
Rusty Russell	fe96fe10c7	Clean up network options. It's become clear that our network options are insufficient, with the coming addition of Tor and unix domain support. Currently: 1. We always bind to local IPv4 and IPv6 sockets, unless --port=0, --offline, or any address is specified explicitly. If they're routable, we announce. 2. --addr is used to announce, but not to control binding. After this change: 1. --port is deprecated. 2. --addr controls what we bind to and announce. 3. --bind-addr/--announce-addr can be used to control one and not the other. 4. Unless --autolisten=0, we add local IPv4 & IPv6 port 9735 (and announce if they are routable). 5. --offline still overrides listening (though announcing is still the same). This means we can bind to as many ports/interfaces as we want, and for special effects we can announce different things (eg. we're sitting behind a port forward or a proxy). What remains to implement is semi-automatic binding: we should be able to say '--addr=0.0.0.0:9999' and have the address resolve at bind time, or even '--addr=0.0.0.0:0' and have the port autoresolve too (you could determine what it was from 'lightning-cli getinfo'. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	7 years ago
Christian Decker	727d115296	pytest: Add py.test fixtures and migrate first example test This is the first example of the py.test style fixtures which should allow us to write much cleaner and nicer tests. Signed-off-by: Christian Decker <decker.christian@gmail.com>	7 years ago