What is Censorship Resistance?
Censorship resistance is the property of a decentralized network that guarantees any valid transaction can be included in the chain, and that no single party — not a government, not a corporation, not even a majority of validators — can reliably prevent specific users from transacting. It is one of the foundational value propositions of public blockchains: where traditional financial systems can freeze accounts, block wires, or comply with sanctions at the push of a button, a censorship-resistant chain is designed so that valid, fee-paying transactions go through regardless of who you are.
Censorship resistance is not binary. It exists on a spectrum determined by how concentrated block production is, how validators choose which transactions to include, and whether the network tolerates builders or sequencers that filter activity. Understanding where a chain sits on that spectrum is essential for evaluating its real-world resilience against political or regulatory pressure.
How Censorship Resistance Works / Technical Details
The Mechanism: Many Independent Block Producers
A chain is censorship-resistant when enough independent entities produce blocks that, even if some refuse to include your transaction, others will. The key metrics are:
- Number of distinct validators/miners — more producers means collusion to censor is harder
- Geographic and jurisdictional diversity — if validators span many legal jurisdictions, no single regulator can coerce them all
- Open, permissionless participation — anyone can spin up a validator or miner, so censors cannot statically target a fixed list
- Low latency to finality — the faster a transaction finalizes, the less window there is to censor it
Why Proof-of-Stake Chains Face New Risks
In proof-of-stake systems, a small number of large staking pools and liquid staking providers (such as Lido, Coinbase, Binance) control a significant share of stake. If a few of these were coerced or chose to censor, a large fraction of blocks could exclude targeted transactions. The danger is liveness vs. safety: Ethereum is designed so that censoring validators cannot prevent the chain from progressing (other validators build on top), but they can delay specific transactions, raising the effective cost and friction of being censored.
MEV and Builder Censorship
With MEV and MEV-Boost, a handful of block builders produce most Ethereum blocks. If the dominant builders choose to comply with sanctions (as some did after the Tornado Cash OFAC listing in 2022), transactions interacting with sanctioned addresses can be systematically excluded from the blocks those builders produce. This does not fully censor — other, non-compliant builders and validators can still include the transactions — but it raises latency and cost, demonstrating that censorship resistance is graduated, not absolute.
Notable Examples and Tension Points
The Tornado Cash Sanctions (2022)
When the U.S. OFAC sanctioned Tornado Cash smart contracts, several major MEV relays and builders began filtering transactions that interacted with the sanctioned addresses. For a period, a large share of Ethereum blocks excluded those interactions. The episode was the clearest real-world stress test of on-chain censorship resistance: the network did not fully censor (transactions still went through via non-compliant builders), but the compliance rate among infrastructure providers was high enough to matter.
Stablecoin Freezes
USDC, USDT, and other fiat-backed stablecoins include centralized freeze functions. The issuer can (and does) blacklist addresses, effectively censoring those holders. This shows that token-level censorship resistance depends on the asset: a self-custodied native coin is far harder to freeze than an issuer-controlled stablecoin.
Validator-Level Filtering
Some staking-as-a-service providers advertise “compliant” validation that excludes certain transactions. The more stake concentrates under such operators, the more the chain’s effective censorship resistance erodes.
How to Measure and Improve Censorship Resistance
Measuring It
- Builder/validator concentration — the Nakamoto coefficient and the share of blocks produced by the top few entities
- Inclusion latency — how long targeted transactions take to confirm versus average
- Compliance rate — fraction of blocks that exclude sanctioned or flagged interactions
Strengthening It
- Decentralize stake. Support independent validators, solo stakers, and distributed validator technology (DVT) that splits a single validator across multiple operators.
- Avoid single-sequencer rollups. Many L2s currently rely on a centralized sequencer that can censor at will; forcing sequencers to be permissionless or fall back to L1 inclusion (escape hatches) is critical.
- Encrypted mempools and PBS done right. Threshold-encrypted mempools and a well-designed proposer-builder separation can prevent builders from even seeing which transaction they are ordering, neutralizing targeted censorship.
- Run your own infrastructure. The more individuals and small entities run nodes and validators across diverse jurisdictions, the higher the baseline censorship resistance.
Frequently Asked Questions
Q: Can Ethereum be censored by governments? A: Fully censoring Ethereum would require coercing a large, globally distributed set of validators simultaneously — extremely difficult. Partial censorship (delaying or raising the cost of specific transactions) is more feasible, as the Tornado Cash episode showed, which is why researchers keep pushing for stronger protocol-level defenses.
Q: Is Bitcoin more censorship-resistant than Ethereum? A: Both are highly resistant in different ways. Bitcoin’s strength is its enormous, globally distributed mining and node network; Ethereum’s is its large validator set and rapid finality. Each has concentration risks in different places (mining pools vs. staking pools/builders).
Q: If my transaction is censored, what can I do? A: Raise the fee, route through a different builder or relay, use a non-censoring L2, or — if a rollup’s sequencer is censoring — trigger the L1 escape hatch to force inclusion directly on the base layer.