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
..
benchmark.py	pytest: Remove test_lightningd and all the legacy testing framework	2018-08-07 00:54:19 +00:00
conftest.py	pytest: Pass result to fixtures and keep directories of failed tests	2018-08-07 00:54:19 +00:00
fixtures.py	pytest: fail if we see 'bad reestablish' in the logs.	2018-08-23 14:46:22 +02:00
requirements.txt	test: add pytest-xdist to the python test requirements	2018-07-26 23:18:37 +02:00
test_closing.py	pytest: remove use dev-override-feerates.	2018-08-24 02:17:51 +00:00
test_connection.py	chaintopology: expose when we don't actually know feerate.	2018-08-24 02:17:51 +00:00
test_gossip.py	connectd: iterate through all known addresses for a peer, not just one.	2018-08-10 12:46:45 +02:00
test_invoices.py	pytest: Move invoice-related tests into their own file	2018-08-07 00:54:19 +00:00
test_misc.py	channel: update fees after lockin.	2018-08-24 02:17:51 +00:00
test_pay.py	pytest: remove use dev-override-feerates.	2018-08-24 02:17:51 +00:00
utils.py	common: log when we toggle IO logging, don't edit env in tests!	2018-08-23 14:46:22 +02:00