Skip to content
Blockchain

Why can my wallet not verify whether the RPC node it trusted told the truth?

82

Opportunity

Almost every dApp and wallet routes its blockchain queries through Infura, Alchemy, or a comparable centralized provider. Those providers can return manipulated state, censor transactions, or go offline with no cryptographic consequence for the user. Light clients can check Merkle proofs for specific values but must bootstrap from a trusted header and rely on peers for data availability. A paper accepted at IEEE ICDCS 2025 identifies the core impasse: permissionless public RPC endpoints have no accountability, while registered providers have accountability but require permissioned access, and no financial incentive exists for altruistic full non-validating nodes to serve read traffic at scale. No production system combines cryptographic verifiability, open participation, and sustainable incentives in a single protocol.

Why it matters

If the RPC layer can lie without consequence, a user has no guarantee that the chain state they read is real or that their signed transaction was broadcast honestly.

How I score the opportunity

The Opportunity Score is my own read, not a measurement: how much it hurts, how often it bites, and how little exists to solve it today. Higher means I think it is more worth building.

Severity8/10

How much pain it causes when it shows up.

Frequency9/10

How often people actually run into it.

Whitespace8/10

How little good tooling exists for it today.

More problems worth solving