new xyzpub API returns txids #436
Merged
Conversation
This file contains 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
janoside
added a commit
that referenced
this pull request
May 18, 2022
-move /api/xyzpub/:xyzpub to /api/xyzpub/txids/:xyzpub -move /api/util/xyzpub/:xyzpub -> /api/xyzpub/:xyzpub -rename xyzpubAddressApi -> xyzpubApi and move more functionality from apiRouter there -searchXpubTxids: return more details about the search, then in the apiRouter just use what's needed -fix in searchXpubTxids: reset gapCount value when tx is found -update api docs -update changelogs
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.
This new xyzpub API endpoint will return a list of txids associated with the xyzpub.
If limit parameter is not set then it will grab all txids associated with the xyzpub.
If limit is set it will grab only txids associated with the limit amount of receive and change addresses. Eg. limit is 1 means 1 receive and 1 change address, the first one in the bip32 path.
My plan is to use this endpoint with my bitcoin-reports.com site. I'm returning only unique txids to make the size of the result as small as possible. As well I do not want to fetch more than txids as it will slow down the endpoint.