A user downloads a browser wallet extension, sends Bitcoin to it, receives a confirmation, and considers the transaction final. But transaction finality depends on the underlying blockchain’s ability to remain secure against reorg attacks and 51% takeovers—risks that vary dramatically across different cryptocurrencies. Cake Wallet stores multiple assets: Bitcoin, Ethereum, Solana, Monero, and Litecoin. Each has a different hash rate, mining distribution, consensus model, and practical exposure to majority attack scenarios. The difference between “confirmed on-chain” and “safe from reversal” is not merely technical trivia; it determines whether a user should wait six more blocks, hold in escrow, or accept immediate settlement.

The cryptocurrency ecosystem often speaks about 51% attacks as abstract dangers—events that “theoretically could happen” but seem remote in practice. For a blockchain wallet user managing real assets across multiple chains, the relevant question is more specific: which coins in my wallet actually face a material 51% attack probability, how much hashpower would be required, and what would a successful attack cost compared to the value of funds at stake? The answer depends on current network conditions, mining centralization, and the exchange rate at the moment a transaction is broadcast. Understanding these risks before pressing send can prevent expensive surprises.

What a 51% attack actually means for wallet users

A 51% attack occurs when a single actor or coalition controls more than half of a network’s hash rate (for proof-of-work chains) or stake (for proof-of-stake chains) and uses that majority to reorg the blockchain, reverse transactions, or prevent competing blocks from being confirmed. For a wallet user, the threat is transaction reversal: funds that appeared to arrive have never actually settled, or a payment sent from the wallet could be reversed by the attacker to double-spend the same coins.

The practical window of vulnerability depends on confirmation depth and the attacker’s sustained hashpower. Bitcoin’s longest reorg on mainnet was approximately six blocks. Most exchanges and merchants require 6 to 12 confirmations for Bitcoin transactions. A 51% attacker could theoretically maintain a 51% hashpower advantage, mine faster than the honest network, and reorg deeper than that—but the resources required, the cost of attack, and the declining profit as the attack becomes visible make such scenarios rare in the modern era.

The key insight for a Bitcoin wallet user is that the threshold depends on profitability relative to the amount being attacked. An attacker with 51% of Bitcoin’s hash rate could theoretically reverse any transaction, but Bitcoin’s current hash rate exceeds 600 exahashes per second, making such control prohibitively expensive. A smaller network where hashpower is cheaper to rent or control presents a fundamentally different risk profile. The goal of analyzing each coin is to establish whether the attack cost exceeds the transaction value at stake.

Confirmation time also matters. A user receiving Litecoin, which has a 2.5-minute block time, will see six confirmations arrive in 15 minutes, whereas Bitcoin’s 10-minute blocks mean six confirmations take an hour. For some transactions, the time cost may be acceptable; for others, accepting a lower confirmation depth is a business decision. The wallet user’s role is to understand the chain they are using and the depth of confirmation appropriate for their scenario.

Bitcoin’s hash rate and the cost of a majority attack

Bitcoin’s security model depends entirely on proof-of-work hash rate. Current total hashpower on the Bitcoin network is approximately 625–650 exahashes per second. To control 51% of the network, an attacker would need roughly 320–330 exahashes per second. Modern Bitcoin mining hardware costs between $10,000 and $20,000 per petahash of sustained computation, and electricity is the dominant operating cost. Acquiring and operating 320 exahashes would require capital investment in the tens of billions of dollars, plus ongoing electricity costs measured in hundreds of millions annually.

The practical consequence is that Bitcoin’s 51% attack risk is not zero, but the attacker’s incentive and financing barriers are extreme. Even state-level actors would face a question of whether attacking Bitcoin is more valuable than alternative security investments. For a Ethereum wallet user or a user managing Bitcoin alongside other assets, the relative risk is important: Bitcoin’s cost of attack is orders of magnitude higher than that of smaller networks.

