doc: correct deriveaddresses RPC name #26424
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Zero-1729
reviewed
Oct 30, 2022
Contributor
Zero-1729
left a comment
Zero-1729
left a comment
There was a problem hiding this comment.
Concept ACK
It seems it was most likely a typo, given the RPC name is accurate at the beginning of the doc.
Perhaps, consider making the commit more explicit about the change, i.e. doc: correct deriveaddresses RPC name or something similar.
Contributor
Author
Done |
bitcoinhodler
changed the title
Zero-1729
approved these changes
Oct 30, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There never was a
deriveaddressRPC, from what I can tell. It was always calledderiveaddresses(plural).