We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Instead of using the conf_target in Bitcoin Core wallet when doing a transaction send, we switch to fee_rate.
We add a parameter to Cyphernode "Spend" which is the Priority
We set priority according to mempool.space format
curl -sSL "https://mempool.space/api/v1/fees/recommended"
`{ fastestFee: 65, halfHourFee: 55, hourFee: 35, economyFee: 25, minimumFee: 12 }
Every spend, we check the feerate from the mempool API according to the priority level and we feed it to the spend request `
The text was updated successfully, but these errors were encountered:
Let Cypnerhonde spend endpoint accept "priority" instead of "conf_target" as a parameter.
Cyphernode will check the mempool fee estimates and Bitcoin core will use the feerate as feerate. Bitcoin Core will never use conf_target anymore.
https://github.com/SatoshiPortal/cyphernode/blob/master/doc/API.v0.md#spend-coins-from-spending-wallet-called-by-your-application
Sorry, something went wrong.
#320
No branches or pull requests
Instead of using the conf_target in Bitcoin Core wallet when doing a transaction send, we switch to fee_rate.
We add a parameter to Cyphernode "Spend" which is the Priority
We set priority according to mempool.space format
curl -sSL "https://mempool.space/api/v1/fees/recommended"
`{
fastestFee: 65,
halfHourFee: 55,
hourFee: 35,
economyFee: 25,
minimumFee: 12
}
Every spend, we check the feerate from the mempool API according to the priority level and we feed it to the spend request
`
The text was updated successfully, but these errors were encountered: