-
Notifications
You must be signed in to change notification settings - Fork 35
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
The fate of this repo #165
Comments
cc @RCasatta |
The fate of FWIW I agree it's wasteful to duplicate effort. I think it'd be better if we PR'd to this repo to use the new json crate rather than bitcoin-core-rpc, since that dependency is the real reason for the fork. |
I think its better not PRing to this repo because:
Those two things are what made me import it into the other repo and rename it. |
Ok, yeah, that makes sense. |
I think we should archive this repo and point users to |
What's the idea around Will there be further work on |
Recently I imported (stole) all the code from this crate and put it in the new
bitcoind-json-rpc
repository.There is a PR in flight at the moment to replace usage of this crate in
rust-miniscript
.We also have an open issue to move the new repo into the
rust-bitcoin
org.We should have a discussion about the fate of this crate. Note that in the new repo this crate is renamed so there is no reason the crate/repo cannot go on living. It seems like a waste of resources however to maintain two copies of basically the same code in the
rust-bitcoin
org.FTR I already got an explicit ACK by email from RCasatta to do the import.
The text was updated successfully, but these errors were encountered: