Does Ripple control XRP or the XRP Ledger, and can it freeze my coins?

The full answer

The XRP Ledger’s own documentation answers the freeze question directly: “No one can freeze XRP in the XRP Ledger.”[1] It also says “XRP is not a token and cannot be clawed back.”[2] That applies to Ripple as much as to anyone else. Control of the ledger itself is a separate question, and the answer there turns on validators and on who publishes the default validator lists that servers start from.

Why can tokens issued on the ledger be frozen when XRP cannot?

XRP is the ledger’s native asset. Everything else on the ledger is a token created by an issuer, and the ledger gives issuers tools XRP does not have. An issuer can freeze a single holder’s trust line so the holder cannot move the balance except back to the issuer, or apply a global freeze to all of its tokens. An issuer that switches on “No Freeze” permanently gives up the ability to freeze at will.[1] Clawback is stricter: an issuer can only switch it on before it has issued anything.[2] The full comparison is on whether XRP can be frozen or clawed back.

What happens to my XRP if an exchange freezes my account?

The ledger rule protects XRP held in an address whose keys you control. It does not protect XRP held for you by a company. Coinbase’s US user agreement, updated July 22, 2026, is one example: it says Coinbase may suspend or restrict an account “with immediate effect for any reason at its sole discretion.”[3] The trade-offs between an exchange account and your own wallet are on exchange or own wallet.

Who chooses the validators?

Each server keeps a Unique Node List (UNL), which XRPL.org defines as “a server’s list of validators that it trusts not to collude.” By default, servers use two published lists, one from the XRP Ledger Foundation and one from Ripple. XRPL.org also says: “Each server operator has full control over which validators are in their UNL.”[4]

XRPL.org’s FAQ says the network has “150+ validators” with “35+ on the default Unique Node List,” and that, as of July 2023, “Ripple runs only 1 of the 35 validators in the default UNL.”[5] On September 29, 2026, the explorer xrpscan’s amendment data showed 35 validations, with 28 needed for an upgrade vote to pass.[6] XRPL.org says the two default lists are typically “very similar to one another or even identical.”[4]

So Ripple’s direct share was 1 validator in 35 at the FAQ’s July 2023 date, the latest figure it gives. Its larger influence is as one of two publishers of the default list. XRPL.org says list publishers “wield significant power in selecting which validators are widely trusted.”[4] How much the lists overlap, and whether that amounts to central control, is argued in full on the validator centralization critique.

How many validators would have to collude to censor or halt transactions?

XRPL.org says consensus continues while “less than about 20%” of trusted validators misbehave. If “more than about 20%” are unreachable or misbehaving, “the network fails to reach a consensus.” To confirm an invalid transaction, at least 80% of trusted validators would have to approve it.[7] xrpscan’s data counted validations, not trusted validators. If those 35 validations stand for 35 trusted validators (our calculation), 8 or more failing could stop the ledger, and 28 would have to collude to confirm an invalid transaction. The XRPL.org consensus pages give no separate threshold for censoring a single transaction.

Researchers Ignacio Amores-Sesar, Christian Cachin and Jovana Mićić, in an OPODIS 2020 paper, give “a detailed, abstract description of the protocol, which has been derived from the source code,” and say the abstract protocol “may violate safety and liveness in several simple executions under relatively benign network assumptions.”[8] XRPL.org itself says that in the worst case, servers’ lists must overlap by 90% to prevent the network splitting, up from an earlier belief of 60%.[4]

The ledger has stopped before. On February 4, 2025, it stopped confirming new ledgers for about an hour, and Decrypt reported no loss of assets. Ripple CTO David Schwartz, as Decrypt identified him, said validations “were not being published” and that servers “did not report any ledgers as trusted during the incident.”[9]

Could Ripple move the market through the XRP it holds?

Holding XRP is different from controlling the ledger. Ripple’s Q1 2025 markets report gave, as of March 31, 2025, 4,562,433,147 XRP held directly and 37,130,000,005 XRP in escrow.[10] That is about 41.7% of the 100 billion created (our calculation). Ripple’s XRP page, checked September 29, 2026, gives a later figure: 37,656,053,914 XRP held by Ripple as of June 30, 2026, which it describes as XRP in its wallets plus XRP in escrow, with 32,600,000,000 XRP placed in escrow.[11] That total is about 37.7% of the 100 billion (our calculation). crypto.news reported on September 1, 2026 that about 31.28 billion XRP remained in on-ledger escrow after the September release, “according to an independent tracker that queries validated XRP Ledger data.”[12] Whether Ripple’s sales weigh on the price is examined on is Ripple dumping XRP.

How does XRPL’s validator distribution compare with other chains?

Direct comparisons are rough, because each network gives power to different people. On Bitcoin, new blocks come from miners grouped in pools. In the month to September 29, 2026, mempool.space data showed Foundry USA finding 1,163 and AntPool 888 of 4,584 blocks, about 44.7% between two pools (our calculation).[13] On the XRP Ledger, Ripple ran 1 of 35 default-list validators as of July 2023.[5] In our reading, the XRPL concentration sits in the default lists, where two publishers set the default starting list for servers.[4]