lnd.xprv/lntest
Calvin Zachman f5fb64e552 add new max channel size config option
- let users specify their MAXIMUM WUMBO with new config option which sets the maximum channel size lnd will accept
- current implementation is a simple check by the fundingManager rather than anything to do with the ChannelAcceptor
- Add test cases which verify that maximum channel limit is respected for wumbo/non-wumbo channels
- use --maxchansize 0 value to distinguish set/unset config. If user sets max value to 0 it will not do anything as 0 is currently used to indicate to the funding manager that the limit should not be enforced. This seems justifiable since --maxchansize=0 doesn't seem to make sense at first glance.
- add integration test case to ensure that config parsing and valiation is proper. I simplified the funding managers check electing to rely on config.go to correctly parse and set up either i) non wumbo default limit of 0.16 BTC OR ii) wumbo default soft limit of 10 BTC

Addresses: https://github.com/lightningnetwork/lnd/issues/4557
2020-09-14 21:16:32 -05:00
..
itest add new max channel size config option 2020-09-14 21:16:32 -05:00
mock lnd: delete mock.go, move mockSpendNotifier to lntest/mock 2020-08-31 20:06:11 -04:00
wait lntest+wait: replace sleeps in assertAmountSent 2019-12-18 23:57:12 -08:00
bitcoind.go lntest/bitcoind: set debug loglevel 2019-09-02 09:37:41 +02:00
btcd.go make+itest: make itest Windows compatible 2020-08-05 08:53:04 +02:00
doc.go lntest: Add doc.go with package documentation. 2017-12-14 20:06:23 -08:00
harness.go rpcserver+fundingmanager: thread remote_max_htlcs to channel opening 2020-08-24 20:11:33 -07:00
neutrino.go lntest: compile time check btcd and neutrino BackendCfg interface 2019-09-02 09:37:37 +02:00
node.go lntest: wait for valid tls cert and macaroon files 2020-07-13 13:24:22 -03:00
timeouts_darwin.go itest: increase mempool timeout 2020-05-26 19:49:42 -07:00
timeouts.go itest: increase mempool timeout 2020-05-26 19:49:42 -07:00