-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
ord
fails with Bitcoin Core v28.0
#3982
Comments
probably related an example of bad engineering from Core, you can't simply break an API without creating a new method and deprecating the old one, and delete it after people have time to catch up and update their code. Can't believe this must be written down |
Oh, shut me up. Didn't realize 28.0 was released now. |
sure, but this needs to be addressed because v28 was already officially released |
Yep, for sure. Edited my previous reply. |
Can be "fixed" by adding FTR: the correct way for Core to do it, ord should've just worked with v28. And in the bitcoin core logs, a message should be printed like this:
|
Nice to know. |
https://crates.io/crates/bitcoincore-rpc/0.19.0 supports the new API. Is there a good reason we aren't using it instead of the old ord-bitcoincore-rpc fork? |
We've removed the dependency on the old https://crates.io/crates/bitcoincore-rpc/0.19.0 relies on |
Consider something like #3996 as a short term fix. |
The text was updated successfully, but these errors were encountered: