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

We Joined Observer Patch Holography: Proving Outside Our Own Stack
Oraclizer CPTO Jay Kim, publishing as Jinwook Kim, is credited on three public OPH repository manuscripts. This update records the formal-verification contribution and links to the r2033 snapshot; the manuscripts are not yet archived or peer-reviewed journal publications.
Oraclizer Core ⋅ Aug 18, 2026
Formalizing ERC-TRUST from Normative Rules to Executable Semantics
Discharging a proof obligation does not mean it constrains anything. If no reachable state satisfies its premise, the obligation passes vacuously and the checker stays silent. This is how ERC-TRUST lowered its normative sentences into machine-checkable state transitions, built an execution for every rule, and drew the line at legal fact.
Oraclizer Core ⋅ Aug 11, 2026
When Regulatory Actions Do Not Commute: Order, Outcome, and Sixty Normal Forms
Enforcement standards define what a freeze or a confiscation does, and say nothing about what happens when two commands overlap. Regulatory action composition closes that gap in Isabelle/HOL: twenty-one action pairs split into twelve commuting and nine not, each non-commuting pair with a witness, and exactly sixty state transformations behind unbounded sequences.
Oraclizer Core ⋅ Jul 31, 2026
Defining the Sync Unit: Oracle Usage Metering for State Synchronization
The State Subscription economy has quoted ten Sync Units for a dollar without ever fixing what one Sync Unit counts, leaving three conflicting conversion rates inside one body of work. This study anchors the unit to a single committed state binding and derives its weight from the sync degree hierarchy. Applying it inverts the existing frequency bands.
Oraclizer Core ⋅ Jul 25, 2026
Designing the ERC-TRUST Enforceability Architecture
A regulator's freeze and a court's confiscation are legally opposite, yet on today's token standards they compile to the same call. This ERC-7943 conformance extension makes each of the six regulatory actions a typed, distinct object whose legal effect is verifiable on-chain, and carries that meaning from the abstract model down to deployed bytecode as evidence.
Oraclizer Core ⋅ Jul 23, 2026