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

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