-
Notifications
You must be signed in to change notification settings - Fork 69
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
Fee Rates #320
Fee Rates #320
Conversation
Hm should the domains to query be loaded from a config rather than having bb and mempool.space hard coded? |
Probably from configs is ideal |
Also the feerate should be added to wasabi spend |
New commit added making the priorities configurable |
Nice PR! Please move In Also, we need to add It would be cool to have a small Last thing is to add the new endpoint to Thanks!! |
Should have covered all this off in the 2 commits above |
Can you make |
Added! |
I rebased on dev |
It first tries to fetch fee rate from bb mempool, then mempool.space and finally if they fail it falls back to using bitcoin core.
I have implemented it to use confTarget rather than priority as the priorities can be inferred from the confTarget value and it allows the functionality to be more backward compatible. E.g. we can easily modify any other method currently using confTarget to use this new approach going forward.
I do have a small modification in
batching.sh
that I haven't committed as I noticed that seems to deal with both fee rate and confTarget already so wasn't sure if the change should be added there.As well as updating the
spend
endpoint I have added in a newgetfeerate
endpoint in case we need to fetch the rates anywhere else.Example:
curl -d '{"confTarget":6}' proxy:8888/getfeerate