Switch to xord with fallback to hiro #187
Merged
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.
🔘 PR Type
What kind of change does this PR introduce?
📜 Background
Hiro's indexer has a few issues. Some of the IDs are incorrect, Ordinals are assigned to incorrect owners, and it's often behind due to slow indexing.
We've brought up our own API, based on Ord, with the same interface in order to replace the Hiro API. This PR changes the endpoint used for inscription data to be our indexer primarily, and to fall back to Hiro's api if our indexer returns a 50X status code.
Further to this, the URl we retrieved ordinal content from was changed to our ord instance since Hiro's IDs are sometimes incorrect and they wouldn't have the content in the correct URL.
Issue Link: ENG-2478
🔄 Changes
Does this PR introduce a breaking change?
Changes:
We now use Xord for inscription data and our own ord for image content
Impact:
What to test:
✅ Review checklist
Please ensure the following are true before merging: