Title: EthSystems · Confidential Systems for Institutional Ethereum

URL Source: https://original.es-internal.pages.dev/

Markdown Content:
---
description: A working knowledge base of confidential systems for institutional Ethereum.
title: EthSystems · Confidential Systems for Institutional Ethereum
image: https://original.es-internal.pages.dev/og.png
---

[Skip to content](#main-content) 

# Confidential Systems for Institutional Ethereum

**EthSystems** helps institutions move on-chain with privacy that's performant, secure, usable, and accessible, disclosing only what the rules require.

[See approaches→](/approaches/) [See writeups→](/blog/) 

0xa50402.190x1c72 <b;#4\~d1&6<:f3+8\~ 0x83e92,151.560xfa50b 0%5/a:2\*7>c0%54=9^e2\* 0x61c7217,382.930xd83 6<b;#4=8\~d1&6<b;a:f3+ 0x4fa4,247.300xb61c c0%5/e2\*7>c0%#4=9^e 0x2d83906.670x94fa5 &6<b;#+8\~d1&/a:f3+8 0x0b61c5,939.040x72d \>c0%5/a^e2\*7>c0;#4=9 0xe9431,666.410x50b6 1&6<b3+8\~d1&6<5/a:f3 0xc72d7,179.780x3e94f 7>c0%59^e2\*7>cb;#4=9^ 0xa50b6830.150x1c7 d1&6<b;f3+8\~d%5/a: 0x83e1,727.520xfa50 \*7>c0\=9^e2\*7><b;#4= 0x61c745,950.890xd83e9 \~d1&6<:f3+8\~d1&0%5/a:f 0x4fa503,111.260xb61 2\*7>c0%4=9^e2\*76<b;# 0x2d8754.630x94fa 8\~d1&a:f3+8c0%5/a 

The team institutions already know

Institutions want to move real financial activity onto Ethereum. A public ledger exposes positions, counterparties, and flows they are not allowed to reveal. 

**EthSystems**, the team behind the Ethereum Foundation’s Institutional Privacy Task Force, builds the confidential, compliant systems that make that possible, from proof-of-concept through to production, backed by a year of open-source work already shipped. 

[What we offer →](/offerings/) 

## Find the right privacy solution

We document patterns, use cases, and regulatory frameworks for implementing privacy-preserving financial applications on Ethereum.

[ Approaches Read worked architectures directly. Each names trade-offs in plain language, evaluates under CROPS, and references a working prototype where one exists. **10** approaches → ](/approaches/) [ Problem areas Begin from the institutional question that mirrors your situation. Each use case pairs with one or more approaches that demonstrate how others have built solutions. **23** use cases → ](/use-cases/) [ Reusable solutions Build your own approach using the cryptographic primitives applied in our case studies. Each building block includes its risk profile, architectural layer, and trade-offs. **69** building blocks → ](/patterns/) 

## Who is this for

EthSystems coordinates between vendors and protocols, institutions, and regulators. The map and the approaches are written so each group can reach the same evidence by a different door. Pick the column that fits your role; each one is a recommended reading order, not a forced path.

For business stakeholders 

Decide what to integrate.

1. [ 01 Use cases Start with business requirements and challenges. → ](/use-cases/)
2. [ 02 Jurisdictions Regulatory considerations in the regions you operate in. → ](/jurisdictions/)
3. [ 03 Approaches Recommended architectures with named trade-offs. → ](/approaches/)

For technical teams 

Decide how to build.

1. [ 01 Building blocks Reusable technical building blocks with standardized evaluations. → ](/patterns/)
2. [ 02 Approaches Detailed implementation guidance from worked approaches. → ](/approaches/)
3. [ 03 Vendors Tooling and infrastructure options mapped to patterns. → ](/vendors/)
4. [ 04 Domains Domain-specific considerations across payments, custody, identity, and more. → ](/domains/)

For legal and compliance 

Map regulatory requirements.

1. [ 01 Jurisdictions Regulatory frameworks applied as overlay on the architectures. → ](/jurisdictions/)
2. [ 02 Use cases Compliance constraints surfaced in context, written from interview. → ](/use-cases/)
3. [ 03 Approaches Architectures evaluated for regulated deployment. → ](/approaches/)
4. [ 04 Disclosure mechanisms Selective disclosure with keys and proofs for audit and reporting. → ](/patterns/pattern-regulatory-disclosure-keys-proofs/)

## Recent writeups from the team

Long-form research, guides, POCs, and analysis from the EthSystems team.

[  2026-07-14 Introducing EthSystems EthSystems builds confidential systems for institutional Ethereum, carrying forward the IPTF work as an independent company focused on privacy, protocol design, and commercial execution. ](/blog/introducing-ethsystems/)[  2026-06-11 Exploring Hardened Shielded Pools Extending a working shielded pool with epoch nullifiers and PIR, and why private selection is the harder problem left for private payments at scale. ](/blog/exploring-hardened-shielded-pools/)[  2026-05-29 Resilient Civic Participation Petitions on Ethereum where the signer list never exists and the outcome stays verifiable from chain state alone. ](/blog/resilient-civic-participation/) 

[See all writeups→](/blog/) 

## How we assess solutions

Every pattern on this site is rated against four properties (the CROPS framework) and tagged for the institutional context it fits.

CR 

### Censorship-resistance

Whether a counterparty, sequencer, or relayer can block your transaction.

OS 

### Open source

Whether the implementation is free to audit, fork, and self-host.

P 

### Privacy

How much of the transaction (amounts, parties, patterns) stays hidden.

S 

### Security

The trust assumptions and threat model the architecture relies on.

Institution to institution

Both counterparties are regulated institutions. Symmetric power dynamic; both parties have legal teams, vendor choice, and contractual recourse.

Institution to user

One counterparty is a regulated institution, the other an individual. Asymmetric power dynamic; privacy must protect the user from the institution.

[Browse the patterns→](/patterns/) 

## Supported by

The coalition standing behind EthSystems.

Ethereum Treasury · BMNR

Ethereum Treasury · SBET

Joe Lubin

Co-Founder, Ethereum

Asia Ethereum Backer

## What institutions ask us most

The questions we hear most, answered directly. Each one links into the full FAQ where answers cite the relevant pattern, jurisdiction, and approach.

What is EthSystems? 

An engineering and research company building confidential systems for institutional Ethereum: the privacy and compliance infrastructure institutions need to put real financial activity on the network.

[  About us ](/about/) 

Who is behind it? 

The team behind the Ethereum Foundation's Institutional Privacy Task Force (IPTF).

[  Meet the team ](/about/) 

What have you actually built? 

A year of public, open-source work: private bonds (ZK, privacy L2s, FHE), compliance-first private stablecoin transfers, private cross-chain atomic swaps, a validium proof-of-concept, privacy-preserving identity, the Public Rails vs Private Ledgers decision framework, and the Ethereum Privacy Map.

[  Writeups ](/blog/)[  Explore the map ](/explore/) 

Why does this matter? 

Every institutional use of Ethereum (tokenization, stablecoins, settlement) eventually hits the same blocker: a public ledger exposes positions, counterparties, and flows that regulated institutions cannot reveal. Confidentiality with built-in compliance is what makes those deployments viable.

What do you offer institutions? 

Hands-on engineering engagements: privacy architecture and advisory, workshops that turn interest into concrete requirements, proof-of-concepts that de-risk decisions, and the design and build of confidential systems integrated with existing vendors and infrastructure, through to live implementation. Engagements can start small and scoped.

[  Approaches ](/approaches/) 

What's your relationship with the Ethereum Foundation? 

We created and ran the Institutional Privacy Task Force at the EF, and we continue that body of work in active collaboration with EF and EF-aligned teams: coordinating the transition together, keeping the artifacts public, and collaborating on public goods, specs, and privacy work. EthSystems is its own company because commercial delivery needs a commercial structure; the collaboration continues.

How do you relate to Ethlabs and Ethereum Institutional? 

As complementary nodes in the same network, often with overlapping supporters, and as collaborators. Ethlabs builds and grows the core protocol and platform capabilities of Ethereum. Ethereum Institutional is a neutral, non-commercial front door helping institutions understand and navigate the ecosystem. EthSystems is the specialist builder: when an institution moves from evaluating Ethereum to building on it, we're the accountable commercial counterparty that designs and delivers the confidential systems involved.

Is your work open source? 

Yes. Our proof-of-concepts, libraries, frameworks, and the Ethereum Privacy Map are public, and we'll keep publishing. Open, verifiable work is how we earn trust.

[  GitHub · map ](https://github.com/ethsystems/map) 

Where do you operate? 

Globally.

[Read all FAQs→](/faq/) 

## Talk to EthSystems

If you are an institution with a privacy requirement, a builder shipping a solution, or a regulator who wants the picture, we are listening.

[ Contact us Tell us about your requirements and the team will follow up. → ](https://forms.gle/24Ec9Grk5VgFMLX29) [ hello@ethsystems.org General correspondence with the team. → ](mailto:hello@ethsystems.org) [ GitHub · map Open issues, propose patterns, contribute use cases. → ](https://github.com/ethsystems/map) 

×

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://ethsystems.org/#organization","name":"EthSystems","url":"https://ethsystems.org/","logo":"https://ethsystems.org/icon-maskable.png","sameAs":["https://x.com/eth_systems","https://www.linkedin.com/company/ethsystems/","https://github.com/ethsystems"]},{"@type":"WebSite","@id":"https://ethsystems.org/#website","url":"https://ethsystems.org/","name":"EthSystems","publisher":{"@id":"https://ethsystems.org/#organization"}}]}
```