Ethereum Foundation researchers have released a "Trustless Manifesto" that calls on developers to prioritize decentralization over convenience, marking a direct response to growing concerns about blockchain infrastructure becoming dependent on centralized cloud providers. The document, co-authored by Ethereum Foundation researchers Yoav Weiss and Marissa with input from co-founder Vitalik Buterin, argues that even small compromises in favor of centralized components can gradually erode the network's core purpose of enabling coordination without intermediaries.

What to Know:

• The manifesto defines trustless systems as those where any honest user can join, verify and participate freely without permission or fear of interference from central authorities.
• A recent Amazon Web Services outage demonstrated the risks of centralized infrastructure when Coinbase's Base chain lost roughly 25% of transaction capacity after its AWS-hosted sequencer went offline.
• The authors propose measuring blockchain projects by how much they reduce reliance on trust per transaction rather than by total transaction volume.

Foundation Warns Against Hidden Centralization Patterns

The manifesto builds on a core argument that Ethereum was designed to enable trustless coordination rather than to optimize financial efficiency. The researchers contend that protocols begin compromising their fundamental identity when they incorporate centralized elements such as hosted nodes or controlled relayers.

These decisions often seem minor initially but establish patterns that undermine permissionless access, the authors wrote.

The document emphasizes that true trustlessness requires every action to be fully verifiable through public data while preventing any single operator from becoming essential to system functionality.

"The manifesto is a statement of those values: credible neutrality, self-custody, verifiability, and resistance to 'convenient' centralization," the team stated in a social media post. The authors argue that simplicity built on external dependencies represents a loss of independence rather than genuine progress.

Cloud Provider Dependence Exposes Network Vulnerabilities

The manifesto points to expanding reliance on centralized infrastructure as evidence of gradual drift toward dependence. Major cloud providers now host significant portions of blockchain node infrastructure.

The recent Amazon Web Services disruption illustrated these risks in practical terms.

Coinbase's Base chain saw transaction capacity decline approximately 25% when its AWS-hosted sequencer stopped functioning. Arbitrum and Optimism maintained operations because they distribute infrastructure across multiple cloud providers.

The timing reflects mounting criticism of Layer 2 networks that have prioritized rapid scalability over complete decentralization. Optimism, Arbitrum and Base have faced scrutiny regarding single sequencer control and postponed decentralization roadmaps. Limited community participation in governance has slowed planned transitions to more distributed models.

Understanding Key Blockchain Architecture Terms

A sequencer processes and orders transactions before they reach the main Ethereum blockchain. Layer 2 networks use sequencers to batch transactions, reducing costs and increasing speed. When a single entity controls the sequencer, it creates a potential failure point and centralization risk.

Cloud providers like Amazon Web Services host the physical servers that run blockchain nodes. While cloud hosting offers convenience and reliability under normal conditions, dependence on any single provider contradicts the distributed architecture that blockchain technology aims to achieve.

Self-custody refers to users maintaining direct control over their digital assets without intermediaries. Verifiability means all network participants can independently confirm transaction validity using publicly available data.

Closing Thoughts

The manifesto introduces a framework for evaluating blockchain projects based on trust reduction rather than transaction throughput. Developers can sign the pledge by connecting their wallet, reading the document and confirming the transaction. Several Ethereum community members including Foundation member Tom Teman and researcher hitas.base.eth have already endorsed the initiative.