I've been putting this off for a few days. It feels like a big job, I need to basically remove a lot of old "ways of going about things", nodes, and start querying the orderbook database instead of relying on websocket messages themselves. I feel like having our own local "game loop" sort of clock will be more conducive to our style of trading (market making), so instead of being reactive to every single market change, we can look at the up to date book every at sub-second intervals to recalibrate our orders and model. Right now, since I built the system as an IV chart with dreams of trading, one of the major flows takes non-authenticated book top messages from the FTX US Derivatives websocket and calculates an IV surface, updating an SQLite db with a theoretical IV for each contract (along with it's actual bid and ask IVs) From there it sends messages to the front end which are rendered as charts. You can see how this will end up rooting up old code and throwing it out in favor of a more local "polling" type system that checks the in memory SQLite db state and generates the IV surface. From there we can send messages like we were, but it should be much less hard on the CPU since websocket messages could arrive in bursts causing the system to calculate 10s of IV surfaces and render them per second... This new way would allow us to take control of the amount of CPU to use and have better control of our timing and certainty of the exchange book state (I hope). It should also make programming and testing various algorithms easier. I don't know if it's the right move or not, but it seems to be.

I hope no one searches up these streams hoping to find a tutorial, it's mostly me bumbling around figuring stuff out Looking to figure out the Node-RED dashboard (particularly the template node along with chart.js) this time