When Ethereum Absorbs the Verifier: Aligned’s 2026 ZK Infrastructure Pivot

The infrastructure decision

On July 21, 2026, Aligned announced that it would deprecate its Proof Verification Layer and stop sending tasks to it. The company is directing users toward its Proof Aggregation Service, which it describes as inheriting Ethereum-level security.

The decision is notable because the retired layer was not a small experiment. Aligned says it verified more than 136,000 proofs, had 59 operators over its lifetime, supported systems including Groth16, Plonk, SP1, RISC Zero, and Circom, and reached roughly 2,100 gas per proof at launch.

Why the middle layer lost its advantage

Aligned identifies three changes. Proving and aggregation systems improved, making dedicated low-cost verification less necessary. Ethereum’s own roadmap is moving toward native ZK support. And, according to Aligned’s account of customer demand, developers valued Ethereum’s security inheritance more than ultra-low latency.

That changes the design question for ZK builders. The key choice is no longer simply where a proof can be verified cheaply. It is where verification should live, what security domain it inherits, and whether an extra operator network creates enough value to justify its operational surface.

For applications, aggregation can reduce the number of proofs that need to reach Ethereum while preserving a stronger settlement anchor. But it may introduce different trade-offs around batching, latency, failure recovery, and service availability. Builders should therefore treat aggregation as an architectural boundary—not as a drop-in replacement whose performance and trust assumptions are automatically identical.

What Ethereum’s roadmap changes

Ethereum’s current privacy roadmap lists optional execution proofs and Verkle Trees as targets for the Hegotá upgrade, while describing zkVM-based execution proofs as part of the path toward lower-cost validation and private computation. This gives middleware providers a strategic signal: infrastructure that complements Ethereum’s native proving direction may have a longer runway than infrastructure whose main purpose is to compensate for today’s verification costs.

The roadmap is still provisional. Its milestones are targets rather than finalized commitments, and governance or research can change them. That uncertainty matters when teams choose a proving or verification dependency with a multi-year lifecycle.

A practical audit for ZK teams

Before adopting a verification service, teams should record four assumptions: which chain ultimately secures the result, whether proofs are individually verified or aggregated, what happens when the service is unavailable, and which latency guarantees are contractual rather than aspirational. Aligned’s pivot is a reminder that the verification layer itself can become the moving part.

The broader lesson is not that dedicated ZK infrastructure has failed. It is that successful infrastructure can be made strategically redundant when the base protocol absorbs its strongest feature. For developers, portability across proof systems and explicit security assumptions may now matter more than optimizing for a single verification route.