The chain's cadence, not the cashier's crediting rule.
NEAR Protocol at
the cashier.
NEAR Protocol (NEAR) at a crypto casino. Confirmation: 600 ms blocks with 1.2-second finality. Network fee: Gas in yoctoNEAR, with most of the fee burnt and part rebated to contracts. No listed casino documents it yet. The cashier sets the deposit minimum and the crediting rule, not the chain. Checked 2026-08-23.
See the chain factsWhat this chain
actually does.
Checked 2026-08-23. Every figure below is the network's own published number, linked to the page that publishes it. None of it is a casino's claim about itself.
The operator's withdrawal fee is charged on top and is often larger.
No tag. Named accounts mean a casino can issue you a subaccount rather than share one address, so identification is usually built into the name itself.
NEAR is the native coin of NEAR.
Each figure,
with its source.
Four facts, four sources. Where a row says the claim is always true of the mechanism there is no link, because there is no dated page to link — the address format of a chain is a property of the protocol rather than an announcement.
| Fact | Figure | How to read it | Source |
|---|---|---|---|
| Confirmation time | 600 ms blocks with 1.2-second finality | NEAR's own announcement gives a 600-millisecond block time and near-instant 1.2-second finality. NEAR is sharded, so a transfer between accounts on different shards is routed as a receipt across them — which is why the honest figure for a deposit is the finality number rather than the block time. | NEAR — 600ms blocks and 1.2s finality |
| Network fee | Gas in yoctoNEAR, with most of the fee burnt and part rebated to contracts | NEAR prices gas in yoctoNEAR — 10^-24 of a NEAR — and burns the bulk of every fee. A share goes to the contract that was called, which means an application can be funded by its own usage. No other chain in this registry rebates part of the transaction fee to the callee. | Always true of the mechanism |
| Address format | A named account such as alice.near, or a 64-character implicit hex account | NEAR's account model uses human-readable names rather than key hashes, so a deposit address can be a word you can read and type. That is friendlier and more dangerous at once: a mistyped name may be a real account belonging to someone else, and it will not fail a checksum because there is no checksum to fail. | NEAR Docs — Account model |
| Settlement | Final at 1.2 seconds; query the finalised state, not the latest | NEAR's documentation tells integrators not to rely on the latest state and to specify the finality requirement in the RPC call, querying finalised state for custody purposes. A cashier reading latest state can see a deposit that has not yet finalised, which is exactly the mistake that finality parameter exists to prevent. | NEAR — 600ms blocks and 1.2s finality |
Why this page exists at all. NEAR is the only chain in this registry addressed by human-readable account names such as alice.near rather than by a key-derived string, with no checksum to catch a typo. It is also the only one that rebates part of every gas fee to the contract that was called, and the only one denominating gas in yoctoNEAR.
NEAR next to
Solana.
Solaspins is a Solana site, so this comparison is the one every coin page owes you: the same four facts for both chains, from both records, so you can see what changes when the cashier's network dropdown changes.
| Fact | NEAR Protocol (NEAR) | Solana (SOL) |
|---|---|---|
| Confirmation | 600 ms blocks with 1.2-second finality | ≈400 ms per slot |
| Network fee | Gas in yoctoNEAR, with most of the fee burnt and part rebated to contracts | 5,000 lamports (≈0.000005 SOL) per signature, plus any priority fee |
| Address | A named account such as alice.near, or a 64-character implicit hex account | Base58-encoded 32-byte ed25519 public key, 32–44 characters |
| Settlement | Final at 1.2 seconds; query the finalised state, not the latest | Commitment levels: processed, confirmed, then finalized |
| Memo or tag | Not needed | Not needed |
Read the Solana chain page for the full record, or the Solana casino list for the operators this site documents in depth. The full side-by-side, every fact from both records with the ones that agree kept in, is at NEAR Protocol vs Solana.
Wallets that
hold it.
No wallet in the Solaspins registry has been verified as holding NEAR, so this page names none. We list a wallet for a chain once we have read that chain on the wallet's own site — an unverified wallet recommendation is worth less than no recommendation, because it is the one thing on this page that could cost you the deposit.
Casinos documenting
NEAR.
No casino in the Solaspins directory has a record documenting NEAR yet. We will not list one until an operator's own cashier states it, because a table of casinos that might take NEAR is indistinguishable from a table of casinos that do — and only one of those is worth reading. The Solana list is where this site's documented operator coverage currently sits.
The three checks
that matter.
No wallet in the Solaspins registry has been verified as holding NEAR, so this page names none. That is a gap in our checking rather than a claim about the ecosystem — we list a wallet once we have read the chain named on the wallet's own site.
| Check | What to look for |
|---|---|
| The network | NEAR's account model uses human-readable names rather than key hashes, so a deposit address can be a word you can read and type. That is friendlier and more dangerous at once: a mistyped name may be a real account belonging to someone else, and it will not fail a checksum because there is no checksum to fail. |
| The memo | No tag. Named accounts mean a casino can issue you a subaccount rather than share one address, so identification is usually built into the name itself. |
| The crediting rule | The chain settles in final at 1.2 seconds; query the finalised state, not the latest. What the cashier does with that is its own policy, and its stated deposit minimum and confirmation count are the numbers that decide when you can play. We hold no account at any operator, so we record those as unconfirmed rather than reprinting them. |
Every figure on this page comes from documentation the network publishes about itself, read on the date shown. Nothing here is a casino's description of a chain, and nothing here is an estimate we made. Last verified 2026-08-23.