Skip links

Announcing Horizen Partnership – Part 2: Ecosystem Integration

Oraclizer Update

Oraclizer is announcing a new phase in our strategic partnership with Horizen. This update shares the progress of ecosystem integration between both projects.

Joint Transition to the Base L2 Ecosystem

Horizen has recently decided through a community vote to transition to the Base L2 ecosystem, and Oraclizer is moving in the same strategic direction. Both projects are adjusting their architecture from Polygon zkEVM to L3 solutions built on Base L2, strengthening interoperability between them.

This joint transition provides the following opportunities:

  • Efficient messaging between L3s within the Base ecosystem using OP Stack-based communication
  • Leverage of Base L2’s scalability and institutional-grade infrastructure
  • Access to the liquidity of the Coinbase ecosystem

Technical Integration Direction

The technical integration between Horizen and Oraclizer is occurring at the infrastructure layer. Oraclizer’s state synchronization technology and Horizen’s zkVerify are expected to create complementary synergies.

Oraclizer plans to work with Horizen within the Base L2 to effectively bridge the gap between DeFi and RWA tokenization through L3 integration.

Partnership Significance

This partnership represents the following for both projects:

  • Technical Synergy: Mutual complementarity between Horizen’s zkVerify and Oraclizer’s state synchronization technology
  • Ecosystem Expansion: Shared developer communities and user bases
  • Infrastructure Optimization: Increased development efficiency through utilization of the same underlying technology stack

Future Updates

Additional information regarding the details of the partnership and specific implementation plans will be continuously updated through the official channels of both companies. More details can be found on the official websites and social media channels of both companies.

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