Corex Network
  • Concept
  • INTRODUCTION
    • Capabilities
    • General Architectural Outline
  • Joint Computing Environments
    • Outline and Operation
    • Standards and Cryptography
    • Auxiliary Channel Protection
  • NODES
    • Setup & Configuration
    • Management & Incentives
    • Efficiency and Stability Monitoring
    • Secure Execution Zones
    • Node Staking
      • Delegation Dynamics & Vesting Durations
  • CLUSTERS
    • Function and Formation
      • Fork & Migrate
    • Authorization & Incentives
    • Acceptance & Allocation
  • COMPUTATIONS
    • Identifying a Computation
      • Computation Units
    • Computation Initiation
      • Computation Timeline
      • Computational Input Data
  • TOKENOMICS
    • $HEAI
    • Liquidity Management
  • SOCIALS
    • Website
    • Twitter
    • Telegram
Powered by GitBook
On this page
  1. Joint Computing Environments

Auxiliary Channel Protection

PreviousStandards and CryptographyNextSetup & Configuration

Last updated 6 months ago

Some confidential execution platforms, such as , depend on hardware to obscure sensitive data. However, this reliance has exposed them to various auxiliary attacks which compromise their privacy and security by allowing information extraction and manipulation. In contrast, is based entirely on computational and information-theoretic security, ensuring that as long as security assumptions hold, no malicious peer or group of peers can extract or tamper with data.

Despite this robustness in theory, some implementations of secure multi party computation may still face risks from timing attacks that can occur when attackers analyze differences in response time during data exchange to infer private information, as certain operations take longer depending on the values involved. Corex Network solution is to use constant-time operations, where the execution time is consistent regardless of input, ensuring that data cannot be compromised through such timing-based exploits.

Secure Execution Zones
BDOZ