Rusty Russell 175db926c2 chaintopology: expose when we don't actually know feerate. ... We use feerate in several places, and each one really should react differently when it's not available (such as when bitcoind is still catching up): 1. For general fee-enforcement, we use the broadest possible limits. 2. For closingd, we use it as our opening negotiation point: just use half the last tx feerate. 3. For onchaind, we can use the last tx feerate as a guide for our own txs; it might be too high, but at least we know it was sufficient to be mined. 4. For withdraw and fund_channel, we can simply refuse. Fixes: #1836 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>		2018-08-24 02:17:51 +00:00
..
.gitignore	wallet: move tests into test/ dir like other unit tests.	2017-12-13 22:46:10 +01:00
Makefile	lightningd: keep local_basepoints and local_funding_pubkey.	2018-07-24 00:40:01 +02:00
run-db.c	wallet: put explicit hook in for fatal error testing.	2018-08-10 12:44:28 +02:00
run-wallet.c	chaintopology: expose when we don't actually know feerate.	2018-08-24 02:17:51 +00:00
test_utils.h	Use expected LIGHTNING_DIR_FILE_H define	2018-03-25 23:54:21 +00:00