Contents
What's changing (and why)
Chainhooks has been very popular amongst builders in the Stacks ecosystem as a convenient way to be notified when new Stacks events happen on chain. However v1 has not been able to scale to the demand and the level of service we want to provide.
Chainhooks v2 is a total backend re-architecture that brings major improvements across the board:
- Better performance: Optimized indexing and event processing deliver faster webhook payloads and lower latency.
- Enhanced reliability: Improved infrastructure and scalability ensure your hooks stay active and responsive even during network disruptions or high load scenarios.
- Expanded filter support: More flexible filtering options let you listen to exactly the Stacks events you care about.
- Improved developer experience: Clearer documentation, better error messages, rich usage metrics, and more intuitive configuration.
If you've been using Chainhooks v1, now is the time to migrate to take advantage of these improvements.
"It has been working really well for me. Built a little admin panel as I track and monitor chainhooks offline. The ability to evaluate a single block has been really useful. Haven't seen a missed event yet... from a reliability perspective things have been great." -Tripnmonkey
What's being deprecated
As of March 9th, 2026, our Hiro Platform-hosted Chainhooks v1 will be fully deprecated and shut down. This includes:
- All Hiro-hosted Chainhooks v1 API endpoints
- v1 editing capability in the Hiro Platform
- v1 webhook delivery
- Legacy v1 documentation and support
If your application currently relies on Hiro-hosted Chainhooks v1, you'll need to migrate to v2 before March 1st to avoid service interruption. If you’re running Chainhooks v1 in your own infrastructure, you will not be affected. The Chainhook GitHub repository will remain as a public archive permanently but will not receive any further updates or development.
What Do I Need To Do?
To determine if you have v1 Chainhooks that need migration, log in to the Hiro Platform and navigate to the Chainhooks section. You’ll see any remaining registrations after selecting “v1.0” in the dropdown below. Follow the Migration Guide to see how to move these chainhooks to v2.
Timeline
- Today: Chainhooks v2 is generally available
- Now through March 9th, 2026: Both v1 and v2 remain available to give teams time to migrate
- March 9th, 2026: Chainhooks v1 will be shut down completely
We strongly recommend migrating as soon as possible to ensure a smooth transition and to start benefiting from v2's improvements.
Migration resources
- 📘 Chainhooks v2 Documentation: https://docs.hiro.so/en/tools/chainhooks
- 🧭 v1 → v2 Migration Guide: https://docs.hiro.so/en/tools/chainhooks/migration
- 🔧 v2 API Reference: https://docs.hiro.so/en/apis/chainhooks-api
Questions or need help?
We understand that every application is unique, and you may have specific questions or edge cases during your migration. If you need assistance, reach out to us in the #chainhooks channel of our Developer Discord. or email us at support@hiro.so. We're here to help ensure your transition to v2 is as smooth as possible.
Closing
Chainhooks v2 represents the culmination of feedback from developers like you who have been building with Chainhooks since the beginning. We're grateful for your patience during the beta period and excited to see what you'll build with the improved platform.
Thank you for being part of the Hiro developer community, and happy building with Chainhooks v2.
