wanted it to work more realtime so i added a tenderly alert. unfortunately it couldn't wake up github actions directly, so i had to add an intermediate cloudflare worker. but then i thought why not migrate to cloudflare worker wholesale. the architecture i ended up with is on worker that serves a static page. then tenderly could poke it using a webhook when new transactions arrive. it indexes them into d1 sql database, and also rebuilds a json dashboard that it serves from kv to the static page as api. i also added a daily cron as a fallback in case the webhook doesn't fire. it's all pretty simple, works well, and requires zero maintenance. you can also scale to more complex workflows using queues. overall i found cloudflare primitives quite pleasant to work with. for web3 webhooks the options i know are tenderly (3 alters on free plan) and alchemy (5 on free plan).
banteg
@banteg
04-01
learned a slightly cursed technique from @wavey0x but the more i thought of it, the more it grew on me.
he made a page to see all yearn/curve vesting escrows and it works really fast. when i asked what he uses to fetch the events so fast, he said that he doesn't fetch them at
From Twitter
Disclaimer: The content above is only the author's opinion which does not represent any position of Followin, and is not intended as, and shall not be understood or construed as, investment advice from Followin.
Like
Add to Favorites
Comments
Share
Relevant content
