Ethereum Foundation CROPS Mandate: What It Commits To

The Ethereum Foundation published a formal mandate on March 13, 2026. It tells the foundation to protect four properties together: censorship resistance, open source and free as in freedom, privacy, and security. The document shortens them to CROPS.

This is a governance commitment by the foundation. It is not an Ethereum protocol upgrade, a privacy release, or a rule imposed on wallet developers, validators, or users. The distinction matters because ordinary activity on Ethereum remains public.

What the mandate says

The mandate gives the foundation two aims. First, Ethereum should remain a decentralized and resilient tool for user self-sovereignty. Second, direct self-sovereign use should be available at the scale and in the form users choose, without violating anyone else's self-sovereignty.

CROPS sits inside the first aim. The document expands the acronym as censorship resistance, open source and free as in freedom, privacy, and security. It tells the foundation to embody those properties and use them as a guide for its decisions.

The mandate also limits its own reach. The foundation describes itself as an original steward, not Ethereum's parent, owner, ruler, or final authority. Its launch post says the canonical mandate is for the foundation's use and imposes no obligation on anyone else. That makes CROPS a stated test for the foundation's work, not a binding constitution for the network.

The onchain record is verifiable

The foundation published the mandate in the input data of an Ethereum transaction. The transaction can be inspected through a block explorer, including the full text stored in its input data. The record provides a public timestamp and lets readers compare the onchain text with the foundation's PDF.

This does not make every copy of the mandate authoritative. It gives the public an independent record of what the foundation published at that address and time. The foundation can issue later statements, but it cannot silently replace the historical transaction.

CROPS does not make Ethereum private

Ethereum's own privacy documentation says the network is transparent by design. Every onchain action is visible, while addresses provide pseudonymity rather than anonymity. Transaction patterns can expose sensitive information or help identify a user.

The same documentation separates privacy into writes, reads, and proofs. Private-write tools include mixers, shielded pools, and stealth addresses. Private reads try to stop wallet providers, node providers, or block explorers from learning which accounts a user checks. Privacy-preserving proofs can confirm a fact without disclosing all of the underlying data.

These techniques carry different costs and trust assumptions. Some remain experimental. Some depend on offchain components. Some attract legal or regulatory scrutiny. A zero- knowledge rollup is not private merely because it uses a validity proof. Ethereum's privacy page states that ZK rollups are not private by default.

What readers can test later

A mandate matters only when it shapes decisions. The public can compare future foundation grants, research programs, technical work, and policy statements with the CROPS test. The document itself says the foundation must derive its technical work, community support, and decision-making from its stated principles.

Claims beyond that need evidence. The mandate does not promise funding to a named privacy project. It does not approve a particular Ethereum Improvement Proposal. It does not give developers a legal defense. It does not establish that the base layer has achieved private transactions. Those outcomes should be judged from later grants, releases, protocol changes, and court records, not inferred from the acronym.

What the commitment changes now

CROPS gives the Ethereum Foundation a published standard that can be quoted and audited. Privacy is no longer only an informal aspiration in this document. It appears beside censorship resistance, open source software, and security as a property the foundation says it must not trade away.

The immediate change is institutional, not technical. Ethereum users still need to judge each wallet, application, node provider, and privacy tool on its actual design. For a broader look at privacy techniques, read the zero-knowledge proofs guide.

Sources

• Ethereum Foundation, mandate launch post: The Promise of Ethereum: Introducing the EF Mandate
• Ethereum Foundation, primary document: Ethereum Foundation Mandate PDF
• Ethereum mainnet record: mandate publication transaction
• Ethereum.org documentation: Privacy on Ethereum
• Ethereum.org developer documentation: Blockchain data storage strategies