Hiro

We build developer tools for Bitcoin layers.

[Hiro @hirosystems]

Migrate to @xverse's L1 APIs (Runes, Ordinals, BRC20)

https://t.co/pJtG5kP80x

[Hiro @hirosystems]

🚨 Final 1-Day Notice for Devs

Reminder: Hiro’s hosted Chainhooks v1 and Bitcoin L1 APIs are being deprecated tomorrow.

If your app still relies on them, you’ll need to migrate ASAP to avoid service disruption.

Don’t get caught by a breaking change in production.

[Hiro @hirosystems]

Migrate to Chainhooks v2 🪝

https://t.co/b1a8ZhL1Ll

[Hiro @hirosystems]

The same goes for the Chainhooks v1 repo.

Always feel free to reach out to us in the Stacks Discord server as well.

https://t.co/NjEV0g9SVX

[Hiro @hirosystems]

As we approach the deprecation date (March 9th) for the Bitcoin L1 APIs (Runes, Ordinals, BRC20) and hosted Chainhooks v1, we'd like to explicity callout that the infra behind these can always be self-hosted.

We'll be leaving both the Bitcoin-Indexer and Chainhooks v1 publicly archived 👇

[Hiro @hirosystems]

The Bitcoin-Indexer repo contains information to help guide you setting this up if you're self-hosting.

Also refer to our docs for more info.

https://t.co/D8Q8vvgfbY

[Hiro @hirosystems]

For migrating from Chainhooks v1 to v2:

https://t.co/b1a8ZhL1Ll

[Hiro @hirosystems]

🚨 DEPRECATION REMINDER 🚨

We are 1 week out from deprecating the L1 API tools and hosted Chainhooks v1.

Both will be deprecated on March 9th.

If you are still relying on either of these, please migrate ASAP. More info below.

[Hiro @hirosystems]

For migrating L1 APIs to @xverse's L1 APIs:

https://t.co/pJtG5kP80x

[Hiro @hirosystems]

🚀 Chainhooks v2 is now generally available and officially out of beta!

This release brings major improvements in reliability, performance, and dev experience.

As part of the transition, the hosted Chainhooks v1 will be deprecated on March 9th.

https://t.co/b1a8ZhL1Ll

[Hiro @hirosystems]

The Bitcoin ecosystem evolves fast — and so do we.

Hiro will be deprecating its L1 Bitcoin tooling (Ordinals, Runes, BRC-20, Bitcoin Indexer) and partnering with @XverseApp to ensure an easy transition for devs.

What’s changing + how to migrate 👇

https://t.co/pJtG5kOAaZ

[Hiro @hirosystems]

Sharpening focus. ⚡️

Chainhook v2 is GA, and soon we’re sunsetting BTC L1 APIs + Chainhook v1.

We’re doubling down on Stacks—and partnering with @xverse to make the transition smooth.

Onward.

[Alex Miller @alexlmiller]

ICYMI, there's some IMPORTANT @hirosystems updates

(1) Chainhook V2 is now GA

(2) Our BTC L1 APIs + Chainhook V1 will be shut down on March 1st

This is part of our streamlined focus on Stacks, and we've partnered with @xverse for an easy transition

Full details & guide ↓

[Hiro @hirosystems]

🚀 Chainhooks v2 is now generally available and officially out of beta!

This release brings major improvements in reliability, performance, and dev experience.

As part of the transition, the hosted Chainhooks v1 will be deprecated on March 9th.

https://t.co/b1a8ZhL1Ll

[Hiro @hirosystems]

As the ecosystem matures, focus matters.

Hiro is doubling down on core Stacks infrastructure, while L1 metaprotocol indexing and wallet-centric workflows move to teams best positioned to innovate on them.

Xverse has been leading here — which is why we’re recommending @XverseApp for Ordinals, BRC-20, and Runes APIs.

[Hiro @hirosystems]

The Bitcoin ecosystem evolves fast — and so do we.

Hiro will be deprecating its L1 Bitcoin tooling (Ordinals, Runes, BRC-20, Bitcoin Indexer) and partnering with @XverseApp to ensure an easy transition for devs.

What’s changing + how to migrate 👇

https://t.co/pJtG5kOAaZ

[Hiro @hirosystems]

An important update on the Stacks API - it's going to be transitioning to Stacks Labs and getting even better.

[Alex Miller @alexlmiller]

Hey Stackers, as we enter another exciting year for the Stacks ecosystem, I have some updates about Stacks Labs, Hiro, and developer tooling:

➡️ We’re doubling down on the increased efficiency we’re seeing from running core development out of Labs by moving the Stacks API and Chainhook from Hiro to Stacks Labs over the next few weeks, along with some of the team.

The API is heavily dependent on the node, by bringing these teams together, we can solve problems holistically, make changes at whatever layer makes sense, and ship faster. For instance, by reworking what the node outputs directly, we can dramatically simplify the API and infrastructure layers, which means better performance, lower costs, and greater reliability for builders.

➡️ For those of you with paid API plans: nothing changes, you keep your same access. And product development continues with API v9 and Chainhook v2 rollouts.

➡️ As part of this transition and the SIP-31 commitment, Hiro is contributing several million dollars of BTC to the Endowment. We'll publish the on-chain transaction once completed.

➡️ Thanks to SIP-31 and recent Treasury Committee approvals, Labs is well capitalized and ready to drive huge growth in 2026! ICYMI, check out my recent overview on Stacks R&D heading into the year:

https://t.co/gYOyGSJ9GC

[Hiro @hirosystems]

See full release notes: https://t.co/QIkVidzOgF

[Hiro @hirosystems]

Stacks Blockchain API v8.13.6 is live 🚀

This is a required upgrade for all API users (incl. partners & exchanges): adds support for smart contracts deployed with empty source code.

It's an easy upgrade: no DB migrations, and fully compatible with the current chainstate.

[Hiro @hirosystems]

Tenure extension transactions will start rolling in by next week, so make sure to update by then!

Release notes: https://t.co/XVGM9lVBF7

[Hiro @hirosystems]

🚀 Stacks Blockchain API v8.13.5 is live

This is a required upgrade for all API operators: adds support for new SIP-034 tenure-extend causes landing in the next Stacks core release.

✔️ No DB migrations
✔️ Fully backwards-compatible
✔️ Prevents API stalls once new tenure extends hit mainnet/testnet