core-lightning/contrib/pyln-testing/pyln/testing
darosior dce2e87928 chaintopology: better feerate targets differentiation
We kept track of an URGENT, a NORMAL, and a SLOW feerate. They were used
for opening (NORMAL), mutual (NORMAL), UNILATERAL (URGENT) transactions
as well as minimum and maximum estimations, and onchain resolution.

We now keep track of more fine-grained feerates:
- `opening` used for funding and also misc transactions
- `mutual_close` used for the mutual close transaction
- `unilateral_close` used for unilateral close (commitment transactions)
- `delayed_to_us` used for resolving our output from our unilateral close
- `htlc_resolution` used for resolving onchain HTLCs
- `penalty` used for resolving revoked transactions

We don't modify our requests to our Bitcoin backend, as the next commit
will batch them !

Changelog-deprecated: The "urgent", "slow", and "normal" field of the `feerates` command are now deprecated.
Changelog-added: The fields "opening", "mutual_close", "unilateral_close", "delayed_to_us", "htlc_resolution" and "penalty" have been added to the `feerates` command.
2020-03-30 20:17:18 +10:30
..
__init__.py pyln: Bump versions of pyln-client and pyln-testing 2019-12-31 16:43:04 +01:00
btcproxy.py pyln-testing: Copy basic support infrastructure into pyln.testing 2019-11-12 21:23:55 +01:00
db.py pyln-testing: Copy basic support infrastructure into pyln.testing 2019-11-12 21:23:55 +01:00
fixtures.py pytest: Configure logging in a fixture to match stdout capturing 2020-03-24 09:52:33 +10:30
utils.py chaintopology: better feerate targets differentiation 2020-03-30 20:17:18 +10:30