When building decentralized applications, developers often face a critical question: does my product actually need a blockchain? Ethereum co-founder Vitalik Buterin recently shared a decision flowchart urging developers to start with the question: "Will the application benefit from global consensus?" If not, he suggests using other, more suitable tools.
This perspective challenges the common tech-driven approach, encouraging a shift toward needs-based reasoning. So, what exactly is "global consensus," and how do we identify the right use cases for a public blockchain like Ethereum?
Understanding Strict Global Consensus
In the context of public blockchains, "strict global consensus" refers to the requirement that every participant in a decentralized network must objectively agree on a specific set of outputs—such as transaction orders and final state changes. This is achieved through cryptographic proofs and decentralized validation, ensuring neutrality and censorship resistance without relying on any trusted third party.
Blockchain infrastructure, with scaling solutions like validity proofs and data availability sampling, is progressing toward extremely high transaction throughput. However, the real constraint isn’t technical capacity—it’s appropriateness. Not every application requires or benefits from such a strict form of global agreement.
Applications That Do Not Require Global Consensus
Many types of applications operate perfectly well—or even better—without relying on a global consensus mechanism.
- Data Storage: In the vast majority of cases, there is no need for every node in the world to store and validate all data. Solutions ranging from cloud storage to distributed protocols like IPFS or BitTorrent are more efficient and cost-effective for storing large amounts of information.
- Governance: On-chain governance modules, like those used by Aave, can handle straightforward voting. However, governance often involves complex, subjective human processes that cannot be fully captured or automated by rigid, objective code. Trying to force them onto a blockchain can lead to inefficiency or inaccuracy.
- Legal Contracts: The law is nuanced, interpretive, and context-dependent. While simple smart contracts can automate predefined conditions, they cannot handle the full breadth of real-world legal systems, which require human judgment and adaptability.
For these use cases, developers are encouraged to explore alternative Web3 or traditional technologies that better match their needs for scalability, cost, and flexibility.
What Is Best Suited for Global Consensus?
The ideal candidates for public blockchains are those dealing with objective value—assets or information that must be recorded and settled in a neutral, universally agreed-upon manner.
- Objective Money: This remains the flagship use case for blockchains. Bitcoin and Ethereum enable the creation and transfer of censorship-resistant, objective value. This foundation supports decentralized finance (DeFi), non-fungible tokens (NFTs), and other structures that require a neutral settlement layer.
- Objective Identity: While most identity attributes are subjective (e.g., reputation, qualifications), certain forms of objective identity can be anchored on-chain. Examples include Ethereum Name Service (ENS) domains or proof-of-attendance tokens (POAPs), which provide globally verifiable, neutral records.
- Filling Regulatory Gaps: Stablecoins like USDT and USDC are prominent examples. They leverage public blockchains to enable fast, borderless transactions that existing financial infrastructures may not support efficiently. It's worth noting that this need might diminish with the advent of well-designed central bank digital currencies (CBDCs).
- Niche Applications: Certain collaborative experiments, like on-chain storytelling or art projects, can also leverage global consensus for their unique requirements. However, these remain secondary to the core use cases of money and identity.
👉 Explore advanced blockchain development strategies
Some applications deploy on public blockchains primarily for token-based incentives or speculative mechanics, even if they don’t strictly need global consensus. However, the focus for sustainable development should be on achieving genuine product-market fit through utility—not just speculation.
Think in Terms of Features, Not Entire Products
Sophisticated dApps often adopt a hybrid architecture. They use Ethereum strictly for components that require global consensus—like final settlement or ownership records—while handling other functions (computation, storage, user interfaces) off-chain or with more appropriate systems.
A leading example is Farcaster, a decentralized social media protocol. It uses Ethereum for objective identity and key transactions but stores social content and interactions off-chain. This approach keeps costs low and performance high while preserving decentralization where it matters most.
As noted by thought leaders in the space, the unique selling proposition (USP) of a public blockchain is global consensus. Anything beyond that should use other tools. Future applications will likely be modular, combining various decentralized and centralized tools to create seamless user experiences.
For instance, a web3 game might run its logic on centralized servers for speed, host assets on IPFS, but record ownership of in-game items and identities on Ethereum—ensuring those critical elements are trustless and verifiable by anyone.
Frequently Asked Questions
What is global consensus in blockchain?
Global consensus is the process by which all participants in a decentralized network agree on the validity and order of transactions without relying on a central authority. It ensures that the state of the blockchain is objective, neutral, and tamper-proof.
Why shouldn’t all applications use Ethereum?
Using Ethereum incurs costs in transaction fees and development complexity. If an application doesn’t require censorship resistance, neutral settlement, or verifiable ownership, other systems may offer better performance, lower cost, and easier maintenance.
What are some examples of objective value?
Cryptocurrencies like ETH or BTC, tokenized real-world assets, digital collectibles (NFTs), and on-chain identity primitives like ENS are all examples of objective value that benefit from global, neutral settlement on a public blockchain.
Can legal agreements ever be fully on-chain?
While simple agreements can be automated with smart contracts, most legal contracts involve interpretation and context that current blockchain technology cannot process. Hybrid systems that combine on-chain execution with off-chain legal frameworks are more feasible.
How do I decide if my project needs a blockchain?
Start by asking if your application requires unstoppable, neutral, and global verification of data. If not, consider alternative databases or decentralized storage solutions. Let your product’s requirements guide your technology choice—not the other way around.
Is off-chain data still secure?
It depends on the implementation. Systems like Ethereum’s data availability sampling or zk-proofs can create strong security guarantees for off-chain data. However, critical data that impacts ownership or monetary value should be secured on-chain.
Building with blockchain technology requires careful thought. By focusing on the unique benefits of global consensus—and using the right tool for each job—developers can create more efficient, powerful, and sustainable applications.