However, Bitcoin’s hash rate and mining distribution have changed over time. As of late 2024, the largest mining pools collectively represent a significant fraction of the network, though no single pool commands 51%. The risk is not that a single pool operator controls the majority but that multiple pools could collude, or that a regulatory change could pressure major mining operations to coordinate. Users evaluating transaction finality should treat Bitcoin as extremely secure for typical transaction values—six confirmations is widely considered safe—while acknowledging that the network does not eliminate risk, only makes it extraordinarily expensive.

The speed at which Bitcoin confirms transactions is also a design trade-off. A 10-minute block time provides statistical security against faster reorgs and gives the network time to propagate the longest chain. Higher throughput would require either larger blocks (increasing centralization pressure on node operators) or second-layer solutions (which involve different custody and routing trade-offs). For users who need faster settlement, Lightning Network channels or atomic swaps to faster chains may be more practical than waiting for on-chain finality.

Ethereum’s shift to proof-of-stake and the validator set concentration

Ethereum transitioned from proof-of-work mining to proof-of-stake in the Merge of September 2022. Under proof-of-stake, “miners” are replaced by validators who lock up Ethereum to participate in block proposal and attestation. A 51% attack becomes a question of controlling 51% of the staked Ethereum, not hashpower. As of late 2024, approximately 32 million Ethereum are staked across roughly 1 million validators.

The cost of a 51% attack on Ethereum under proof-of-stake is theoretically lower than Bitcoin because it depends on purchasing or borrowing Ethereum tokens rather than manufacturing specialized hardware. If an attacker bought 51% of staked Ethereum at current market prices, the capital requirement would be in the range of $60–80 billion (depending on the exchange rate). That is still a colossal sum, but it is lower than Bitcoin’s hardware-plus-electricity cost because the attack does not require manufacturing unique equipment.

The more relevant risk for Ethereum is validator set concentration. The largest staking pools—including Lido, Coinbase, and Kraken—collectively manage a large fraction of validators. If a single pool or a coalition of them acted maliciously, they could potentially reorg recent blocks. Lido alone represents roughly 30% of staked Ethereum. Most validators are still distributed, but the concentration is higher than Bitcoin’s mining distribution. The Ethereum community has discussed this risk seriously and considered limiting any single pool’s share, but no hard cap currently exists.

Users of an Ethereum wallet should understand that on-chain Ethereum transactions are less vulnerable to a 51% attack than smaller networks, but the validator set is meaningfully more concentrated than Bitcoin’s mining network. Six confirmations on Ethereum (roughly 1.5 minutes) provides statistical finality, though the Ethereum protocol does include a more formal finality mechanism where validators vote to “justify” and “finalize” checkpoints. For a user waiting for finality, understanding that Ethereum has both probabilistic and formal confirmation layers is useful.

Solana’s delegated proof-of-stake and validator concentration risk

Solana uses delegated proof-of-stake, where token holders vote for validators who process transactions. The network’s top 19 validators represent a significant fraction of voting power, and the top five validators exceed 30% of the stake. This concentration is substantially higher than Bitcoin or Ethereum, creating a meaningful attack surface: if five major validators coordinated, they could reorg the chain at will.

Solana’s design makes the cost of a 51% attack theoretically lower than Ethereum. An attacker needs to control validator nodes and their stake, not necessarily to purchase tokens. If a single entity controlled Solana’s major validator infrastructure or convinced five large validators to collude, a successful 51% attack could reverse recent transactions or prevent new transactions from being finalized. The network has experienced outages and validator issues in the past, demonstrating that the concentration is not merely theoretical.

Transaction finality on Solana is also faster than Bitcoin or Ethereum, with clusters of confirmations occurring in seconds. However, speed does not eliminate the 51% risk; it only changes the window during which an attack could be executed. A user receiving Solana in a blockchain wallet extension should wait longer than Solana’s nominal confirmation time before treating the transaction as final—or, more conservatively, wait for an explicit finality vote from the validator set if the transaction value is high enough to justify the delay.

Solana has also experienced periods where the network required a “restart” after disagreement among validators about the canonical state. This is not a 51% attack in the classic sense, but it demonstrates that Solana’s consensus is more fragile than Bitcoin’s and sensitive to validator behavior. Users should treat Solana transactions of high value with more caution than Bitcoin or Ethereum, accepting lower confirmation depth only for smaller amounts or shorter time horizons.

Monero’s ASIC-resistant mining and distributed hashpower

Monero uses a proof-of-work algorithm called RandomX, explicitly designed to be resistant to ASIC (application-specific integrated circuit) mining. The intent is to allow ordinary CPU and GPU hardware to participate in mining, distributing hashpower more widely and preventing the concentration of mining in large industrial operations. In theory, this makes Monero more resistant to 51% attacks because no single entity can easily accumulate dominant hashpower without controlling a large pool of consumer hardware.

In practice, Monero’s 51% attack risk depends on the current network hashpower and the cost of renting compute resources. As of late 2024, Monero’s estimated hashpower is roughly 3–4 gigahashes per second, compared to Bitcoin’s 625+ exahashes. The absolute numbers make Monero’s network appear fragile, but that is partly because the attack cost depends on the current exchange rate and the value at stake. An attacker would need to rent or control roughly 50% of the RandomX-capable computers on the internet or attract a significant fraction of Monero’s existing mining pool to collude.

The advantage of ASIC resistance is that it raises the entry barrier for a large-scale attacker: they cannot simply manufacture custom hardware in secret and deploy it. The disadvantage is that larger players can still accumulate compute power through cloud providers or distributed botnets. A user receiving Monero should wait for multiple confirmations (most wallets default to 10 for Monero), but the security profile is weaker than Bitcoin for equivalent confirmation depth due to the lower absolute hashpower cost.

Litecoin’s smaller network and lightweight block time

Litecoin uses the Scrypt proof-of-work algorithm and operates with a 2.5-minute average block time, making it four times faster than Bitcoin. The total hashpower is substantially lower than Bitcoin’s—roughly 1.5–2 terahashes per second compared to Bitcoin’s 625+ exahashes. This means the cost of acquiring 51% of Litecoin’s hashpower is much lower in absolute terms, though still substantial in comparison to the typical transaction value.

A 51% attack on Litecoin could be mounted more easily than Bitcoin simply because the hashpower is smaller. However, Litecoin’s smaller value may mean that attacking it is less profitable: reversing a $10 million transaction on Litecoin would require spending significant mining cost for a relatively low payoff. The ratio of attack cost to transaction value is more favorable for attackers on smaller networks, but it is not infinitely favorable.

For users managing Litecoin in a wallet, the standard practice of waiting for six confirmations is reasonable but slightly less protective than Bitcoin. A confirmation depth of 12 blocks (30 minutes for Litecoin versus one hour for Bitcoin) would be more conservative for high-value transactions. The faster block time makes Litecoin attractive for faster settlement but introduces a trade-off: each confirmation represents less total computational work than a Bitcoin confirmation, so the same number of confirmations provides slightly less statistical security.

Mining pools, exchange rate volatility, and real-world attack incentives

The theoretical cost of a 51% attack is only one part of the equation. The actual risk depends on whether an attacker’s incentive exceeds the cost. For Bitcoin, reversing a $100 million transaction might be profitable if the attacker gains $150 million from double-spending elsewhere—but the attack becomes visible, other miners will resist, and the attacker’s reputation is destroyed. Regulatory repercussions would likely follow. For smaller networks, the calculus can be different: attacking a chain with $50 million in transaction volume might require only $10 million in hashpower to control, creating a favorable ratio.

