Horizen 백서

Horizen

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 4쪽 중 2쪽

state references, and enforce policy context - all without exposing private data or application logic. This contract layer is composed of three primary modules: 1. ProcessorEndpoint : Coordinates confidential computation requests and responses between decentralized applications and the CCE. 2. TeeAuthenticator : Checks the correctness of the payload produced by the TEE. 3. AuthorityRegistry : Records the entities allowed to request de-anonymized data. Together, these modules establish the verifiable interface that connects encrypted off-chain execution to transparent onchain settlement. The ProcessorEndpoint serves as the operational hub. It queues incoming confidential workloads from decentralized applications, tracks their lifecycle, and records the resulting attestations generated by the Secure Processor Manager. Each attestation (representing a verified computation within the TEE) is validated for authenticity and immutably committed onchain. The contract maintains pointers to the encrypted state stored in the Data Layer, ensuring that while attestations are public, all data and logic remain fully encrypted. Figure 8: On-Chain Smart Contracts for Encrypted, Compliant Workflows Depicts how Horizen’s onchain contracts (ProcessorEndpoint, TeeAuthenticator, and AuthorityRegistry) coordinate encrypted execution flows, validate attestations, and maintain compliance metadata, enabling verifiable computation and settlement without exposing underlying data or logic. The TeeAuthenticator verifies the correctness of the TEE attestation payload. It executes an onchain verification of the payload signature coming from the TEE, providing the guarantee the data has been processed by the expected software in the expected secure enclave, and the result has not been tampered by the processor manager. The AuthorityRegistry is an entrypoint for checking the entities allowed to request data deanonymization. It provides a default mechanism to identify the authorities (implemented by an admin-managed whitelist), but allows every application to define a more custom logic via a specialized smart contract. By design, Horizen’s onchain smart contracts transform the CCE into an auditable subsystem of Base’s broader execution environment. They uphold composability and transparency while ensuring that privacy and compliance remain verifiable through cryptographic proof rather than disclosure. 2.2.4 Component 3: Data Layer The Data Layer provides the encrypted persistence backbone of the Horizen CCE . It offers a secure API for storing, retrieving, and auditing all data produced by decentralized applications (dApps), ensuring that every element of a computation – from bytecode to state and compliance records – remains encrypted at rest, in transit, and during retrieval. Each dApp operates as a self-contained entity within this framework, maintaining its own encrypted internal state and data model. The Data Layer allows every dApp to define how its private state is organized – whether as a ledger, liquidity pool, order book, or another domain-specific structure. These data structures are coupled to the dApp’s WASM logic, which enforces transaction rules, compliance controls, and workflow constraints inside the TEE. Three principal kinds of data are managed through the Data Layer API: ● WASM application bytecode , representing the executable logic of each dApp. ● Application state , encrypted with the TEE key, preserving confidentiality so that only attested execution environments can decrypt or update it. ● Deanonymization reports , encrypted with an authority key, enabling authorized oversight under defined compliance contexts. After every confidential execution, the TEE commits the updated encrypted state root to the Horizen Chain, anchoring the computation to a verifiable public record. The corresponding full encrypted state is stored in the Data Layer for durability, recovery, and compliance audits . Each new state version links cryptographically to the previous one, forming an immutable and verifiable history of encrypted state transitions without revealing underlying data. Additionally, the Data Layer is structured to allow flexibility in adopting decentralized data-availability options to ensure resilience and long-term verifiability. Figure 9: Data Layer for Encrypted State & Compliance Persistence Depicts how each dApp defines and manages its own encrypted data structures, WASM logic, and compliance artifacts, with every state update committed onchain and the full encrypted state persisted for durability and auditability. This dApp-centric design ensures that encryption is pervasive and persistent - no plaintext bytecode, key, or report ever exists outside attested environments. By coupling private data ownership with verifiable auditability, the Data Layer allows decentralized applications to achieve true compliant privacy while remaining composable with the public settlement and liquidity of Base. 2.2.5 Component 4: Authority Service The Authority Service provides the oversight and auditability framework that enables privacy to coexist with regulatory and organizational accountability. It allows authorized entities to request, verify, and decrypt audit artifacts through controlled, onchain governance - ensuring that transparency is verifiable, scoped, and cryptographically enforced. At its core, the Authority Service operates under an authority-based model , where each dApp defines its own compliance structure and associated oversight entities. These authority entities (such as custodians, compliance officers, or designated auditors) are registered onchain and validated through authenticated public keys or decentralized identifiers (DIDs). This establishes a verifiable link between a dApp’s internal policy and its external accountability framework. This model differs from traditional viewing-key systems, which delegate disclosure to individual users and often lack reliable audit trails. In Horizen’s design, disclosure is mediated through cryptographic attestations and onchain events, ensuring that access occurs only within an auditable and verifiable process defined by the dApp’s compliance policy. When an authorized entity initiates a deanonymization request, the Authority Service coordinates the process through onchain smart contracts. It validates the requester’s credentials and verifies that the request conforms to the dApp’s registered policy parameters. Once confirmed, the system triggers an invocation of the TEE. Inside the enclave, the Secure Processor Manager generates a deanonymization report (encrypted with the authority’s public key) containing only the approved subset of information, such as transaction metadata, balance proofs, or identity attestations. Each deanonymization event is immutably recorded onchain, providing a cryptographic record of access without disclosing the contents of the report. This creates a two-fold structure of accountability: 1. On-chain transparency , through visible records of every access request and attestation. 2. Cryptographic containment , through key-based encryption that limits data visibility strictly to approved authorities. Figure 10: Authority Service for Encrypted Oversight & Auditability Depicts how the Authority Service authenticates registered authorities, retrieves encrypted deanonymization reports, and enables verified access under onchain accountability in accordance with dApp-defined compliance rules. The Authority Service is tightly integrated with the Data Layer and AuthorityRegistry , enabling controlled retrieval of encrypted records for audits and compliance verification. Every request, authorization, and output remains encrypted end-to-end, preserving the confidentiality of the underlying data while allowing external validation of compliance activity. Through this architecture, the Authority Service establishes a verifiable model of compliant privacy , where decentralized applications can satisfy oversight and regulatory expectations without sacrificing confidentiality. It bridges cryptographic integrity with institutional accountability, allowing Horizen to support enterprise, financial, and public-sector applications that require both privacy and verifiability. 2.2.6 Redundancy Considerations As with any form of hardware-backed execution environment, TEEs may encounter faults, deprecations, or newly discovered vulnerabilities over time. The Horizen Protocol is designed with this reality in mind: the system supports enclave rollover and re-attestation, allowing faulty or outdated TEEs to be safely replaced without disrupting dApp state or execution guarantees. Looking forward, the protocol treats TEE redundancy as an ongoing design consideration, prioritizing mechanisms that allow execution to continue even when individual enclaves must be rotated out for security or reliability reasons. 2.3 Horizen Chain 2.3.1 Chain Architecture and Base Anchoring The Horizen Chain forms the execution and settlement backbone of the Horizen Protocol. It is purpose-built to extend Base’s scalability and liquidity into a compliant-privacy domain by combining three key architectural elements: anchoring to Base’s native data-availability layer, fast omnichain bridging through Stargate V2 (LayerZero), and confidential execution through the Horizen Confidential Compute Environment (HCCE). Together, these components allow Horizen to maintain interoperability with Base’s ecosystem while enabling verifiable, compliance-ready privacy. 1) Base-Anchored Rollup Horizen operates as an OP Stack L3 rollup that publishes its transaction data and state commitments directly to Base’s native DA layer. This anchoring model allows Horizen to inherit Base’s scalability, composability, and sequencing infrastructure while remaining economically aligned with Ethereum. By finalizing all data and proofs on Base, Horizen inherits Ethereum’s security and finality guarantees implicitly through Base, creating a unified trust model from confidential execution to public settlement. 2) Fast Bridging via Stargate V2 (LayerZero) Interoperability and liquidity between Horizen and Base are facilitated by Stargate V2, LayerZero’s cross-chain routing primitive designed for unified liquidity across networks (LayerZero Labs, 2025). At launch, native ETH serves as the first supported asset with shared liquidity pools between Horizen and Base, enabling transfers that settle within seconds and achieve guaranteed finality without wrapped or re-minted tokens. Stablecoins such as USDC.e are bridged through Hydra’s Omnichain Fungible Token (OFT) framework (HydraDX, 2025). Support for additional assets (such as WBTC, cbBTC, and cbETH) is planned through a combination of custom OFT deployments or dedicated Stargate V2 pools as the ecosystem matures. This bridging framework ensures that privacy-oriented dApps on Horizen can access Base’s liquidity directly while maintaining seamless composability within the broader Ethereum and Superchain environment. 3) Connection to the Horizen Confidential Compute Environment (HCCE) Each application deployed on the Horizen Chain can connect natively to the HCCE, where its logic executes inside attested TEEs. The chain provides standardized runtime APIs for dApps to offload private computation, receive encrypted results, and anchor attested state roots and compliance metadata onchain. This linkage ensures every confidential operation executed within the HCCE is transparently verifiable on Base through Horizen’s settlement process, preserving both privacy and auditability. Figure 11: Horizen Chain and Base Anchoring Depicts the three foundational elements of the Horizen Chain: Base-anchored rollup settlement, fast bridging via Stargate V2, and secure connection to the HCCE for confidential execution and policy-aware computation. 2.3.2 Ecosystem of Privacy DApps The Thrive Builder Funding Program is the primary growth engine of the Horizen Chain , established in partnership between Horizen and Thrive Protocol to fund privacy-first builders across the Base ecosystem. Season 1 of the program allocates 200,000 ZEN in funding for approximately 25 to 50 high-impact projects, with average grants of $50,000 - $100,000 per project. Funding is milestone-based and results-driven, tracking total value locked in ZEN, transaction volume, and active wallets as key metrics of network growth and impact (Thrive Protocol, 2025). The program supports projects that advance privacy as core infrastructure for decentralized applications. Approximately 40% of funding targets privacy-centric DeFi protocols (e.g., private DEXs, confidential lending, hidden order books), 30% supports verified AI and machine-learning use cases (such as privacy-preserving training and ZK model verification), and 30% is directed toward gaming and governance systems (including private voting and ZK-based reputation). All applications deployed on the Horizen Chain have the ability to access fast omnichain bridging via Stargate V2 and the Horizen Confidential Compute Environment (HCCE) if desired, enabling rapid liquidity movement and confidential execution within a unified compliance framework. By combining Horizen’s privacy-focused chain architecture with Thrive’s GDP-layer funding model, the program establishes a merit-based ecosystem that rewards measurable adoption and advances the future of compliant privacy on Base. For economic design and sustainability details, see the Horizen Tokenomics Whitepaper (Horizen Labs, 2025). 2.3.3 Near-Term Roadmap The Horizen Chain is designed as a continuously evolving privacy infrastructure that advances in parallel with Base and the broader Superchain ecosystem. Each phase strengthens the protocol’s compliance, verifiability, and interoperability while preserving alignment with Base’s liquidity and the Horizen Confidential Compute Environment (HCCE). 1. Base Anchoring & Liquidity Alignment Horizen Chain anchors to Base’s native data-availability layer, inheriting its scalability, security, and settlement guarantees. This phase also establishes fast cross-chain bridging through Stargate V2, enabling shared liquidity between Horizen and Base and forming the foundation for subsequent privacy-focused upgrades. 2. Phase 2: Confidential Execution & Compliance Toolkit Building on this foundation, Phase 2 introduces confidential execution via the HCCE, supported by a built-in compliance and authorization framework. It establishes a compliance toolbox for KYC, accreditation, and privacy-preserving identity (DID / zkID), allowing applications to meet regulatory requirements without sacrificing privacy or composability. 3. Phase 3: Validity Proofs & Accelerated Finality The final phase integrates validity-proof frameworks such as OP Succinct and Risc Zero Kailua to replace the traditional optimistic challenge window with cryptographic verification, reducing settlement times from days to minutes. This advancement delivers fast, verifiable withdrawals and cross-chain settlement between Horizen and Base, completing the progression toward fully verifiable privacy infrastructure. Figure 12: Horizen Chain Near-Term Roadmap Shows the three developmental phases of the Horizen Chain: Base anchoring, chain-level compliance, & validity-proof verification - illustrating its progressive evolution toward faster and more verifiable privacy execution. Together, these phases outline a clear trajectory from anchored compliant execution to cryptographically verified confidentiality, ensuring that Horizen evolves as a foundational, Base-aligned privacy infrastructure. 3. Applied Research at the Privacy Frontier 3.1 Privacy as a Progressive Continuum Horizen also views compliant privacy as a progressive continuum , not a static endpoint. The current protocol represents a practical first phase, built on TEEs and ZK verification. Future iterations are designed to evolve alongside emerging technologies such as Fully Homomorphic Encryption (FHE) and next-generation ZK proof systems , allowing the Horizen Protocol to adapt as Base and the broader Superchain ecosystem advance toward deeper programmable privacy. Horizen’s Privacy Development Roadmap is divided into four stages, each of them integrating progressively more advanced technologies in order to achieve more and more robust privacy applications. 3.2 Stage 0: Near-Term Our choice to initially build on TEEs is a deliberate and strategic decision rooted in pragmatism. While purely cryptographic solutions like general-purpose Zero-Knowledge Proofs (ZK) and FHE hold immense promise for the future of onchain privacy, they are not yet mature enough for widespread, production-grade deployment. ZK systems currently face significant challenges with high proving times, circuit complexity, and poor developer ergonomics, while FHE remains orders of magnitude too slow for most practical applications. In contrast, TEEs offer a solution that is mature, performant, and deployable today . The key advantages that make TEEs the ideal foundation for Horizen's compliant privacy layer include: ● Production Readiness: TEE technology is a mature field, with hardware-backed solutions widely deployed in data centers and cloud environments globally. ● Near-Native Performance: Computation within a TEE occurs at speeds close to native execution, avoiding the latency and computational overhead associated with current ZK and FHE systems. ● Developer-First Approach: The Horizen Confidential Compute Environment is designed to support mainstream development workflows. It accommodates widely used programmin
프로젝트로 돌아가기