-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
estimatefees
has changed in CLN version v23.05
#20
Comments
If anyone wants to send a pull request, that will be great. |
Anybody who already take a look ont his one? It appears to be broken in 24.05. I get the following error: Or do I jump to the wrong conclusion? |
It's definitely broken and waiting for your pull request that fixes it! |
Merged
Alright, let's do this. #28 How hard can it be. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
estimatefees
has changed in CLN version v23.05.See deprecated section in https://github.com/ElementsProject/lightning/blob/master/CHANGELOG.md#23051---2023-06-05-austin-texas-agreementatxa-ii.
The new spec is (https://github.com/ElementsProject/lightning/blob/master/doc/PLUGINS.md#estimatefees):
estimatefees
Polled by
lightningd
to get the current feerate, all values must be passed in sat/kVB.The plugin must return
feerate_floor
(e.g. 1000 if mempool isempty), and an array of 0 or more
feerates
. Each element offeerates
is an object withblocks
andfeerate
, inascending-blocks order, for example:
lightningd will currently linearly interpolate to estimate between given blocks (it will not extrapolate, but use the min/max blocks values).
The text was updated successfully, but these errors were encountered: