Skip to content
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

Closed
tonyaldon opened this issue Jun 21, 2023 · 4 comments · Fixed by #28
Closed

estimatefees has changed in CLN version v23.05 #20

tonyaldon opened this issue Jun 21, 2023 · 4 comments · Fixed by #28

Comments

@tonyaldon
Copy link

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 is
empty), and an array of 0 or more feerates. Each element of
feerates is an object with blocks and feerate, in
ascending-blocks order, for example:

{
	"feerate_floor": <sat per kVB>,
	"feerates": {
		{ "blocks": 2, "feerate": <sat per kVB> },
		{ "blocks": 6, "feerate": <sat per kVB> },
		{ "blocks": 12, "feerate": <sat per kVB> }
		{ "blocks": 100, "feerate": <sat per kVB> }
	}
}

lightningd will currently linearly interpolate to estimate between given blocks (it will not extrapolate, but use the min/max blocks values).

@fiatjaf
Copy link
Collaborator

fiatjaf commented Jun 21, 2023

If anyone wants to send a pull request, that will be great.

@cryptoteun
Copy link

Anybody who already take a look ont his one? It appears to be broken in 24.05. I get the following error:
**BROKEN** lightningd: DEPRECATED API USED estimatefeesv1

Or do I jump to the wrong conclusion?

@fiatjaf
Copy link
Collaborator

fiatjaf commented Jun 17, 2024

It's definitely broken and waiting for your pull request that fixes it!

@1ma 1ma mentioned this issue Jul 11, 2024
@1ma
Copy link
Contributor

1ma commented Jul 11, 2024

Alright, let's do this. #28

How hard can it be.

rabbit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants