EthSystems, a team recently spun out of the Ethereum Foundation, says the biggest obstacle to bringing large institutions on-chain is not whether they want Ethereum. It is whether they can use it without exposing their balances, positions, counterparties, and execution logic to the world.
In an interview with Bankless, co-founders Mo Jalil and Oscar Thorne said Ethereum’s transparency, long celebrated as one of its defining strengths, becomes a direct constraint in institutional settings. For large financial firms, they said, the core concerns are business continuity and security, along with strict compliance obligations. Without modern cryptography, institutions cannot capture the liquidity and coordination benefits of a public chain while protecting commercially sensitive information.
A spinout focused on Ethereum, institutions, and privacy
Bankless host David introduced EthSystems as a new team formally separated from the Ethereum Foundation, with a clear focus on three areas: Ethereum, institutions, and privacy. Thorne said Ethereum works well as a neutral decentralized base layer, but privacy is not built into the protocol itself. That gap has led many teams to explore solutions at both the base and application layers. EthSystems wants to work in that missing space.
Thorne said institutions usually care about two things above all else. First, they need continuity and safety for core business functions. Second, they operate under tight compliance requirements. Those constraints pushed many firms toward private networks or consortium chains for years, since those environments could be tightly controlled. At the same time, public Ethereum offers deep global liquidity, new forms of coordination, and a chance to improve existing operating models. To access those advantages, he said, institutions need privacy-preserving computation.
The founders’ backgrounds combine banking systems and advanced cryptography
Jalil said he started in traditional finance and spent about five years building quantitative algorithmic trading systems at firms including Goldman Sachs. That work gave him direct exposure to what major banks actually require in system architecture, matching, clearing, risk management, and compliance. He later spent several more years in the hedge fund sector.
He said he had followed frontier technologies for a long time and remembered being struck when he first read the Bitcoin white paper, though he considered public-chain use in core financial infrastructure premature at the time. Years later, he joined the Ethereum Foundation and worked on a large amount of application-layer business development. Tomas, he said, was serving as co-executive director at the time. During that period, one conclusion became hard to ignore: if large traditional organizations were going to use public Ethereum in a serious way, privacy and modern cryptographic systems would be mandatory. Jalil said he had known Thorne for years and reached out because the challenge matched Thorne’s background.
Thorne said he has spent roughly a decade in crypto and focused on privacy long before it became a mainstream topic in the industry. He worked at Status early on and later created a research lab. During that period, he led development of different peer-to-peer communication protocols with an emphasis on censorship resistance, data availability, and communications privacy.
Over the past five to six years, he said, he moved deeply into zero-knowledge proofs, building developer tooling and infrastructure and working closely with early members of the Ethereum Foundation’s PSC, or Privacy & Scaling Explorations. He said he wrote a short book on proof systems, researched polynomial commitment schemes, and led work on tools to reduce client-side proving complexity. In recent years, he served as a privacy strategy adviser at the Ethereum Foundation, where his work centered on a new access-layer architecture. He and Jalil began the institutional privacy effort while working together there.
Thorne added that his earlier focus had been on individual sovereignty and user privacy, and that principle still matters to him. But in the last few years, he said, it became clear that institutional demand for privacy is real and, in many business cases, even more urgent than consumer demand. He tied that shift directly to the gradual clarification of regulatory frameworks. The team spent the past year building the system publicly inside the foundation before spinning it out as an independent entity about a month ago.
Jalil stressed that EthSystems did not begin from scratch. The spinout, he said, brought with it a full year of research and delivery work, including closed-door workshops, hands-on engagements with many financial entities, published public products, and architecture analysis comparing private execution rails with public ledgers.
What “privacy strategy” meant inside the Ethereum Foundation
When asked to explain privacy strategy, Thorne said the term came out of the research environment around PSC inside the Ethereum Foundation. The idea was to bring advanced cryptographic work into a broader institutional view inside the foundation and think systematically about which privacy directions should receive priority.
As the lead of the institutional privacy working group, he said, the mission was to connect two worlds that had been largely separated for a long time: traditional large institutions on one side, and the Ethereum-native ecosystem on the other. Early conversations with financial firms often showed a major information gap. Many still saw Ethereum as a fully transparent public chain with no room for commercial confidentiality. In practice, he said, the ecosystem already had a wide range of cryptographic primitives, specialist security vendors, and layered privacy protocols.
That meant translating in both directions. EthSystems needed to explain the full privacy technology stack on Ethereum to institutions, while also telling crypto-native teams and protocol engineers what trillion-dollar commercial users were actually looking for. Thorne said the group mapped the privacy market in detail, organized institutional needs by business process, legal and compliance constraint, and transaction context, then matched those needs to technologies such as zero-knowledge proofs, secure multi-party computation, and homomorphic encryption. The team used proof-of-concept work and architecture papers to show which components were missing and how those cryptographic building blocks could fit together.
Jalil added that PSC had long served as a home for privacy and scaling research within the Ethereum Foundation and could be thought of as a specialized cryptography lab focused on turning theory into deployable systems.
The bottleneck has moved from theory to systems engineering
David asked whether the industry already has usable code that institutions simply need to discover and adopt, or whether major infrastructure gaps still remain. Thorne said the answer is both.
Over the past decade, he said, the Ethereum Foundation, the Zcash ecosystem, and many independent cryptography teams have succeeded in turning a large amount of advanced cryptographic research into usable code. A group of service providers has also emerged to lower integration costs, and in standard use cases the technical path is now fairly well understood.
That changes once a project meets the specific constraints of a real institution. Thorne said many business rules in traditional finance are extremely strict and sometimes counterintuitive, which means generic standardized designs often do not fit cleanly. From the outside, it may seem enough to deploy a privacy-focused Layer 2 for institutions. But once teams move into actual trading and post-trade flows, a general-purpose rollup can force trade-offs around latency, liquidity fragmentation, or permissioning that some firms simply will not accept.
He also said digital maturity varies sharply across the institutional landscape. Some top firms have internal labs with dozens of researchers, including cryptography PhDs, and have tracked zero-knowledge proofs for years. Others have no Web3 engineering capability at all and would rather buy a white-label compliance-ready stack. Their requirements around throughput, deterministic settlement times, and security levels differ enough that a single template is not realistic.
Jalil framed it more bluntly. Based on the institutional cases EthSystems has followed, he said the main bottleneck is no longer pure cryptographic theory. It is systems engineering and architecture adaptation. Ethereum has already done much of the research-heavy work. The difficult part now is fitting those components securely into modern financial infrastructure.
A concrete banking example: inter-dealer compression
Jalil said the team sees a wide range of institutional use cases, but it spends most of its time on problems the current market has not solved. Basic private transfers and tokenized deposits, he said, already have some early solutions and have seen limited progress in certain compliance-friendly jurisdictions and organizations. EthSystems is more interested in large, structurally important pain points from traditional finance that have not been seriously addressed on public chains.
One example he described involved deep discussions with a top-tier global investment bank around inter-dealer compression. In traditional derivatives and foreign exchange markets, major banks accumulate large bilateral exposures every day. At the end of each trading day, participating banks send large transaction datasets to a trusted centralized clearing service to reduce capital usage and counterparty risk through netting and compression. Jalil said the banks involved can pay tens of millions of dollars, and in some cases more than $100 million, in annual fees to third-party providers.
That centralized intermediary sees sensitive trade details and live positions from each bank and performs the compression in the background. No major bank wants to reveal the full details of its book to a third party, Jalil said, but the business still tolerates it because compression can materially reduce capital requirements and shrink the number of trades that ultimately need to settle.
The bank executive’s question to EthSystems was whether cryptography could remove that trusted middle layer altogether. Ethereum’s tamper-resistant shared global state, he said, looked like the right foundation. The obvious problem is confidentiality: if those positions and trade details were submitted directly to a transparent public mainnet, competitors could infer each bank’s real exposure. Jalil described it as a real-world use case with potential value in the tens of billions of dollars, but one that crypto-native teams had rarely focused on before.
He said the team has also gone through multiple rounds of architecture analysis with large institutions in several sovereign jurisdictions around private payments and settlement. Even where “private payments” sound standardized, local rules on financial supervision, AML look-through requirements, and foreign exchange controls can turn a simple cryptographic model into a much more constrained design problem.
Thorne said building enterprise-grade confidential systems goes far beyond adding a zero-knowledge proof. Institutions also care about high availability, deterministic security boundaries, censorship resistance, and compatibility with existing settlement infrastructure. In many cases, he said, EthSystems is helping raise the level of rigor in engineering specifications and systems delivery across Web3.
He added that these incumbents already run businesses with proven product-market fit and internal systems moving billions of dollars every day. When they evaluate Ethereum, what they want first is complete determinism at the systems level. That differs sharply from the intuition-led, fast-iteration style that shaped much of early crypto development. Privacy is one of the hardest pieces, he said, but only one piece. Formalized technical specifications and edge-case coverage matter just as much.
A national payments case with four required parties
Without naming the institution because of confidentiality limits, Jalil also described a case involving national-scale financial infrastructure. In that jurisdiction, a large financial institution wanted to roll out a blockchain-based payment network across the country. The organization accepted the efficiency case for a public chain in inter-institution settlement, but the system also had to support high transaction concurrency for a population in the tens of millions and fit the jurisdiction’s specific audit and compliance architecture.
In a standard private-payment model, he said, cryptographic privacy and verification are usually designed around the sender and receiver. But local regulation in this case required each transaction to support four-party interaction at the cryptographic level: the sender, the recipient, a licensed compliance auditor, and the national regulator.
The institution spent the past two to three years trying nearly every major privacy protocol and scaling network it could find, Jalil said, yet none could simultaneously support controlled disclosure among four parties, required throughput, deterministic latency, and manageable on-chain computation costs. He said the institution even produced a technical assessment running to dozens of pages explaining why existing public-chain systems could not meet the target.
The turning point came from work EthSystems had published while still inside the Ethereum Foundation. The team had released research posts and proof-of-concept code on multi-party private state transitions. After seeing that open work, the institution’s technical lead reached out and said the foundation’s breakthrough had reopened the possibility of building a national clearing network on Ethereum. Jalil said deployment is now moving forward based on that open architecture blueprint.
Thorne said institutional projects of this kind involve long commercial and validation cycles, including compliance review, legal assessment, and security audits. He noted that during the team’s time at the foundation, some institutions wanted to buy deeper architecture support through commercial contracts, but the foundation, as a neutral nonprofit, could not accept those arrangements. That left some projects stalled in the final stretch. Spinning out into an independent for-profit entity, he said, was a way to bridge that gap while continuing to contribute through open-source work.
Customization first, standardization after
David raised a common concern: if every jurisdiction and every compliance regime requires heavy customization, how can the business ever scale or generate network effects?
Jalil said the relationship between custom deployment and shared standards is not binary. One reason Ethereum is powerful, he argued, is that it supports multi-layered evolution. He also pushed back on the idea that these are merely niche custom markets. In traditional finance, many of the “specialized” verticals outsiders dismiss are large industries in their own right, sometimes worth hundreds of billions of dollars.
He said EthSystems has no interest in endless bespoke outsourcing. The strategy is to start on the front line, fully understand the hardest verticals, and only then design cryptographic architectures that work in production. Once that happens, the team plans to abstract broadly reusable primitives and protocol standards from those hard cases.
The inter-dealer compression protocol, for example, could be generalized across global investment banks once it works at one top-tier institution. Likewise, a controlled multi-party compliance disclosure protocol built for sovereign-scale payments could become a standard module for compliance-oriented stablecoins in different regions.
Jalil said the long-term path is straightforward. Core algorithms and common interfaces validated in real deployments will be contributed back to the Ethereum community under permissive open-source licenses, which he said should ease institutional concerns about vendor lock-in. At the same time, the team plans to package audited components into high-performance, plug-in modular tools.
Thorne said he agreed. Crypto has often assumed that if the right generalized infrastructure is built, users and applications will arrive on their own. In heavily regulated and operationally complex institutional markets, he said, that assumption regularly breaks down. Solving extreme concrete cases first, then turning what is learned into standards, is a more grounded engineering path.
EthSystems says it is a product company, not a consulting shop
Asked whether EthSystems is closer to a custom-delivery consultancy for traditional financial institutions or a product-driven company more like Uniswap Labs or Aave Companies, Jalil said the answer is clear: it sees itself as a product company.
He said he previously served as a chief technology officer and has spent his career building scalable software products, while Thorne brings long experience in product architecture and protocol development. Standardized products, he said, are the only way to get compounding network effects.
Still, Jalil said there is a practical path to get there. Teams cannot sit in abstraction and invent demand at the edge between Ethereum and traditional finance. They need to go into trading desks and compliance offices, watch how traders interact with post-trade systems, and understand the details of real operational flows. The point of the early custom work is to distill it into standardized infrastructure products later.
Thorne said traditional institutional procurement and decision cycles are naturally slow. Through proof-of-concept work, deep technical collaboration, and joint architecture reviews, EthSystems can see real demand much more clearly and make product bets with stronger defensibility.
Institutional demand is moving from PoCs to live business
On the broader market cycle, Jalil said most of the demand EthSystems sees today is coming from institutions themselves rather than from the team trying to persuade them to look at Ethereum.
He gave two reasons. First, global financial institutions have spent the past several years understanding the value of decentralized shared ledgers in reducing reconciliation costs and enabling real-time atomic settlement. Second, he said, native DeFi deserves credit. When institutions saw protocols such as Aave, Uniswap, and MakerDAO display resilience and capital efficiency through years of severe market volatility, interest increased sharply. The central question became how to enter under existing law, not whether the systems were worth studying.
Jalil said the internal driver changed even more once digital asset compliance frameworks in Europe and the US became clearer. In previous years, many firms kept blockchain efforts inside peripheral innovation labs running low-risk proof-of-concept projects. Over the past year, he said, EthSystems has increasingly seen CEOs and business-line heads at large institutions tell technical teams to stop building “lab toys” and start creating real business loops on public chains.
Thorne said the likely evolution begins with cryptographically protected, compliance-aware institutional sandboxes where firms can run business logic in controlled settings. Over time, as liquidity and infrastructure mature, those systems can connect through cross-chain and zero-knowledge bridging designs into deeper native DeFi venues such as Morpho and Uniswap.
He said some forward-looking asset managers are already thinking carefully about how tokenized funds could be composed with on-chain lending protocols. But before that becomes common, there is still a multi-year translation period in both legal and conceptual terms. Many multinational banks are more than 100 years old, and their risk manuals and compliance systems were built around traditional central-counterparty settlement structures. Mapping those frameworks into Ethereum smart contracts will require technologists, legal advisers, and policymakers to work in parallel.
What 2033 could look like
When asked to imagine the system seven years from now, Jalil said the best technology in its final form should be nearly invisible. Ordinary users should not need to think about blockchains, cryptography, or decentralized ledgers in order to benefit from the security and freedom of movement they provide.
He said decentralized identity, or DID, together with zero-knowledge systems could let an ordinary investor keep control over sovereign personal data while still investing compliantly in global assets and receiving real-time settlement, without handing sensitive information to centralized intermediaries. His view is not only that trillions of dollars in traditional assets could be minted onto Ethereum, but that global assets could preserve DeFi’s permissionless composability without forcing individuals or businesses to leave their data fully exposed. Within the next seven years, he said, the migration of core financial infrastructure onto decentralized public chains such as Ethereum will become a reality.
David then raised a classic objection from the crypto community. If asset flows, pool sizes, and institutional positions are hidden by zero-knowledge systems, how can the public know that the system has not secretly overissued liabilities or created bad debt? How do privacy and public trust coexist?
Jalil said many observers define privacy too narrowly as total opacity. In modern cryptography, he argued, privacy means tightly controlled disclosure: clearly specifying who can access which dimensions of information, at what time, and with what mathematical proof. In ordinary banking, he noted, a daily transfer is not globally visible. Typically only the sender, recipient, and bank know the transaction details. The public demand for transparency is really a demand for certainty that the system is not cheating. If cryptography can provide mathematically sound solvency assurances without exposing counterparties and trade secrets, he said, that becomes a higher-order trust model: selectively verifiable disclosure.
David said the kind of on-chain auditability he wants to preserve is at the aggregate level: total transaction volume, aggregate pool size, total value locked, and liquidation thresholds. If an institution deposits a large confidential position into a lending protocol such as Morpho, the system should still be able to show the verified total asset amount to the whole network in real time. If a large trade takes place on a decentralized exchange, the public should be able to verify that the trade happened and settled, without seeing the institution’s detailed position or strategy.
Thorne said there is no irreconcilable conflict between those goals at the cryptographic level. With modern zero-knowledge proofs and homomorphic commitment schemes, it is possible to build layered systems in which macro indicators relevant to public safety and system soundness remain globally visible, while account identities, transaction details, and trading strategies remain protected. Ethereum’s programmable nature, he said, makes it a strong environment for exactly that kind of design.
A call to DeFi teams and the broader ecosystem
Jalil closed with a direct message to DeFi builders. Teams working on new lending, trading, or asset-management infrastructure, he said, should reach out if they want to explore how battle-tested DeFi systems can be adapted for institutional compliance and privacy use cases.
He also said EthSystems plans to open-source fresh technical specifications and codebases every three to four weeks. According to him, many international financial executives and architects are watching those releases closely. If the native crypto community builds new privacy or scalability tools, he said, they are welcome to contribute to the team’s repositories.
Thorne said Ethereum participants should take a broader view of the user base they are serving. That means not only improving the experience for native retail users, but also thinking seriously about what kinds of interfaces compliance-constrained large entities actually need. Closing the knowledge gap between Ethereum-native builders and traditional institutions, he said, will take sustained ecosystem coordination.
Jalil summed up EthSystems’ mission in one line: to act as a translator and bridge between boardrooms and cypherpunks. Those groups often misunderstand each other or even treat each other as opponents, he said, but unless decentralized technologies that protect individual rights and commercial freedom are written into the system specifications used at the highest levels of decision-making, the future of global financial infrastructure will not really change.
Thorne made a similar point at the end of the discussion. For both individuals and institutions, he said, the fundamental properties people care about are the same: security, censorship resistance, transparent rules, and privacy sovereignty. In his view, Ethereum’s appeal lies in its ability to support both fully decentralized, identity-free crypto experiments and next-generation financial systems for trillion-dollar entities operating under strict legal and business constraints.