I’ve been thinking a lot about a missing piece in the Cosmos dev stack — a simple state & event indexer + a webhook service. Basically, something that makes it way easier to track on-chain events in real time and react to them automatically.
Right now, tools like DefiantLabs/cosmos-indexer and KiFoundation/cosmos-indexer do a great job indexing chain data into structured schemas for querying, but I’m exploring building something that would give a bit more flexibility and has better UX for develoeprs— more like a reaction layer/querying layer. Ideally it should be flexible enought to easily add new modules to the system
Basically, you could set up triggers such as
-
“Ping me when a proposal passes”
-
“Alert when the validator set changes”
-
“Notify when a module parameter is updated”
Instead of just storing data, it’s focused on real-time reactions to Cosmos SDK events (or event cosmowasm contracts in the future) — something closer to Alchemy Webhooks but for Cosmos.
I’ve started putting together a small CLI prototype to test the concept, but before going too deep, I’d love to know:
-
Would something like this actually help in your day-to-day work, that would use it and give me feedback?
-
What are the biggest pain points you’ve hit when trying to react to chain data or automate workflows?
-
Are there other developer tools or services you wish existed in the Cosmos space?
I’m trying to validate if this solves a real problem or if there’s a better direction to explore — any feedback, ideas, or even critiques would be super helpful 