Add /address/:address/ JSON API endpoints #4008
Closed
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
…PI endpoints for fetching runes and inscriptions UTXOs
|
@raphjaph Any thoughts on this? |
lifofifoX
added a commit
to TheWizardsOfOrd/ord
that referenced
this pull request
Nov 7, 2024
|
I think we should go with something like this: #4056 What do you think? |
|
Closed by #4056 |
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 is branched off #3979
In addition to the
/address/:address/cardinalsendpoint, this PR adds/address/:address/runesand/address/:address/inscriptionsendpoints.This PR also groups all the
/address/:address/*tests. That way, we don't need a dedicated test to check that inscriptions/runes are excluded from/address/:address/cardinals.