Skip to content
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

rpcclient: send legacy GetBlock request for backwards compatibility #1577

Merged
merged 1 commit into from
May 15, 2020
Merged

rpcclient: send legacy GetBlock request for backwards compatibility #1577

merged 1 commit into from
May 15, 2020

Conversation

wpaulino
Copy link
Collaborator

Without this, users of this library wouldn't be able to issue GetBlock requests to nodes which haven't updated to support the latest request format, namely the use of a single int parameter to denote verbosity instead of two bools.

I've confirmed through manual testing that these changes, along with #1560, provide full compatibility for bitcoind and btcd and provide backwards compatibility for btcd.

@wpaulino wpaulino requested a review from Roasbeef May 14, 2020 21:52
@wpaulino wpaulino mentioned this pull request May 14, 2020
@Roasbeef
Copy link
Member

Needs a rebase with the dependent PR merged.

@wpaulino
Copy link
Collaborator Author

@Roasbeef done.

Copy link
Member

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work around! We should also follow up on the lnd side with a PR that updates our CI to point against btcd master (temporarily) to make sure it works in our context as well.

In the end, I think putting some effort into the abstract HTTP-only client would allow us to keep up with the bitcoind changes for those users that use the rpcclient to interact with bitcoidn primarily, yet allow us to not have to break base btcd functionality.

rpcclient/chain.go Outdated Show resolved Hide resolved
rpcclient/chain.go Show resolved Hide resolved
rpcclient/chain.go Show resolved Hide resolved
Without this, users of this library wouldn't be able to issue GetBlock
requests to nodes which haven't updated to support the latest request
format, namely the use of a single `int` parameter to denote verbosity
instead of two `bool`s.
@wpaulino wpaulino requested a review from Roasbeef May 15, 2020 01:08
Copy link
Member

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🍕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants