How does withdrawal batching work at crypto roulette casinos?

Withdrawal batching is the practice of collecting many players’ withdrawal requests over a short window and sending them all in one transaction with many outputs, rather than one transaction each. On Bitcoin, the savings are large because a transaction with one input and fifty outputs is around 1,700 bytes, while fifty separate transactions are around 7,000 bytes together. The batch pays a quarter of the fee, and the casino passes some or all of that savings on as a lower withdrawal fee. The cost to the player is that a withdrawal waits for the next batch rather than leaving at once.

Most roulette games with crypto sites batch bitcoin, litecoin and bitcoin cash withdrawals, since those chains charge by size. Ethereum and Tron withdrawals are usually sent singly because batching on those chains saves little. Here is how one bitcoin batch is built.

1. The window opens – The site sets a batch interval, commonly every ten, fifteen or thirty minutes. Withdrawal requests made during the interval are held in a queue rather than being signed immediately.
2. Requests are screened – Each request is checked against the account’s withdrawal cap and the automatic approval threshold. Requests above the threshold are pulled out for manual review and join a later batch once approved. Everything else stays in the queue.
3. The batch is assembled – At the end of the window, the hot wallet builds one transaction. It selects enough inputs to cover the total, adds one output per player at their withdrawal address, and one change output back to itself. Fifty requests become fifty outputs in a single transaction.
4. The fee is set – The wallet queries a fee estimator for the rate needed to confirm within the site’s target, usually one to three blocks, and multiplies it by the transaction’s size. The total fee is divided across the outputs, which is how a per-player fee of a few hundred satoshis can appear on a day when a single transaction would cost thousands.
5. The batch is signed and broadcast – One signature covers all fifty outputs. The transaction is sent to the network, and its ID is recorded against every request in the batch.
6. Confirmation – When the block containing the batch is mined, every output confirms at the same moment. All fifty players see their coins arrive together.

From the cashier, the same six stages look like this

• Requested – Your withdrawal shows as pending with no transaction ID. It is in the queue for the next window.
• Processing – The window has closed, and the batch is being built and signed. A short delay of a minute or two.
• Sent – A transaction ID appears. On an explorer, it shows as one transaction with many outputs, and yours is one of them. If you see other amounts to other addresses in the same transaction, that is the batch, and nothing is wrong.
• Confirmed – The block arrives, and the coins are spendable. The fee shown against your withdrawal is your share of the batch fee.

Two things follow from batching. A withdrawal requested one minute after a window closes waits nearly the full interval before it is sent, so a site with a fifteen-minute batch can take up to fifteen minutes plus confirmation time, and that is normal rather than a delay. And if a batch confirms slowly because the network got busy after the fee was set, every withdrawal in it waits together, and the site’s fee bump lifts them all at once.