Consider moving this crate to `github.com/rust-bitcoin/corepc`

[tcharding]

Hey Riccardo,

Do you want to move this crate to corepc repo so that we update and release them in sync? It seems its inline with the stated aims of corepc repo which is officially

2. Provide tools for integration testing Rust code that interacts with the Bitcoin network.
   Primarily consumers of the [`rust-bitcoin`](https://crates.io/crates/bitcoin) library. And enable
   doing so against multiple versions of Bitcoin Core.

(ref: the readme in corepc)

And unofficially: "everything that rust-bitcoin devs don't really care about or want to work on but feel obliged to provide to the community as a service because it needs to exist"

[RCasatta]

I am fine moving this, what should I do exactly?

[tcharding]

As step 0, I invited you to be an owner of corepc-node - I should have done that soon as I moved/renamed bitcoind.

One way to do it would be after you tag and release 0.37 I could just manually pull it into corepc repo. We'd loose all the git history but the patch could include the commit hash in electrsd repo then we could archive that repo and update docs accordingly?

One thing still not sitting well with me is the rename of bitcoind to corepc-node I did, and if we move electrsd the naming becomes even more stark. Not sure right now what to do about that, any suggestions?

I could also make you a maintainer on corepc repo if you are willing to take on that burden? I wouldn't expect you to do anything but at least then you can merge things and release if needed/wanted.

Oh I've just realized that being an owner of corepc-node is not that useful without being an owner of corepc-types and corepc-client because they usually have to be released in sync. Bother. The aim of this issue was to reduce your stress not increase it.

How about we sit on this idea for a while and not rush.

[RCasatta]

any suggestions?

We can keep the crate name? I can give you permission on https://crates.io/crates/electrsd and we can move the code repository under corepc Il giorno ven 10 ott 2025 alle ore 18:46 Tobin C. Harding < ***@***.***> ha scritto:

…

*tcharding* left a comment (RCasatta/electrsd#113) <#113 (comment)> As step 0, I invited you to be an owner of corepc-node - I should have done that soon as I moved/renamed bitcoind. One way to do it would be after you tag and release 0.37 I could just manually pull it into corepc repo. We'd loose all the git history but the patch could include the commit hash in electrsd repo then we could archive that repo and update docs accordingly? One thing still not sitting well with me is the rename of bitcoind to corepc-node I did, and if we move electrsd the naming becomes even more stark. Not sure right now what to do about that, any suggestions? I could also make you a maintainer on corepc repo if you are willing to take on that burden? I wouldn't expect you to do anything but at least then you can merge things and release if needed/wanted. Oh I've just realized that being an owner of corepc-node is not that useful without being an owner of corepc-types and corepc-client because they usually have to be released in sync. Bother. The aim of this issue was to *reduce* your stress not increase it. How about we sit on this idea for a while and not rush. — Reply to this email directly, view it on GitHub <#113 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRLVLZ5W5ABWEQZ5L3D6VL3W7PHRAVCNFSM6AAAAACIR5JBCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJRGE2TSMZWGU> . You are receiving this because you commented.Message ID: ***@***.***>

-- Riccardo Casatta - @RCasatta <https://twitter.com/RCasatta>