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

Insurance and Recovery Economics: Preparing for Black Swan Events
Earlier designs cut node risk by 73%, but the unpredictable 27% needs different rules. This study fixes how a staking insurance pool is sized (15% of stake, not protected value), bootstrapped, and banded; why a reserve held in its own token collapses with it; and how session protection follows the sync-degree hierarchy when security breaks mid-session.
Oraclizer Core ⋅ May 29, 2026
Tokenized Securities Under the CLARITY Act: The Weight of Codification
The CLARITY Act tokenized securities clause settles a single proposition in statute: tokenization is a delivery method, not a new asset class. That one sentence codifies the regulatory status of tokenized securities in U.S. law for the first time and derives an entire infrastructure specification for boundaries the token crosses.
Oraclizer Core ⋅ May 23, 2026
Sync Degree Hierarchy: Classifying What Assets Demand from State Synchronization
Sync degree hierarchy turns sync requirement strength into a four-level classification axis for RWA assets. S₀ static through S₃ atomic state binding form a reduction relation where causal consistency separates S₁ from S₂. Existing oracles, structurally two independent channels, are capped at S₁ by definition. Regulatory action forces S₃.
Oraclizer Core ⋅ May 20, 2026
Why RWA Isn’t Real DeFi Collateral Yet: The Non-Atomicity of the Collateral Layer
Tokenized RWA-backed stablecoin supply reached $8.5B, yet only 12% operates inside DeFi. Aave Horizon's dual structure separates rather than solves regulatory state synchronization. Three conditions from cross-border securities trading transfer into the DeFi collateral layer, with a fourth condition added when the protocol becomes a regulatory subject.
Oraclizer Core ⋅ May 14, 2026
Node Compensation Framework: Multi-layered Reward Design
After designing how the node incentive pool survives 7.6 years, an unresolved question remained: how are those rewards distributed to individual nodes? Three pressures conflict, and no single-mode distribution satisfies all three. A three-layer framework with activity, throughput, and session continuity, paired with phase-evolving weights, resolves the trilemma.
Oraclizer Core ⋅ May 13, 2026