Closed rajarshimaitra closed 2 years ago
Hey @rajarshimaitra concept ACK! but I need to focus on the next bdk release (taproot!) so won't be able to do a through review until that's out.
Ya thanks @notmandatory no issues.. I opened this early for discussion.. This can wait till other major things are done..
bdk v0.19.0
Backend
structBackend
now can be both bitcoind
and electrum
Some minor update in the integration testing..
@notmandatory this PR is now ready for review..
Edit: The tests failure is due to version conflicts in bdk ocuring from bdk-reserves.. Working on a fix for that.. The PR can be code reviewed in the mean time..
Updated the PR doc..
The current test failure at cargo build --features reserves,electrum --locked
fixes with https://github.com/weareseba/bdk-reserves/pull/5
Opened an alternate version of the same PR in #102.
Not closing this one yet, in case we need to revert back to previous crate structure..
Closing this as we are moving ahead with #102
Description
fixes #62 fixes #76
This PR does the following
bdk-cli node <command> [<args>]
. The API of thenode
commands are kept very similar tobitcoin-cli
api. This allows us to control the auto deployed backend node viaregtest-*
features from bdk-cli itself.std::Command
from rust. That can be used to simulate various wallet transaction situations with bdk-cli, like #87.repl
mode so now bdk-cli can have real time communication between a backend and a wallet in repl shell itself. Which can be very useful for quick runs of different testing conditions.Notes to the reviewers
@sandipndev @krtk6160. This is the PR you guys can start working on top of to simulate the intended test situations. At least with
bitcoind
it can be done with all existing toolings. For LND some other wrapper needes to be built.@notmandatory let me know what you think about the whole framework.
Also looking for more integration test ideas too add into.
basic
node
usage looks like thisChecklists
All Submissions:
cargo fmt
andcargo clippy
before committingNew Features:
CHANGELOG.md