An off-chain backend for event-driven blockchain workflows, looking for feedback

Post original

Every project I work on ends up needing the same off-chain piece: a service that watches a chain, decodes the events I care about, retries delivery, and pushes the result somewhere useful. It's never the product itself, just plumbing, and it always takes longer than I expect. So we pulled it out into a standalone backend that's been running in production. It's called Atria, now in beta. First time showing it to ethdev, and I want to know where it falls short for real work. You point it at a chain, write your event filter in JS, and it fires a webhook on a match, all on top of RPC. What you get is the plumbing around it, reorg detection, cursors, delivery retries, and a test-against-a-real-block loop before you deploy. We're not an RPC provider. On cloud we handle the RPC for you, self-hosted you bring your own endpoint. Upfront about what's not there yet: no historical backfill (feeds only process forward from a block you pick, and that's the priority we're building now), and webhook is the only output today. Each feed reads one chain. For multi-chain you run a feed per chain into the same downstream, so watching several chains is just a matter of running more feeds. There's also a cloud AI assistant that drafts a feed from plain English, and a cloud MCP server so you can create and manage feeds from any MCP client. You can self-host it with docker-compose, the source is public. There's a hosted version too if you'd rather not run it yourself. - GitHub: https://github.com/Pulsy-Global/atria - Try it: https://pulsy.app/atria - Quick demo: https://youtu.be/M8p-grH4kOI - Quick start: https://docs.pulsy.app/atria/getting-started/overview It's in beta and I'm genuinely after feedback, so the questions I actually want answered: - How are you handling on-chain event ingestion today, and what's the most annoying part? - Which outputs should we add first (Postgres, S3, queues, something else)? - Which JS libraries would you want to require() inside a feed?   submitted by   /u/pulsylabs [link]   [comments]