The XRP Ledger is the network every cashier sits on

Consensus, in plain terms

Most public blockchains people have heard of add new blocks through mining: computers compete to solve a puzzle, and whoever wins adds the next block. The network behind XRP runs on a different principle entirely. A set of independent validators compares the transactions they have each seen and agrees, through a process called consensus, on which set of transactions to include in the next ledger version. There is no mining, no puzzle to solve, and no single party that decides what goes in; agreement among the validators is what settles it.

That process happens continuously. Ledgers close roughly every three to five seconds, validating the transactions inside each one — deposits, withdrawals, any other payment on the network — together as a set. This is a property of the network itself, not of any casino's cashier: the pace at which ledgers close has nothing to do with how quickly an operator credits a deposit to your account, which is a separate, operator-specific decision written in that operator's own document rather than a network setting.

What the XRP Ledger means by “ledger,” versus a block

On a mining-based chain, a “block” is a single unit added to a growing chain, and its position in that chain is what makes it more or less trustworthy over time — more blocks built on top mean more confidence a transaction will not be reversed. The network here uses a different unit and a different guarantee. A “ledger” here is a complete record of the network's state at one point — every account, every balance, every open transaction — agreed on by the validators through consensus and then closed.

Once a ledger version is validated, in the network's own language, it is validated and final: there is no equivalent of “waiting for more confirmations” the way there is on a mining-based chain, because there is no growing chain to build confidence on top of. A payment is either inside a validated ledger, in which case it is settled and cannot be reversed by anyone, or it is not yet inside one. That binary outcome — settled or not yet settled — is one of the clearest practical differences between reading a transaction here and reading a transaction on a chain that works block by block.

The close time is a network rhythm, not a cashier promise

Ledgers close roughly every three to five seconds, continuously, whether or not anyone is depositing to a casino at that particular moment. That rhythm is stated here purely as a property of the network: it says nothing about how fast any operator this site tracks credits a balance, processes a withdrawal request, or runs any part of its own cashier queue. A payment settling on the ledger in a matter of seconds and an operator crediting that payment to a playable balance are two different events, decided by two different parties, and conflating them is one of the more common sources of confusion around a stuck-looking deposit.

Confirmation time covers that second event — the operator's own rule for turning a settled network payment into a balance you can actually use — as a separate subject from the network rhythm described on this page.

Accounts, and what it costs to hold one

Every account on the XRP Ledger is itself an object the network stores, and the network requires a minimum balance, called a reserve, to be kept in that account at all times — a floor under the account rather than a fee taken from it. That reserve is a network-level rule, unrelated to any casino, and it is why a wallet's displayed balance and the amount it can actually send are two different numbers; the difference between them is the part the network will not let leave. The account reserve covers the arithmetic in full.

What moving a payment actually costs

Sending a transaction on the network requires a small fee, paid in XRP and destroyed rather than collected by anyone — not by a validator, not by the network as an organisation, and certainly not by any casino. That destroyed fee is the entire cost the network itself imposes on a transfer; whatever a cashier separately states about its own charges is a different figure, set by that operator, and the two are not the same kind of cost. Network fees sets the two apart in full.

The two fields that decide who a payment is for

A payment on the XRP Ledger carries a destination account and, separately, a field many cashiers rely on to tell one depositor from another when they all share the same address: a destination tag. The ledger itself does not require this second field to be filled in — a payment sent without one still settles normally — which is exactly what makes it worth understanding on its own terms rather than assuming every wallet fills it in automatically. Destination tag covers what the field is, why an address alone is not always enough at a shared-address cashier, and what happens when it is left blank.

Reading the record yourself

Because the XRP Ledger is public, any transaction can be looked up by its hash, independent of what a casino's own dashboard shows. A handful of fields, read together, settle nearly any question a deposit could raise: what kind of transaction it was, which account it went to, what tag accompanied it if any, how much was sent, and metadata describing what actually arrived at the other end. Reading your own transaction walks through those fields one at a time, including the distinction between the amount a sender requested and the amount that was actually delivered — a distinction that matters more than it might seem, since the two are not always printed as the same figure.

Why this matters at a casino cashier specifically

None of the twelve operators this site tracks can change how consensus works, how quickly ledgers close, what a reserve requires, or what a network fee costs — all four are rules of the network, fixed for every account and every payment alike. What an operator can change is everything downstream of the network doing its part: whether a deposit is credited automatically or reviewed manually, whether a minimum applies, whether a withdrawal moves through an identity check first. Knowing which category a given rule falls into — the network's, fixed for everyone, or the operator's, specific to one cashier — is the most useful single habit for reading any XRP Ledger transaction in the context of a casino deposit.

That habit also explains why two operators can describe what looks like the same step in quite different words. One cashier's page might mention “confirmations,” language borrowed from mining-based chains, while another simply says a deposit is credited once a ledger closes; both are describing an operator's own crediting rule layered on top of the same underlying network event, not two different networks. Reading the operator's document for that layer, and this page for the network layer beneath it, is the combination that actually answers most questions about why a deposit looks the way it does at a given moment.

How a protocol fact like this turns into a score for a specific operator is shown on best ripple casinos, the site's own ranking page.