Proposal: Allow querying multiple address info #350
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Currently, there is
/api/addr/[:addr][?noTxList=1&noCache=1]which can query 1 single address.I would like to query a list of 20 or so addresses so that I may see just if they have any related transactions. This is useful for implementations of BIP44 etc. and any other BIP32 chains with gap limits that need to know which addresses to generate.
My proposal is the following:
/api/addrs/[:addrs]/info[?noTxList=1&noCache=1]/api/addrs/infoIf there are performance issues / concerns, I think forcing noTxList=1 would be OK, as someone looking for all the transactions could use the tx api call.
If there are other places where code needs to be implemented, please let me know.
For now this is a WIP / proposal.