lightning

History

Christian Decker 72f1c78a1e jsonrpc: Arm the minconf=1 parameter and deal with the fallout We want to disallow using unconfirmed outputs by default, so making the default 1 confirmation seems a good idea. This also matches `bitcoind`s minimum confirmation requirement. Arming however breaks some of our tests, so I used `minconf=0` for the breaking tests and added a new test specifically for the `minconf` parameter for `fundchannel`. Signed-off-by: Christian Decker <decker.christian@gmail.com>		6 years ago
..
data	pytest: test starting with db corrupted by dangling peer.	6 years ago
plugins	pylightning: Split @method and @async_method decorators	6 years ago
benchmark.py	py-tests: rename 'announce' to 'wait_for_announce'	6 years ago
btcproxy.py	pytest: create proper mock failures.	6 years ago
conftest.py	pytest: Pass result to fixtures and keep directories of failed tests	6 years ago
fixtures.py	pytest: Have bitcoind own its proxies	6 years ago
requirements.txt	pytest: Update test dependencies to latest version	6 years ago
test_closing.py	jsonrpc: Arm the minconf=1 parameter and deal with the fallout	6 years ago
test_connection.py	jsonrpc: Arm the minconf=1 parameter and deal with the fallout	6 years ago
test_db.py	db: fix dangling peers on db upgrade.	6 years ago
test_gossip.py	pytest: Mark the worst gossip offenders as developer-only tests	6 years ago
test_invoices.py	bitcoin/chainparams: use amount_sat / amount_msat	6 years ago
test_misc.py	jsonrpc: Arm the minconf=1 parameter and deal with the fallout	6 years ago
test_pay.py	channeld: use amount_msat for struct htlc amount.	6 years ago
test_plugin.py	pylightning: Add a small test for async rpcmethods	6 years ago
utils.py	pytest: add support for starting nodes with a pre-canned db.	6 years ago