Skip to content

Fix feerate docs #6170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ShahanaFarooqui merged 2 commits into from
Apr 11, 2023
Merged

Fix feerate docs #6170

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
97dfa05
doc: give helpful examples for feerate values.
rustyrussell Apr 11, 2023
ca5976a
doc: document that urgent doesn't use the 2-block estimate, but the 6…
rustyrussell Apr 11, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions doc/lightning-feerates.7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,11 @@ CLN will also smoothen feerate estimations from the backend.

*style* is either of the two strings:

* *perkw* - provide feerate in units of satoshis per 1000 weight.
* *perkb* - provide feerate in units of satoshis per 1000 virtual bytes.
* *perkw* - provide feerate in units of satoshis per 1000 weight (e.g. the minimum fee is usually `253perkw`)
* *perkb* - provide feerate in units of satoshis per 1000 virtual bytes (eg. the minimum fee is usually `1000perkb`)

Explorers often present fees in "sat/vB": 4 sat/vB is `4000perkb` or
`1000perkw`.

Bitcoin transactions have non-witness and witness bytes:

Expand Down Expand Up @@ -101,8 +104,8 @@ NOTES
Many other commands have a *feerate* parameter. This can be:

* One of the strings to use lightningd's internal estimates:
* *urgent* (aim for next block),
* *normal* (next 6 blocks or so)
* *urgent* (next 6 blocks or so)
* *normal* (next 12 blocks or so)
* *slow* (next 100 blocks or so)
* *minimum* for the lowest value bitcoind will currently accept (added in v23.05)

Expand Down