Mining pools add another layer. If a large pool operator wished to attack their own network, they could coordinate a reorg using their pool’s hashpower without acquiring additional resources. Most major mining pools have incentives not to do so—their reputation and long-term revenue depend on chain security—but the centralization of hashpower in pools means the risk is not zero. Users of a blockchain wallet storing assets across multiple chains should be aware that smaller networks are more vulnerable to this form of attack.

Exchange rate volatility also changes the attack incentive over time. A coin worth $100 each with $1 billion total market cap presents different attack economics than the same coin worth $200. As prices rise, the absolute hashpower cost to attack rises, but the transaction values at stake also rise. Users who suddenly receive or hold large balances in smaller-cap coins should be more cautious about transaction finality than users holding Bitcoin or Ethereum.

For users managing a wallet extension and moving assets between chains, Cake Wallet’s built-in swap functionality introduces additional considerations. When exchanging between chains with different 51% attack risks, a user should be aware that the source and destination have different finality guarantees. Swapping from Bitcoin to Solana, for example, means accepting different confirmation semantics. Reviewing available cake wallet / cake wallet download / cake wallet web documentation or support resources can clarify these trade-offs before executing a swap of significant value.

Practical confirmation depths and wait times by coin

The empirical standard for transaction safety varies by network and use case. Bitcoin exchanges typically require 6 confirmations, which at 10 minutes per block means roughly one hour. Larger deposits or transfers sometimes require 12 confirmations (two hours). This practice reflects both the statistical security of Bitcoin’s hashpower and the cost of reversing transactions: an attacker would need to sustain a majority for a full hour against the honest network, which is expensive.

Ethereum’s post-merge standard is less formally codified, but 12 confirmations (roughly three minutes) is widely accepted as final. Some services accept far fewer confirmations due to Ethereum’s higher transaction cost and the belief that reorg risk beyond a few blocks is negligible. However, users should not assume that a wallet showing “confirmed” means the transaction is safe from reorg; the wallet interface may simply show on-chain confirmation count without making a judgment about practical finality.

Solana’s faster blocks (roughly 400-millisecond slot time) and cluster-based finality model make confirmation depth less straightforward. A transaction might appear confirmed in under a second, but finality on Solana is better defined by an explicit vote from the validator set. Users should wait for explicit finality if the transaction is high-value, rather than assuming that speed equals security.

Monero’s 10-block confirmation standard is more protective than Bitcoin’s 6 confirmations because the absolute hashpower is lower, requiring deeper confirmation history to achieve equivalent statistical security. Litecoin follows Bitcoin’s convention of six confirmations but with the caveat that each Litecoin confirmation represents less cumulative work than a Bitcoin confirmation.

Managing wallet security across different 51% attack profiles

Users managing a multi-asset wallet should apply different security practices depending on the coin. For Bitcoin, the risk of a 51% attack affecting a specific transaction is vanishingly small for amounts under several million dollars. For Monero or Litecoin, the same absolute confidence requires either more confirmations or a lower transaction value threshold. For Solana, the validator concentration means that the confidence level depends more on whether the major validators have finalized the transaction than on confirmation count alone.

A practical approach is to calibrate confirmation wait time to the transaction value and the chain’s 51% attack cost. A $500 transaction on Solana might be acceptable after one slot; a $50,000 transaction should wait for explicit finality. A $10,000 transfer on Monero might require 10 confirmations; on Bitcoin, six confirmations provides similar confidence. Users of a blockchain wallet extension should develop the habit of checking the confirmation count and the target chain before concluding that a transaction is final.

Custody and wallet security interact with 51% attack risk in important ways. If a user controls their own seed phrase and private keys through a non-custodial wallet, the 51% attack risk is independent of the wallet provider—the chain’s own security is what matters. However, if the wallet uses a custodial model or delegates signing to a service, the custodian’s own security becomes a larger concern than the underlying chain’s 51% vulnerability. Cake Wallet’s local-only key storage and non-custodial architecture mean that users are not trading chain security risk for custodian risk in that regard.