Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/hirosystems/ordinals-explorer
Explore Ordinals inscriptions, using the Hiro Ordinals API powered by Chainhooks.
https://github.com/hirosystems/ordinals-explorer
bitcoin hiro ordinals stacks
Last synced: 2 months ago
JSON representation
Explore Ordinals inscriptions, using the Hiro Ordinals API powered by Chainhooks.
- Host: GitHub
- URL: https://github.com/hirosystems/ordinals-explorer
- Owner: hirosystems
- License: apache-2.0
- Created: 2023-04-10T16:31:25.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-07-23T12:46:56.000Z (6 months ago)
- Last Synced: 2024-09-27T00:19:45.284Z (3 months ago)
- Topics: bitcoin, hiro, ordinals, stacks
- Language: TypeScript
- Homepage: https://ordinals.hiro.so
- Size: 7.55 MB
- Stars: 32
- Watchers: 6
- Forks: 20
- Open Issues: 21
-
Metadata Files:
- Readme: README.md
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# Hiro Ordinals Explorer
➡️ https://ordinals.hiro.so 🌐
## Overview
The Ordinals Explorer is a Next.js (app router) project that uses the [Hiro Ordinals API](https://docs.hiro.so/ordinals).
There are two main parts of this project:
- The explorer `app/(explorer)` — A frontend for exploring ordinal inscriptions
- The preview API `app/(preview)` — An endpoint to render a specific ordinal inscription
## Development
```bash
cp .env.sample .env.local
```
```bash
npm install
```
```bash
npm run dev
```
Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
## Bugs and feature requests
If you encounter a bug or have a feature request, we encourage you to follow the steps below:
1. **Search for existing issues:** Before submitting a new issue, please search [existing and closed issues](../../issues) to check if a similar problem or feature request has already been reported.
1. **Open a new issue:** If it hasn't been addressed, please [open a new issue](../../issues/new/choose). Choose the appropriate issue template and provide as much detail as possible, including steps to reproduce the bug or a clear description of the requested feature.
1. **Evaluation SLA:** Our team reads and evaluates all the issues and pull requests. We are avaliable Monday to Friday and we make a best effort to respond within 7 business days.
Please **do not** use the issue tracker for personal support requests or to ask for the status of a transaction. You'll find help at the [#support Discord channel](https://stacks.chat/).
## Contribute
Development of this product happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving the product.
### Code of Conduct
Please read our [Code of conduct](../../../.github/blob/main/CODE_OF_CONDUCT.md) since we expect project participants to adhere to it.
### Contributing Guide
Read our [contributing guide](.github/CONTRIBUTING.md) to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes.
## Community
Join our community and stay connected with the latest updates and discussions:
- [Join our Discord community chat](https://stacks.chat/) to engage with other users, ask questions, and participate in discussions.
- [Visit hiro.so](https://www.hiro.so/) for updates and subcribing to the mailing list.
- Follow [Hiro on Twitter.](https://twitter.com/hirosystems)