0% read

Last updated:

Horizen

Horizen is an -compatible blockchain built on using the OP Stack. It is designed to support onchain applications that require confidential execution and programmable compliance, with potential applications across , payments, institutional finance, and . [1]

Overview

Horizen is an -compatible blockchain built with the OP Stack that settles onto , which in turn settles onto . Its current architecture was established after ZEN balances were migrated from the original Horizen mainchain and EON chain to a -native contract in July 2025. The network is developed by Horizen Labs, which also develops Vela, a confidential-computation system, and zkVerify, a verification and attestation protocol. The Horizen Foundation oversees ecosystem stewardship and operates under the governance framework established by the Horizen DAO Constitution.

Horizen is designed to support applications that require confidentiality, auditability, or compliance while retaining compatibility with the development stack. Developers can use standard Solidity and familiar tools and choose among different privacy approaches, including Vela's trusted execution environments, zkVerify's zero-knowledge infrastructure, or confidentiality mechanisms implemented directly at the application level. Applications can keep selected computations or data confidential while providing cryptographically verifiable information for auditing and compliance, and assets can move between Horizen and through native and -based bridges. The architecture is intended to support use cases including , payments, institutional finance, and AI applications without requiring every application to adopt the same privacy technology. [4]

History

Horizen's current architecture followed a migration that consolidated ZEN balances from both the original Horizen mainchain and the EON chain onto a single on , with the process completed on July 23, 2025. EON balances, including staked balances, were automatically migrated to corresponding addresses, while balances from the original ZEND mainchain required users to claim their funds through a dedicated backup vault because the mainchain's -style address format could not be directly mapped to -compatible addresses. Following the migration, both legacy chains were discontinued, and ZEN activity was consolidated within -based as Horizen transitioned to its current form as an settling on . [1]

Features

Vela

Vela is a confidential compute layer developed by Horizen Labs for private execution on Horizen Chain. It uses Trusted Execution Environments (TEEs), which isolate application computations in hardware-protected enclaves and produce cryptographic attestations that the computation was performed correctly. Applications can therefore keep sensitive data, positions, and execution logic hidden from the public and the infrastructure operator, while publishing encrypted outputs and verifiable evidence of execution onchain. Vela is intended to support confidential applications that also require auditability and compliance, with potential use cases including , institutional finance, payments, and other applications where transaction or business data cannot be fully public. [5]

Architecture

L3 Model

Horizen Chain operates as an -compatible OP Stack rollup that settles directly onto , creating a layered architecture in which provides the underlying security and final settlement, provides execution scalability and data availability, and Horizen provides application execution and coordination. Horizen publishes transaction data and state commitments to while inheriting its sequencing and infrastructure, allowing applications to operate within the broader ecosystem. Confidential computation can be added through Vela, a separate coprocessor that executes sensitive workloads inside trusted execution environments (TEEs), produces cryptographically attested results, and anchors those results on-chain. Operating as an independent also gives applications shared infrastructure such as a common address space, composability, and , rather than requiring them to operate as a disconnected collection of applications directly on . [6]

Privacy and Compliance

Horizen uses a privacy-agnostic approach in which applications can select different confidentiality mechanisms according to their requirements rather than relying on a single mandatory architecture. Vela provides confidential execution through trusted execution environments (TEEs), keeping application data encrypted during processing while producing cryptographic attestations of the computation; it is designed as a chain-agnostic coprocessor that can serve -compatible networks beyond Horizen. Applications can also use zkVerify for verification and attestation or implement simpler confidentiality mechanisms directly within Solidity contracts when dedicated TEE or ZK infrastructure is unnecessary.

Compliance is similarly implemented at the application level rather than enforced through a universal platform-wide rule set. Developers can encode deterministic controls such as allowlists, role-based permissions, jurisdiction restrictions, and transaction limits directly into , while Vela can handle compliance checks involving sensitive information by executing verification logic privately and producing attestations that authorized auditors or regulators can verify without accessing the underlying data. Horizen also supports third-party / screening through , which performs risk checks off-chain and returns signed verification data that can validate before allowing a transaction or other business logic to proceed. [7]

ZEN

ZEN is the native coordination, value-routing, and of the Horizen ecosystem. It is an token on that can be bridged to Horizen Chain through framework, but it is not used to pay on Horizen. Instead, ZEN is intended to support , ecosystem coordination, governance, and application-level utility, with its broader economic role tied to activity across the network. rewards are designed to come from multiple sources, including bootstrap incentives, liquidity-provisioning activity, protocol fee shares from applications, VFY emissions associated with zkVerify nodes, planned Vela-related economics, and sequencer revenue. Other assets supported within the ecosystem include and , while and other supported assets can move between and Horizen through the native OP Stack bridge or -based bridging infrastructure.

ZEN also has a role in Horizen's governance structure through the Horizen DAO, which provides the framework for community participation in decisions affecting the ecosystem. Governance allows community members to submit and vote on proposals through defined categories and procedures, with the DAO Constitution and related foundational documents establishing the responsibilities and mandate of the Horizen Foundation. In this structure, ZEN's function extends beyond being a transferable token to serving as part of the mechanisms through which economic activity, , and governance are connected across the ecosystem. [2] [8]

Tokenomics

ZEN has a total supply of 21M tokens and has the following allocation: [10]

  • Collator Rewards: 40%
  • Horizon Foundation: 32.5%
  • Ecosystem Development: 15%
  • ZEN Growth: 10%
  • DAO Treasury: 27.5%
  • ZEN Sustainability Initiative: 17.5%
  • Community Grants: 5%
  • Growth Marketing: 5%

Partnerships

  • Obscura
  • AdPriva
  • Goldsky
  • Stork
  • Caldera
  • ZENDEX
  • Tachyon
  • Lighter.IM
  • Amaanah
See something wrong?

References (10 sources)

HomeCategoriesWiki MCEventsGlossary