The Enterprise Blockchain Experiment Is Over: ZK + Ethereum Define the New Standard

Introduction — “Enterprise blockchains did not deliver the promised future”

※ This post is published as a preliminary version and will be updated to the final Daily Crypto Times (DCT) format in 2 days.

Over the past few years, financial institutions and large enterprises have been moving with one shared conviction: they believed they needed “blockchain”, but that public chains like Bitcoin or Ethereum were not suitable in terms of regulation, privacy, and control. So they told themselves:

“We will build our own blockchain.”

A wave of private chains followed, initially presented as something that would combine “the best of both worlds”. But as time passed, the reality turned out to be the opposite.

They were centralized enough to be controlled, yet still carried the complexity and slowness of decentralization. They were private enough to exclude the public, yet failed to provide true privacy in a meaningful way.

As Merlijn The Trader summarized from Vitalik’s message, this is the core problem: enterprise blockchains did not combine the strengths of both worlds, they combined the weaknesses.

And Vitalik proposes a completely different path. He tells institutions: “Do not build a new chain.” Instead, he suggests the following:

Keep your existing servers as they are.
Add only a circuit that generates ZK proofs on top of them.
Then anchor those proofs to Ethereum via smart contracts.

This is not just a piece of technical advice. It is closer to a declaration of a new way: a way to connect information systems that institutions have been running for decades directly to Ethereum’s security and integrity guarantees.

In other words, institutions do not need their own chains. What they need is Ethereum’s security and the integrity guarantees of ZK. Let’s now unpack this message from a technical perspective.

1. Enterprise proof circuits vs. L1 verifier — fundamentally different from “enterprise blockchains”

The core of an enterprise ZK architecture is separation of roles. The institution generates proofs that it followed its internal rules based on its own data, and Ethereum only checks whether those proofs are valid.

Consider a simple internal rule:

“After a transfer, the account balance must not be negative.”

Inside the institution’s servers, there are concrete values like balance_before = 100, amount = 30, balance_after = 70. But these values are never exposed externally.

The institution encodes this rule as a set of mathematical constraints:

balance_after = balance_before - amount
assert(balance_after >= 0)

It then plugs the real data into this circuit and generates a zk-proof that the constraints are satisfied. Here, balance_before, amount, and balance_after all remain private as witnesses.

Ethereum (L1) never sees this data. L1 only knows one thing:

“This proof must satisfy this circuit (rule).”

L1 does not re-check the business rule itself. It only checks whether the proof satisfies the circuit. This is the essence of enterprise ZK, and it is structurally very different from traditional “enterprise blockchains”.

2. Enterprise ZK is also fundamentally different from L2 zk-rollups

Despite the similar naming, enterprise ZK and L2 zk-rollups have completely different structures and goals.

L2 zk-rollups exist primarily for scalability. Anyone should be able to reconstruct the state, and all transaction data must be published to a data availability (DA) layer.

Enterprise ZK, on the other hand, exists for integrity + privacy. All data stays inside the institution’s internal databases, and only the state root and the proof are posted to L1. No DA is required.

L2 zk-rollups need to implement the entire EVM (or equivalent logic) as a circuit, while enterprise ZK only needs to encode the institution’s specific rules. The circuit size and cost are therefore dramatically smaller.

In short, L2 zk-rollups are “public scalability systems that anyone can verify,” while enterprise ZK is a “closed integrity system where data remains private but rule compliance is provable.”

3. Why must zk-proofs be submitted to L1 — and not to a TTP?

This naturally raises a question: “Do these ZK proofs really need to be submitted to Ethereum? Couldn’t we just send them to a trusted third party (TTP) instead?”

The moment you submit proofs to Ethereum, something crucial happens: trust is no longer required.

L1 cannot be tampered with. If a proof does not satisfy the circuit, verification fails 100% of the time. Even if an institution manipulates its internal data, it cannot generate a valid proof for false data. Ethereum will not be fooled.

Another key property is immutability. Once recorded on Ethereum, entries cannot be deleted, modified, or rolled back. This makes them extremely powerful as regulatory, audit, and legal evidence.

This structure is also highly meaningful for inter-institution collaboration. Even if Bank A and Bank B do not fully trust each other, as long as both trust Ethereum, Ethereum becomes the “source of truth”.

Now consider the alternative: submitting proofs to a trusted third party (TTP). In that case, everything reverts back to a trust-based model. The TTP could be compromised, collude with an institution, or be hacked, or even delete records.

In inter-institution scenarios, the question “Why should we trust that TTP?” never goes away. Immutability is not guaranteed either.

In summary, L1 removes trust from the model, while TTPs add another layer of trust.

Conclusion — Institutions don’t need their own chains, they need Ethereum

Vitalik’s “retrofit” model offers a highly pragmatic path for institutions.

Keep your existing servers as they are.
Add only ZK proof generation on top.
Then anchor those proofs to Ethereum.

This approach simultaneously achieves:

• Data remains private.
• Rule compliance is publicly verifiable.
• No separate data availability (DA) layer is required.
• No fraud-proof mechanism is needed.
• Ethereum L1’s security and immutability are inherited.
• Trust issues between institutions are structurally reduced.

The combination of “privacy + integrity + security” that institutions have been searching for over many years is realized here in the simplest possible way. And that path does not start with building a new chain, but with putting ZK on top of Ethereum.

Younchan Jung
Researcher exploring structural shifts in AI, blockchain, and the on‑chain economy.

If you would like to read this article in Korean, please click the button below.

Read This Article in Korean →