fix: use address UTXO endpoint - #2
Open
manuelsampedro1 wants to merge 1 commit into
Open
Conversation
|
Review-assist note for the Bitgesell #81 improvement lane. I checked the public PR metadata and diff. This is a focused Go SDK endpoint fix:
Suggested maintainer checks before merge:
From the public patch shape, this looks like a useful low-risk SDK correctness candidate for the #81 improvement queue. I did not run Go tests, connect to a node, use wallet keys, submit payment details, or perform any live-chain action for this review-assist note. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GetAddressUTXO currently calls the unconfirmed transactions endpoint, so callers requesting UTXOs receive transaction-history data instead of the address UTXO response.
Changes:
/address/utxo/{address}Cross-checks:
/address/utxo/{address}for UTXOsValidation:
rgacross the toolkit, wallet client, and bglapiserver route usageNote: I could not run
go test ./...in this local environment because the Go toolchain is not installed here.Bounty context: BitgesellOfficial/bitgesell#39