Function estimatefees_next

plugins/bcli.c:678–717

};

static struct command_result *estimatefees_next(struct command *cmd,
						struct estimatefees_stash *stash)
{
	struct json_stream *response;

	if (stash->cursor < ARRAY_SIZE(stash->perkb)) {
		start_bitcoin_cli(NULL, cmd, estimatefees_done, true,
				  BITCOIND_LOW_PRIO, stash,
				  "estimatesmartfee",
				  take(tal_fmt(NULL, "%u",
					       estimatefee_params[stash->cursor].blocks)),
				  estimatefee_params[stash->cursor].style,
				  NULL);

		return command_still_pending(cmd);
	}

	response = jsonrpc_stream_success(cmd);
	json_add_u64(response, "opening", stash->perkb[FEERATE_NORMAL]);
	json_add_u64(response, "mutual_close", stash->perkb[FEERATE_SLOW]);
	json_add_u64(response, "unilateral_close",
		     stash->perkb[FEERATE_URGENT] * bitcoind->commit_fee_percent / 100);
	json_add_u64(response, "delayed_to_us", stash->perkb[FEERATE_NORMAL]);
	json_add_u64(response, "htlc_resolution", stash->perkb[FEERATE_URGENT]);
	json_add_u64(response, "penalty", stash->perkb[FEERATE_NORMAL]);
	/* We divide the slow feerate for the minimum acceptable, lightningd
	 * will use floor if it's hit, though. */
	json_add_u64(response, "min_acceptable",
		     stash->perkb[FEERATE_SLOW] / 2);
	/* BOLT #2:
	 *
	 * Given the variance in fees, and the fact that the transaction may be
	 * spent in the future, it's a good idea for the fee payer to keep a good
	 * margin (say 5x the expected fee requirement)
	 */
	json_add_u64(response, "max_acceptable",
		     stash->perkb[FEERATE_HIGHEST]
		     * bitcoind->max_fee_multiplier);
	return command_finished(cmd, response);
}

/* Get the current feerates. We use an urgent feerate for unilateral_close and max,
 * a slightly less urgent feerate for htlc_resolution and penalty transactions,