Skip links

Horizen Protocol Whitepaper: A New Chapter in Privacy Infrastructure for Base

Horizen Labs has officially released the Horizen Protocol Whitepaper v1.0.0. This whitepaper presents a vision for building regulatory-compliant privacy infrastructure on the Base blockchain, adding new dimensions to our existing partnership with Horizen.

Horizen Protocol Overview

Horizen Protocol consists of two core components:

Horizen Confidential Compute Environment (HCCE): A confidential computing environment based on Trusted Execution Environments (TEE), where data remains encrypted at rest, in transit, and during verification. It supports various confidential financial applications including KYC-verified transfers, institutional settlements, and regulated asset issuance.

Horizen Chain: An OP Stack-based L3 rollup anchored to Base’s native DA layer. It supports native ETH and USDC.e through fast bridging via Stargate V2 (LayerZero).

Balancing Privacy and Regulatory Compliance

A particularly noteworthy aspect of the whitepaper is the Authority Service design. While existing privacy solutions have pursued absolute anonymity, Horizen introduces a new approach: “dApp-defined audit policies.”

  • Deanonymization requests from regulatory authorities are validated on-chain
  • Encrypted reports can only be decrypted with authorized authorities’ public keys
  • Immutable audit trails maintained for all access events

This reflects Horizen’s core philosophy: “Privacy flows with liquidity.” It’s an attempt to provide institutional-grade privacy while leveraging the liquidity of the Ethereum ecosystem.

Implications from Oraclizer’s Perspective

While Oraclizer and Horizen solve different problems, we share a common philosophy: harmonizing regulatory compliance with blockchain innovation.

AspectHorizen ProtocolOraclizer
Core ProblemLack of on-chain privacyOn-off chain state disconnect
ApproachTEE-based confidential computeBidirectional state synchronization
Regulatory CompliancePost-hoc audit (Authority Service)Pre-verification (RCP/OCID)
InfrastructureBase L3 (OP Stack)Base L3 (Polygon CDK)

Both projects are building their specialized domains within the Base L3 ecosystem. While Oraclizer leverages Horizen Labs’ zkVerify for proof verification, Horizen Protocol focuses on TEE-based confidential computing—complementary approaches within the same partner ecosystem.

An Extension of Existing Collaboration

Oraclizer already leverages Horizen Labs’ zkVerify network to optimize zk proof verification costs. This Horizen Protocol whitepaper release reaffirms that our strategic directions are aligned:

  • Shared Vision: Both projects committed to regulatory-compliant blockchain infrastructure
  • Base Ecosystem: Building L3 solutions on the same L2 foundation
  • zkVerify Partnership: Oraclizer utilizes Horizen Labs’ proof verification infrastructure

Horizen Protocol’s privacy infrastructure and Oraclizer’s state synchronization technology operate independently, yet hold potential for synergy in future composite use cases such as privacy-preserving RWA tokenization.

Looking Ahead

Horizen Protocol presents a four-stage privacy technology roadmap, with long-term plans to integrate next-generation cryptographic technologies including FHE (Fully Homomorphic Encryption), STARKs (quantum-resistant proofs), and zkEVM.

Notably, Horizen has launched the Thrive Builder Funding Program with 200,000 ZEN allocated to support 25-50 privacy-focused projects—40% for privacy DeFi, 30% for verifiable AI/ML, and 30% for gaming and governance applications. This signals a serious commitment to ecosystem development.

The Oraclizer team will continue monitoring Horizen Protocol’s development and exploring how our technologies can interact within the Base ecosystem.

The full Horizen Protocol whitepaper is available through Horizen’s official channels.

Read Next

The Cross-Domain State Preservation Functor: What It Closed, and What It Was For
The cross-domain state preservation proofs are closed: homomorphism, functor completion, a natural-transformation tower, and unconditional bounded convergence. Ten theory files, zero sorry. The harder work was catching what passes a prover while saying nothing: a trivial functor, a bypassed threshold, a witness outside the roster. Each retreat left the rest firmer.
Oraclizer Core ⋅ Jul 16, 2026
Sync Degree Enforcement: What Turns a Classification Into a Constraint
A classification does nothing on its own. Sync degree enforcement closes the gap between labeling an asset S2 and having the system refuse to touch it any other way. It rests on a two-directional result: over-provisioning preserves every guarantee, under-provisioning admits a state that defeats all of them. So the check leaves runtime and enters Rust's type system.
Oraclizer Core ⋅ Jul 16, 2026
ERC-8319: A Citable Regulatory Constitution for Tokenized Assets
The ERC-8319 Regulatory Compliance Protocol has entered Ethereum's standards repository. It defines the legal effect of six enforcement actions on tokenized assets, from a reversible freeze to an irreversible confiscation, and compiles 31 requirements from 15 regulators under five principles. A convention, not an interface, under one permanent, citable identifier.
Oraclizer Core ⋅ Jul 14, 2026
ERC-8319 Regulatory Compliance Protocol Enters the Ethereum Standards Process
Oraclizer's Regulatory Compliance Protocol has been submitted to ethereum/ERCs as ERC-8319 and is under editor review. Not a glossary but a reference bundling a taxonomy of six enforcement actions, their legal effect, the dynamics between them, and 31 regulator requirements, layered non-invasively on existing standards. Co-authored with Horizen Labs and Dan Spuller.
Oraclizer Core ⋅ Jul 11, 2026
Three Category Axioms, One Proved Functor
A research-journal account of mechanizing the functor laws and the degree-hierarchy natural transformation in Isabelle/HOL, where the obstacles were almost never the mathematics. The measure decrease I feared closed at once; a reserved keyword broke seven builds; a finiteness clash forced a redefinition; and the code overturned my belief that glue gives validity.
Oraclizer Core ⋅ Jun 06, 2026