Methodology: how we verify and what we won't claim
ChainDeposit covers a high-stakes, panicky moment — money that might be stuck. That makes accuracy and honesty non-negotiable. Here's exactly how our information is built and where its limits are.
The sources we use, in order
Every figure on this site traces back to one of two primary sources, and nothing below them. There is a strict order:
- Protocol documentation and block explorers — for how a chain actually behaves. The XRP Ledger and Stellar specs tell us which assets require a destination tag or memo. Explorers like Etherscan, BscScan, Tronscan and Solscan show real transactions, confirmation behaviour and address formats. These are properties of the networks, not of any casino, and they drive the core verdict in our how the checker decides recoverability.
- Each operator's own help centre and Terms — for that operator's deposit rules: supported networks, minimums, confirmation thresholds and any stated recovery policy. We read the operator's published pages, not a summary of them.
That is the whole list. We do not cite affiliate roundups, comparison blogs or aggregator sites for any deposit fact. If a claim cannot be traced to a chain's own behaviour or an operator's own words, it does not go on the page.
"Verified" versus "verifying"
A per-operator figure is published only when it sits on a primary source and carries a date. When an operator does not publish something — an exact confirmation count, a recovery fee, the real time a credit takes to land — we mark that field "verifying" rather than print a number we cannot stand behind. This matters because gambling deposit pages sit squarely in territory where a wrong figure can cost a reader real money. A blank we are honest about is safer than a confident guess. As we complete first-hand test deposits, "verifying" fields become dated, sourced entries.
How the checker decides recoverability
The checker logic reasons from how the chains work, not from any promise an operator has made. It applies the network-family rule: send on the same network the operator credits and funds arrive; send a different EVM chain to the same 0x address and the deposit is sometimes sweepable, because the operator controls that key across EVM chains; cross between families — EVM to Tron, or to Solana — and recovery is generally off the table, because the addresses are not interchangeable. This is guidance, not a guarantee. The operator that received your funds is always the final authority on your specific transaction. If your coins went the wrong way, start with our wrong-network guide, then contact that operator's support.
Our stance on recovery scams
Funds can only ever be recovered by the operator that received them or the exchange that sent them — directly and for free. We will never recommend, and you should never pay, a third-party "recovery service". Any up-front fee or request for your seed phrase is a scam, full stop.
Affiliate transparency
Some outbound links are affiliate links (marked, and routed through /go/). If you open an account through them we may earn a commission. This never changes the deposit facts on any page, the verdicts in the checker, or what you pay. See about us.
Re-verification and corrections
Deposit terms are not static: operators add networks, change minimums and adjust confirmation thresholds without notice. Each operator page therefore carries its own date and is re-checked against the operator's current Terms on a rolling basis. If you spot something stale or wrong, tell us via contact and we will re-verify against the primary source and correct the page, with a fresh date. Reader reports are one of the fastest ways we catch a change.
FAQ
Does ChainDeposit guarantee my deposit will be recovered?
No. We explain how the chains work and what is generally recoverable, but the receiving operator or exchange is always the authority on your specific transaction. We never promise an outcome.
Where does your data come from?
Two layers: protocol-level facts (memo requirements, network families, block times) that are properties of the chains; and per-operator specifics that we verify first-hand or from official sources, each stamped with a date and source. Anything unverified is withheld, not guessed.