From Ethereum to AI's "CROPS": What Exactly Are These "Slow Variables" Vitalik Keeps Emphasizing?

Recently, Vitalik has repeatedly mentioned a somewhat unfamiliar term: CROPS.

The systematic emergence of this concept can be traced back to March 13. The Ethereum Foundation Board published the "EF Mandate" document, explicitly stating that its primary focus will be on Ethereum's censorship resistance, open source, privacy, and security – namely CROPS – serving user self-sovereignty while maintaining extractability resistance and a more seamless user experience.

This statement is actually very important, especially as AI begins to enter wallet and automated execution scenarios, CROPS is no longer limited to Ethereum's values but could potentially become the issue of whether users can continue to control their digital lives in the age of AI.

1. What Exactly is CROPS?

To understand CROPS, one must first move past a common misconception. While Ethereum certainly needs to improve performance and reduce costs, its goal isn't just to compete with other public chains on speed or transaction fees.

From a short-term user experience perspective, speed and cost are the most tangible metrics. However, over a longer timeframe, Ethereum's stance has become increasingly clear over the past two years: it aims to provide a set of more foundational capabilities: users can hold assets, express identity, sign transactions, and participate in coordination without relying on a single platform, surrendering ultimate control, or being arbitrarily blocked by a centralized service.

This is the meaning of CROPS.

In the context of the EF Mandate, CROPS primarily points to five directions, forming the acronym from their keywords: Censorship Resistance, Capture Resistance (which Vitalik later added), Open Source, Privacy, Security:

• C - Censorship Resistance: Ensuring the immutability of transactions and smart contracts, preventing termination due to external political pressure or from centralized entities.
• R - Capture Resistance: Preventing Ethereum's governance, development roadmap, and key access points from being long-term controlled by a minority of vested interests.
• O - Open Source / Openness: Maintaining fully open-source code and ensuring absolute permissionless access to the ecosystem.
• P - Privacy: Utilizing cryptographic techniques to grant users the right to be free from surveillance on top of a transparent ledger.
• S - Security: Upholding the foundational bottom line, providing unbreachable ultimate settlement security.

Viewed together, these form a clear set of guiding principles and selection criteria, consistent with Ethereum's long-standing value system.

For instance, at the protocol layer, this means Ethereum needs to continually improve censorship resistance, client diversity, validator decentralization, and formal verification. At the application layer, wallets, RPCs, browsers, signing interfaces, and account systems need to reduce reliance on centralized gateways. At the user experience layer, security shouldn't rely solely on users understanding complex transactions themselves, but should employ clearer signing displays, more verifiable interactions, and better risk warnings, front-loading risk awareness before actions are taken.

This is why the EF has recently progressed several more specific initiatives around security, privacy, protocol resilience, and ecosystem public goods. An example is the Ethereum Audit Subsidy program, which aims to lower the barrier for developers in the Ethereum ecosystem to access high-quality security audits. Looking further, this is not just about subsidizing costs; it's about pushing "security" from a high-cost service affordable only to large projects, further out to more small and medium-sized developers.

In late May, Vitalik also discussed his views on the EF's future direction, emphasizing that the EF should become a smaller, more principled organization focused on long-term sustainability, rather than trying to cover every need in the ecosystem. The reason is pragmatic: the EF doesn't possess unlimited resources nor has a continuous income stream from staking or transaction fees. Therefore, it should concentrate its limited resources on tasks crucial for Ethereum to realize its CROPS values, tasks that other entities cannot reliably undertake.

In other words, at this current transformative historical stage for Ethereum, CROPS is not an abstract slogan prioritizing ideals over reality, but rather an external definition and constraint on what the EF should and should not do.

2. When CROPS Meets AI: The Intersection of Two Parallel Universes

Vitalik Buterin's most recent push to bring CROPS into a broader discussion occurred within the context of AI.

On May 28, Vitalik Buterin posted an update on his progress with localized AI, stating that DeepSeek V4 has a 2-bit quantized version that can run in approximately 90 GB of VRAM, achieving speeds of about 35 tok/s on Apple hardware and 7 tok/s on AMD hardware. He stated that true "CROPS AI" should support multiple hardware platforms, and not just be "decentralized AI."

He also pointed out significant overlap between the CROPS Ethereum access layer and CROPS AI, such as using zero-knowledge proofs for paid remote LLM calls and private Ethereum RPC reads. He suggested more AI models specifically fine-tuned for Ethereum scenarios should emerge to improve smart contracts, protocol code, and ecosystem security.

This effectively places Ethereum and AI within the same problem framework.

Previously, when discussing AI, the focus was often on model capabilities, such as writing code or handling complex tasks. However, from a user security perspective, the real change AI brings isn't just "more powerful capabilities," but its transformation of the gateway for digital operations.

To revisit a common point: applications used to be relatively clear interfaces. You'd open a wallet to transfer, open a DApp to trade, open a browser to search, open a social platform to post. Each app had defined boundaries. But with the advent of AI Agents, these boundaries blur. Users no longer click functions one by one; they express intent using natural language:

"Help me find the optimal cross-chain path," "Execute a swap for me," "Help me organize my assets," "Execute a specific DeFi strategy for me," "Generate and send a transaction..."

This sounds convenient, but it raises a critical question: when the AI acts as your digital agent, what transactions is it signing on your behalf? What privacy is it exposing?

If the AI operates entirely in a centralized cloud, user asset information, transaction intents, address relationships, identity preferences, and usage habits could be concentrated in the hands of a few service providers. Relying on opaque APIs, centralized RPCs, black-box plugins, and unverifiable inference processes, especially during on-chain operations, might make things more convenient for users, but it also makes it harder for them to know exactly what they are giving up.

This is the question CROPS AI aims to answer.

An AI truly aligned with CROPS is not just capable, but also censorship-resistant, open, privacy-preserving, and secure. Ideally, it should run locally, or at least minimize reliance on centralized cloud services for sensitive tasks, minimize information leakage, and allow users to understand, confirm, and retain ultimate control.

In other words, AI cannot just be a smarter black box, especially in Web3 contexts. In the future, AI might not just help summarize articles, write code, or handle customer service, but directly participate in asset management and automated execution.

The closer it gets to user assets, the more critical CROPS becomes.

This is precisely why the CROPS Ethereum access layer and CROPS AI intersect.

3. What Web3 Growth Opportunities Exist at This Intersection?

From this perspective, Vitalik's recent mention of the overlap between the CROPS Ethereum Access Layer and CROPS AI is quite natural.

Whether for Ethereum or AI, the core problem users face is becoming the same: when using AI assistance, how can I avoid handing over my privacy, identity, assets, and autonomy completely to centralized intermediaries?

• On the Ethereum side, this manifests as how users access on-chain data, connect to RPCs, sign transactions, confirm the safety of DApp interactions, and avoid all wallet queries, balance reads, and transaction broadcasts passing through a few centralized services.
• On the AI side, this manifests as how users call models, ensure prompts and personal data aren't misused, let local models handle sensitive tasks, and minimize exposing their identity and intents when needing remote large model capabilities.

While these two sets of problems seem different, they share a fundamental core.

For example, when an Ethereum user checks balances, reads transaction history, or simulates transaction outcomes, they typically need to go through RPC services. RPC might just look like a technical interface, but it can know your IP address, on-chain addresses, query habits, asset structure, and interaction patterns. If this data is centrally collected, a user's on-chain privacy can be pieced together gradually.

Similarly, when an AI user calls a remote model, they might expose their preferences, financial information, or even identity clues. If users start using AI to handle wallet operations in the future, the risks amplify further.

Therefore, Vitalik's mention of ZK-paid remote LLM calls and private Ethereum RPC reads essentially attempts to solve the same problem: how can you access remote capabilities and obtain services without fully exposing all your information?

This is the intersection of CROPS Ethereum and CROPS AI. On one side is a more private, more verifiable on-chain access layer requiring fewer trust assumptions. On the other is a more open, more localized, and safer AI execution environment. Combined, they could form a new gateway for users entering the digital world in the future.

Extending along CROPS's underlying logic, the entire Web3 ecosystem (especially the wallet layer as a traffic gateway) will undoubtedly take on more roles:

When users start expressing on-chain needs using natural language, the wallet is no longer just a signing tool, but the user's console for digital actions. It needs to help users judge if a DApp can be connected to, what a specific transaction will actually do, and whether an AI Agent is calling unnecessary data.

From this perspective, CROPS is not an abstract value system. It will directly influence wallet product design directions and drive the evolution of integrating Web3 interaction experiences and the wallet sector over the next decade.

Final Thoughts

In the current market conditions, many people may have lower interest in pure concepts.

However, the colder the market, the easier it is to overlook technological variables that are not immediately attractive in the short term but truly determine the long-term direction.

CROPS is worth paying attention to not because it creates a new hype, but because it reframes the long-term challenges of Ethereum and AI within a single framework: as digital systems become more powerful, can users still retain their control?

After all, security and privacy cannot just be afterthoughts or patches.

From this perspective, in an era where AI is accelerating its takeover of the digital world, making systems more understandable, verifiable, private, and secure might be the true positive variable for why Ethereum remains worth building and using.

In an era where AI is accelerating its takeover of the digital world, being more understandable, more verifiable, more private, and more secure may be the real reason Ethereum continues to be worth building and using.