-
Notifications
You must be signed in to change notification settings - Fork 100
Bitcoind REST sync #496
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
Comments
Hmm, I'm not fully convinced, could you reiterate the benefits over RPC, besides the absence of any authentication method?
No, actually we're not using the |
Abscence of auth is really important, eg it means you can run one bitcoind and have multiple services talk to it, without the ability to do things like stop the node, disconnect all its peers, etc.
Nontrivial - you skip the JSON + hex encoding for various things and can fetch straight binary. Maybe more important, you can trivially slap nginx in front of it and cache block data and the like rather than having bitcoind load it from disk. |
Ah, right. Thanks for refreshing my memory. I agree we should go for it, should be easy enough. |
Hi @tnull, happy to take this on if it's unassigned. Are there any specific considerations or preferences you'd like me to keep in mind before I get started? |
Cool, go for it!
I think generally you'll want to keep it as analogous / DRY as possible w.r.t. the RPC variant. You'll want to use Also note that we're planning to do a bunch of cleanups/refactors/code moves in the |
Thanks. |
Its probably not all that important and most folks wouldn't use it, but if its possible to do a sync via bitcoind REST easily, it'd be nice to support. I assume BDK would have to support it and that's kinda it since LDK already does?
The text was updated successfully, but these errors were encountered: