The EF Mandate

In March 2026, the Ethereum Foundation published its Mandate (part constitution, part manifesto). It was written for “a thousand-year horizon.” It lives onchain, and it’s free for anyone to read forever.

The document is addressed primarily to members of the Foundation. But it contains a sentence which is relevant to the rest of the ecosystem:

“We require of them no aesthetic conformity, only principled alignment: when people share the instinct to keep systems forkable, censorship resistant, private, and secure, we treat them as fellow travelers of the path and fellow stewards of the infinite garden.”

Isla Labs is not the Ethereum Foundation, and the Mandate imposes no obligation on the organization to align with its principles. However, since the org was born from ground-floor Web3 communities, we consider ourselves to be Ethereum-aligned by default: open source, trust-minimized, decentralized, and independent.

Since there is some native alignment, we hold our products to the standards outlined in the EF Mandate: not out of deference, but because it happens to be the most precise public articulation of the culture we had already chosen.

What the Mandate says

Ethereum exists for self-sovereignty. The Mandate’s first principle is that a user has the final say over their identities, assets, actions, and agents. Ethereum honors two promises: self-sovereign computation, and sovereignty-preserving coordination at scale. The network and its emergent culture was designed to allow people to organize without surrendering to centralized, unaccountable power.

CROPS is non-negotiable. Censorship Resistance, Capture Resistance, Open Source, Privacy, and Security must remain “as an indivisible whole, the sine qua non of all Ethereum’s development priorities.” We went through the properties in detail in our Lean Ethereum post; the Mandate’s contribution is the insistence that they cannot be traded off against each other, or against convenience.

The walkaway test. The Mandate’s measure of security goes beyond audits: things must do what they claim, and users must never be trapped. Systems should remain functional and exitable without depending on any single entity, including the Foundation itself. In other words, onchain automation and contract immutability supersede onchain governance or legacy organizational structures by default, and protocols should be designed with this in mind.

Extraction is failure, whatever the user count. Perhaps the sharpest line in the document: “A billion users in a centralized silo is not a success; designing around the enshrinement of centralized extraction pipelines in the protocol is not a success; it is a failure of mission.” Growth rate is not a worthy aim next to true decentralization. The core ethos of Web3 is about protecting users against concentration of control, or the encroachment of large-scale organizations on the rights of the everyman — especially in the context of Decentralized Finance.

Subtraction as strategy. The Foundation describes its own operating model as “a process of subtraction for resilience”: Ethereum succeeds when it no longer needs its original steward. The EF explicitly refuses to be a kingmaker, refuses value extraction dressed up as alignment, and treats its own diminishing responsibilities as the definitive signal of success. Its recent restructuring for Lean Ethereum is this philosophy implemented.

CROPS-native over incrementalist. When there is a choice, the Mandate prefers “the option that is fully-CROPS from the beginning even if it is technically or socially more difficult to get off the ground and scale.”

How Isla Labs measures up

HighPotential is CROPS-native by default. Open source design principles, self-custodied experiences, and decentralized exchange operations were never brought into question during the design of the protocol itself. It was going to be like that from day one.

As a result, Isla Labs is verifiably aligned to many of the principles outlines in the EF Mandate, with some notable caveats that are important to cover.

Self-sovereignty with a seamless experience. The Mandate demands that Ethereum’s “self-sovereign use must be extraction-resistant” — something which is notable in the context of our product suite. HighPotential was designed and built by a single founder, and HP is designed as a revenue-generating, onchain business.

This process of generating onchain revenue in DeFi can be seen as value extraction, or it can be seen as enabling scaling for Ethereum by expanding its total reach. On the first point, it is not that selfish, and on the second, it is not that selfless. Launching a business contains within it a native economic feedback loop, where success with the product increases profits.

The fee systems integrated by Isla Labs typically contain distributed incentive mechanics by default: simple economic loops that can reinforce perpetual, value-adjusted returns for users of the products in various contexts. These processes have self-sovereign guarantees: Isla Labs cannot retroactively alter these core systems. Everything related to money flows is enshrined onchain, and storage of the assets is fully self-custodied.

The walkaway test, applied honestly. HighPotential’s assets are ordinary ERC20 tokens, and the liquidity pools that the platform uses, both during its bonding curve stage and post-migration, are Uniswap V4, which is a permissionless, open source protocol. If Isla Labs vanished tomorrow, the markets would remain tradable, the tokens would remain yours, and every settlement that the protocol ever facilitated would remain verifiable against onchain records forever.

The yield pipeline leveraged in HighPotential utilizes a licensed offchain data feed that is secured by Chainlink Runtime Environment: up to 10 nodes in the Decentralized Oracle Network (DON) validate data integrity, while a zero-knowledge virtual machine (zkVM) attests to the honesty of the algorithm that runs on top of the raw data. Stage 2 of decentralizing HighPotential involves packaging the witness process, where HP token incentives and a downloadable zkVM enable the platform to pass the walkaway test.

CROPS-native from day one, even though it was harder. The easy version of our platform runs the yield distribution on a private backend and asks users to trust it. We spent the design effort to make settlement provable instead: raw data digests locked onchain with an independent oracle cross-checking authenticity, and a zkVM proving that the published algorithm — and only that algorithm — produced every result. Market deployments and discontinuations pass through similar machinery.

This was the technically harder path, but CROPS-adherence compounds, and precedents are durable. There is no walled garden. Users of the protocol have assurances that centralized involvement is restricted to low-impact maintenance. Everything users need to verify HP, including the algorithms, deployment criteria, identity mappings, proofs, and digests, are published onchain.

The one thing we cannot publish, licensed raw match data, is handled the way the Mandate’s open-source principle demands of unavoidable constraints: verifiable by cryptographic digest, selectively disclosable under dispute, and never a black box that anyone is asked to simply believe. This is covered in depth in Trustless PPM.

Fellow travelers

The Foundation could have spent its time heading the development of Ethereum core simply accumulating control, but it chose subtraction. The equivalent choice for an application-layer team is to build products whose correctness does not depend on the builder’s continued good behavior. To make Isla Labs, in the ways that matter most, irrelevant to the health of the protocol.

That is the primary thing to aim for as a protocol team building on decentralized financial rails. It is possible to create consumer- and enterprise-grade financial technologies in the ecosystem today, but that should not be treated as a goal in itself unless it is combined with a continuation of Web3’s day one principles, which include decentralization away from the control of any single counterparty or middleman.

HP has been designed from the ground up to ensure confluence in this context, so that it can grow beyond its humble beginnings in a maximally sustainable way.