tbc: add block-by-hash command to RPC, use chainhash #224
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.
Summary
Add
tbcapi-block-by-hash
andtbcapi-block-by-hash-raw
commands to TBC RPC.Additionally, use
chainhash.Hash
for all hashes in RPC.Closes #219
Changes
tbcapi-block-by-hash
andtbcapi-block-by-hash-raw
commands to TBC RPC, these commands can be used to retrieve blocks by their hash.chainhash.Hash
instead ofapi.ByteSlice
for hashes in RPC. This is a breaking change. Raw RPC calls must now provide hashes in display-order as well.Utxo
asUTXO
consistently in thetbcapi
package. Initialisms should be all uppercase, per https://go.dev/wiki/CodeReviewComments#initialisms