Steem Bingo Goes Fully Serverless — No More Servers, No More Downtime

blaze.apps (75)verified developerin Steem Dev • 19 days ago

For a long time, Steem Bingo ran the way most blockchain apps do: one big Node.js process (blocks.js) sitting on a server, watching the chain, issuing tickets, running the nightly draw, and paying winners — all in one place, kept alive by a process manager and a lot of manual babysitting. If that one process crashed, stalled, or needed a restart, everything stopped: tickets, draws, payments, all of it.

That process is now retired. Steem Bingo runs on five small, independent Cloudflare Workers, each doing exactly one job, deployed at the edge with no server to patch, reboot, or lose sleep over.

What changed

Before:

One Next.js dashboard + one always-on Node process handling ticket issuance, the daily draw, and payouts together
A single point of failure — if it went down, the whole game stopped
A self-hosted MongoDB instance and a server to maintain

After — five focused Workers:

Worker	Job
🎫 `ticket-worker`	Polls for incoming STEEM transfers and issues bingo cards
🎲 `draw-worker`	Runs the nightly draw at 00:00 UTC — numbers, winners, everything
💰 `pay-worker`	Pays winners and the platform share, with independent on-chain verification of every payment
📰 `post-worker`	Posts the daily results report right here on Steem
📊 `dashboard-worker`	Serves the live stats site — rounds, players, winners, hall of fame

Each does one thing, restarts instantly if anything goes wrong, and the chain — draw → pay → post — now talks to itself directly at the edge instead of over the public internet.

Powered by our own Steem library

Cloudflare Workers don't run a normal Node.js server, so the usual steem library couldn't move over as-is. We built and now run on our own edge-compatible fork, @blazeapps/steem — same signing/broadcasting behavior the community already trusts, rebuilt to run natively at the edge.