-
Notifications
You must be signed in to change notification settings - Fork 4
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
Join forces with my tonic_lnd? #28
Comments
It's awesome to know that there are other people working in the same space as us! That said, for our purposes at @bipa-app it's best to keep our open source version that we support. Comparing the projects I see they really are pretty similar, so there's more reason for us to keep our version than to make a change at the present time. That said it'd be awesome to see your project grow and even more awesome if you think contributing to |
Thinking about it maybe it'd make more sense to discuss our future plans with the libraries to see if we plan to do the same thing and thus we could split the work. For my use cases Eventually, I'd also like to write a separate, higher-level crate that would make the API more convenient (e.g I understand that you want to ensure reliability of your version and it's good that you do that. An alternative approach to your own library may be just having fork that you just sync with upstream and if shit hits the fan (upstream devs taking too much time for review) you deploy your change before merging upstream. There's also the trust issue. If there are multiple interested developers I'd like the crate to be developed using a GH organization. (possibly rust-bitcoin if folks over there agree)
|
I made and released the
tonic_lnd
crate and I wonder if you'd be interested in cooperating on a single crate which would be hopefully more efficient. From cursory look I don't see significant differences between our crates so switching shouldn't be too hard?The text was updated successfully, but these errors were encountered: