chainhook aggregator service #36
Conversation
possible deploy issue with preview URLs, on the other hand if generated per PR maybe can remove?
|
Noting we had to add migration and delete migration from #34 since we share the preview URL - next deployment from that PR will likely fail so we should close it out and revisit when ready. |
Co-authored-by: aider (openrouter/google/gemini-2.5-pro) <aider@aider.chat>
|
Noting we should add a fallback option to use the API websocket for new blocks instead of polling, that way we can at least get new block data, maybe backfill what's missing with rate limited calls, and avoid such a heavy load when things are down. The design will also allow for multiple API keys to define accounts and multiple chainhooks per account so should be easier to just get a whole bunch online and minimize failures. Also would be cool to have a dashboard that at least shows the latest data on all this. What's created, what's not, what's online, etc. |
|
Closing this out as we've implemented a solution in the backend instead |
we got a plan, man