How to Tackle Timing Attacks on Automated Nodes?

Got a bit of a dilemma. I'm running cloudflare tunnels for my webhooks and only using tor for outgoing stuff. But I've noticed the timing between the webhook hitting the server and the tx going out is super obvious. Anyone knows how to add random delays to the broadcast? I'm really hoping there's a built-in option for this. Don't want to mess around with a custom Python script... What do you all think?

Sadly, there’s no simple way to do that. I remember someone else asking about adding a delay feature too, but no luck. Your best bet for reliable delayed broadcasting without slowing down your server would be to set up a cron job that manages your tx hashes. Write them into a file queue and then schedule a script to send them out. You can add timestamps for sorting but be careful with access, set locks to prevent collisions.

Consider separating the webhook from the broadcasting process. Just make the webhook throw the raw tx into a queue and get it done quickly, then have a scheduled job handle the broadcasting on its own schedule, throwing in some random delays. This gives you the needed jitter without hanging any requests and cuts down on the need for heavy scripts. But remember, this only helps against casual watchers. If someone keeps hitting your webhook and tracking mempool trades closely, they might still narrow you down unless you mix in some noise.

Yeah, I figured there wouldn’t be some easy toggle for that. I'm gonna take your advice and build out a Python daemon with a queuing system. Appreciate the link to that thread, just what I needed!