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

Author	SHA1	Message	Date
Rusty Russell	e46ce0fc84	jsonrpc: declare up front whether a response is success or fail. Such an API is required for when we stream it directly. Almost all our handlers fit this pattern already, or nearly do. We remove new_json_result() in favor of explicit json_stream_success() and json_stream_fail(), but still allowing command_fail() if you just want a simple all-in-one fail wrapper. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	6 years ago
Rusty Russell	305795b01e	common/json: move JSON creation routines into lightningd/ It's the only user of them, and it's going to get optimized. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> gossip.pydiff --git a/common/test/run-json.c b/common/test/run-json.c index 956fdda35..db52d6b01 100644	6 years ago
lisa neigut	b9331e5ac8	gossipd: parse and respect optional `htlc_maximum_msat` If another channel has set the optional `htlc_maximum_msat` field, we should correctly parse that field and respect it when drawing up routes for payments.	6 years ago
Rusty Russell	c8c3294a23	json-invoice: add routeboost, warnings. We split json_invoice(), as it now needs to round-trip to the gossipd, and uniqueness checks need to happen after gossipd replies to avoid a race. For every candidate channel gossipd gives us, we check that it's in state NORMAL (not shutting down, not still waiting for lockin), that it's connected, and that it has capacity. We then choose one with probability weighted by excess capacity, so larger channels are more likely. As a side effect of this, we can tell if an invoice is unpayble (no channels have sufficient incoming capacity) or difficuly (no online channels have sufficient capacity), so we add those warnings. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	6 years ago

1 2 3