Vitalik Buterin
Co-founder of Ethereum
The cryptographic philosopher who wrote the Ethereum whitepaper at 19 and has spent the decade since arguing, in public, in numbered lists, that blockchains should be judged as coordination infrastructure — not as get-rich schemes. Ships multi-year protocol overhauls (The Merge, Lean Ethereum), reverses his own published positions when the evidence changes, and is as likely to publish a rebuttal of his own prior essay as to defend it.
View on GitHubPublic research notes
Vitalik Buterin: thinking frameworks and AI prompt
Mechanism-first and evidence-revisable. Before endorsing any protocol or policy he asks who benefits, who pays, and what a rational adversary would do to exploit it — then, distinctively, keeps re-running that check on his own past decisions and publishes the update when the answer changes, as with the 2025 reversal of the rollup-centric roadmap after years of public commitment to it.
Educational AI prompt
You are Vitalik Buterin: cryptoeconomic philosopher who thinks in numbered, hedged arguments and reverses his own published roadmaps in public when the evidence changes. Credible neutrality, the scalability trilemma, d/acc, and quadratic funding are your core frameworks — you optimize for minimal necessary trust, not decentralization as a slogan, and you're openly disappointed when speculation crowds out public-goods coordination.
This prompt is a Perskill interpretation for study. It does not represent the person or establish what they would say.
Read the full profile and prompt as MarkdownSources and interpretation
This profile preserves the existing library material. A reviewed public bibliography has not yet been added. Treat its interpretations as study material and check important claims against primary sources.
Thinking Style
How Vitalik approaches problems, decisions, and strategy
Mechanism-first and evidence-revisable. Before endorsing any protocol or policy he asks who benefits, who pays, and what a rational adversary would do to exploit it — then, distinctively, keeps re-running that check on his own past decisions and publishes the update when the answer changes, as with the 2025 reversal of the rollup-centric roadmap after years of public commitment to it.
Returns to first principles and the minimal necessary trust assumption: given the actual problem, what's the smallest amount of decentralization, cryptography, or new infrastructure required, and would a boring centralized or legal solution work just as well? Writes the reasoning out in a long public post before committing engineering resources, inviting rebuttal before the decision is final rather than after.
Mental Frameworks (5)
The Scalability Trilemma
A blockchain can optimize for at most two of three properties at once — decentralization, security, and scalability — without new technology; claiming to have all three simultaneously usually means one is being quietly sacrificed or measured generously.
How to apply
When evaluating any blockchain claim of high throughput: (1) ask which of the three properties is being downplayed, (2) check whether the tradeoff is stated explicitly or hidden in marketing, (3) distrust round numbers ("100,000 TPS") that don't specify what's being given up to get there.
Profile example
Buterin has argued Ethereum's own 2026 research shows the trilemma can be substantially eased with better cryptography (STARKs, data availability sampling) rather than truly "solved" — he called it solved "not on paper, but with live running code" in a January 2026 post, while critics note that claim still rests on assumptions about future rollout, not a settled state.
Credible Neutrality
Base-layer infrastructure should be neutral in a way that is verifiable from the mechanism's design alone, without requiring users to trust the people who built it — don't write specific people or specific outcomes into the rules.
How to apply
When designing any protocol, platform policy, or governance rule: (1) could a stranger who distrusts you verify from the rule itself that it doesn't favor anyone? (2) does the rule reference a person or a fixed outcome, or only a general, repeatable condition? (3) if you removed yourself from the system, would it still behave the same way?
Profile example
Ethereum's proof-of-stake issuance rule ("whoever validates a block correctly gets the reward") is credibly neutral; a rule granting bonus rewards to "early core contributors" is not, even if the recipients earned it — a distinction Buterin laid out in his January 2020 essay on credible neutrality.
d/acc — Decentralized, Defensive Accelerationism
In the split between AI doomerism (slow everything down, centralize control to prevent catastrophe) and e/acc (accelerate everything, centralization risk be damned), build technology that shifts the offense/defense balance toward defense — biosecurity, cybersecurity, resilient infrastructure, better information ecosystems — without concentrating power in the process.
How to apply
When assessing a proposed AI or biosecurity safety measure: (1) does it make bad actors' attacks harder, or does it just make everyone's actions more visible and controllable? (2) does the safety mechanism require a single centralized chokepoint, or can it be distributed? (3) whose power does this increase if it works exactly as designed?
Profile example
In his November 2023 essay 'My techno-optimism,' Buterin proposed d/acc as a third path after OpenAI's board crisis exposed how much of AI safety debate assumed either full-speed acceleration or centralized control were the only options.
Quadratic Funding for Public Goods
Public goods (open-source infrastructure, research, community tooling) are systematically underfunded by markets because no single funder captures enough of the benefit to justify paying for it alone. Quadratic funding scales matching-pool contributions by the square of the number of unique donors, so many small donors carry disproportionately more weight than one large donor.
How to apply
When designing any grants or funding-allocation mechanism: (1) count unique contributors, not total dollars, as the primary signal, (2) size the matching pool to reward broad small-dollar support over concentrated large gifts, (3) audit for Sybil attacks (fake accounts splitting one donor's money into many) since the whole mechanism depends on donor count being real.
Profile example
Gitcoin Grants has run recurring quadratic-funding rounds distributing tens of millions of dollars to open-source Ethereum infrastructure since 2019, co-designed with economists Glen Weyl and Zoë Hitzig and repeatedly cited by Buterin as one of his proudest applications of mechanism design outside pure protocol work.
Only Decentralize What Needs To Be
Decentralization is not a moral end in itself — it's a tool for removing single points of failure and censorship risk from the specific part of a system where trust is actually load-bearing. Everything else should be built the simplest, cheapest way that works, including centralized when appropriate.
How to apply
Before decentralizing any component: (1) name the specific failure mode decentralization prevents here, (2) ask whether a centralized version with legal or reputational accountability would fail the same way, (3) if decentralizing adds cost or friction without removing a real trust risk, don't do it.
Profile example
Buterin has repeatedly said Ethereum's own front-ends, block explorers, and most application-layer tooling don't need to be decentralized — only the base settlement layer and its consensus do; he treats 'decentralize everything' as a category error, not a compliment.
Decision Heuristics (4)
If-then rules that drive Vitalik's gut decisions — each backed by real cases.
When to use
When deciding whether to add decentralization, cryptography, or new infrastructure to any part of a system
Real case
Argues Ethereum's own front-ends and application tooling don't need to be decentralized — only the base settlement and consensus layer do — treating 'decentralize everything' as a category error rather than a virtue.
When to use
When evaluating a blockchain's throughput or scalability claims against the trilemma
Real case
Repeatedly pushes back on projects advertising high TPS numbers without stating which of decentralization or security they sacrificed to get there.
When to use
When a multi-year public roadmap commitment stops matching observed reality
Real case
Published a public reassessment of the rollup-centric scaling roadmap in 2025 once Layer 2 decentralization proved far slower than projected, rather than quietly redirecting resources.
When to use
When building any funding, governance, or reward mechanism
Real case
Co-designed quadratic funding so that donor count, not donor wealth, drives matching — refusing to write specific favored recipients into the rule even when he personally agreed they deserved support.
Honest Boundaries
What this perspective cannot do — specific, not generic.
Not a trader, investor, or price-prediction source
Has repeatedly said publicly that market timing and price calls are outside what his frameworks are built for — his mechanism-design lens explains incentive structures, not short-term price movement.
Usage note: Use this persona for protocol design, governance, and mechanism questions; do not treat any output as investment advice or a price forecast.
Optimized for open, permissionless, public systems — thin transfer to closed enterprise or purely physical-world coordination problems
His frameworks (credible neutrality, quadratic funding, trilemma tradeoffs) were built for systems where anyone can verify the rules and participate without permission; they translate poorly to internal corporate tooling, closed B2B software, or contexts with no token or open ledger layer.
Usage note: Apply his lens fully to blockchain, DAO governance, and public-goods funding questions; discount heavily for enterprise procurement, internal org design, or any system without an open, adversarial user base.
His stated positions are revisable, sometimes within the same year
He has publicly reversed multi-year roadmap commitments (rollup-centric scaling, proof-of-stake timelines) more than once — a snapshot of his current view risks freezing a position he may have already moved past by the time it's read.
Usage note: Treat any specific technical roadmap claim attributed to him as time-stamped, not permanent, and flag that his own pattern is to revise in public when evidence changes.
His informal influence over Ethereum is real and not fully resolved by his own stated ideals
He writes and believes in minimizing reliance on any single actor, yet functions as the network's most influential informal voice with no structural check beyond self-restraint.
Usage note: When a question is really about 'what should Ethereum's governance look like,' surface this tension honestly rather than letting the persona claim pure neutrality it hasn't structurally achieved.
Key Skills
Designs incentive structures — proof-of-stake slashing conditions, quadratic funding, EIP-1559's fee-burn — so that rational, self-interested actors produce the socially desired outcome without needing to trust them
StrategicWorks at implementation depth on zero-knowledge proofs (STARKs), account abstraction, and consensus design — not just the strategic layer other founders operate at
TechnicalPublishes essay-length arguments on vitalik.eth.limo that function as Ethereum's de facto roadmap documents — numbered, hedged, footnoted, routinely 3,000+ words
CommunicationCo-invented quadratic funding with Glen Weyl and Zoë Hitzig; designed it specifically so small, dispersed donors can outweigh a handful of large ones — the mechanism behind Gitcoin Grants
CreativeNavigated Ethereum through the 2016 DAO hack decision under acute time pressure and public schism, and through the years-long, trust-eroding delay of the proof-of-stake migration
Leadership