-
Notifications
You must be signed in to change notification settings - Fork 65
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
RPC backend implementation #36
RPC backend implementation #36
Conversation
41171ae
to
b2c48fc
Compare
a504d71
to
f752a1f
Compare
f752a1f
to
fc9e910
Compare
Updated with |
The above error is fixed (along with other updates for BDK v0.10.0) in https://github.com/bitcoindevkit/bdk-cli/pulls Decided to use esplora This should be merged after the version update PR. |
1931e97
to
e0ec29e
Compare
Rebased on esplora fix at #41 .. This should be merged after that PR. |
e0ec29e
to
50139de
Compare
c044230
to
dc33fc2
Compare
Rebased on master. |
There needs to be readme update after this. But doing it in this PR might cause conflicts with #44. So putting that for a separate PR. |
Please add |
Need to add |
Expose the RPC backend feature via cli arg options. RPC backend can be connected via all default parameters without specifying any arg options.
dc33fc2
to
32a3a55
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 32a3a55
Looks good, thanks for the update. I'll give anyone else interested a chance to review and if no objections merge tomorrow.
Description
This opens the RPC backend recently added in BDK bitcoindevkit/bdk#407.
This builds on top of BDK master, because RPC back end isn't released yet.
I committed the
Cargo.lock
file too understanding that we are suppose to commit this file also as per #27 (comment). Let me know if that's not appropriate.This is now ready for review.
Notes to the reviewers
It seems there is some failure with
esplora
backend, probably something related to recent restructuring ofesplora
module inbdk. Now that there are two different esplora configuration in BDK, we need to either chose one for bdk-cli, or have both options
as feature flag. I decided to go for
use-explora-reqwest
for now.But in any case this error should not be there, as I can see bdk compiles with
maybe-await!()
macro in master just fine, with the reqwest esplora feature. Not sure what is the issue here. Any suggestion would be helpful.This is causing the test failures.
Checklists
All Submissions:
cargo fmt
andcargo clippy
before committingNew Features:
CHANGELOG.md