Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate Hiro Ordinals API #3417

Closed
markmhendrickson opened this issue Mar 13, 2023 · 2 comments · Fixed by #3654
Closed

Integrate Hiro Ordinals API #3417

markmhendrickson opened this issue Mar 13, 2023 · 2 comments · Fixed by #3654
Assignees
Labels
area:ordinals area:performance enhancement-p3 Non-critical functionality wanted by many users, or there are clear alternatives

Comments

@markmhendrickson
Copy link
Collaborator

markmhendrickson commented Mar 13, 2023

For performance gains, replacing ordapi.xyz usage

https://docs.hiro.so/ordinals

@markmhendrickson markmhendrickson added Enhancement 💡 enhancement-p3 Non-critical functionality wanted by many users, or there are clear alternatives area:performance area:ordinals labels Mar 13, 2023
@kyranjamie
Copy link
Collaborator

Should allow us to query by address

@markmhendrickson
Copy link
Collaborator Author

This is blocked by hirosystems/ordinals-api#23

@markmhendrickson markmhendrickson linked a pull request May 7, 2023 that will close this issue
blockstack-devops pushed a commit that referenced this issue May 12, 2023
## [4.24.0](v4.23.0...v4.24.0) (2023-05-12)

### Features

* add hiro api test ([db53c6d](db53c6d))
* change ordapi to hiro ordinals api, closes [#3417](#3417) ([73a2957](73a2957))
* send inscription choose fee, closes [#3544](#3544) ([45c090f](45c090f))

### Bug Fixes

* **brc-20:** handle bad response ([3775a6c](3775a6c))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:ordinals area:performance enhancement-p3 Non-critical functionality wanted by many users, or there are clear alternatives
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants