Self-hosting is useful, but I would still limit each key to the permissions the bot needs, with withdrawals disabled. For the fan-out layer, one test would disconnect a worker while the publisher keeps sending ticks, then reconnect it. The worker should detect the gap, rebuild its state from a snapshot, and keep new entries disabled until that state is current. Redis Pub/Sub alone does not replay the missed events.
Arnold Holm
Challenge Pre-Check: know before you risk. Your rules, tested against prop limits. Historical simulation, not a forecast.
Self-hosting is useful, but I would still limit each key to the permissions the bot needs, with withdrawals disabled. For the fan-out layer, one test would disconnect a worker while the publisher keeps sending ticks, then reconnect it. The worker should detect the gap, rebuild its state from a snapshot, and keep new entries disabled until that state is current. Redis Pub/Sub alone does not replay the missed events.