Shuttle Docs
  • Trusted Execution Environments
    • Confidentiality
    • Execution Integrity
    • Remote Attestation
    • Threat Models
    • Side-Channel Attacks
    • Side-Channel Attack Mitigation
    • Model Types
  • Foreword
    • Shuttle
  • Solution #1
    • Blockchain | Framework Alignment
    • Enarx
    • Web Assembly System Interface(WASI)
  • Solution #2
    • Attestation
      • SGX DCAP
      • Intel Trust Authority
    • Decentralizing Attestation
      • It’s Butterfree!
      • Decentralized Public Key Infrastructure(DPKI)
      • Our Tool: Cryptographic Accumulator
      • Re-attestation
  • Blockchain
    • Reducing Computational Overhead
    • Ekiden
    • Verifier's Dilemma
    • Independent Layers
    • Security of Enclaves & Consensus
    • Non-Byzantine Computation
      • Discrepancy Detection - Good Idea Oasis!
    • Roughtime
  • Avalanche
    • Multi-dimensional Fees
    • Stakeless?
  • Privacy
    • Confidential Blockchain
    • Secret Network Vulnerability - 2022
  • Summary
    • Market Potential
    • Cosmos, Polkadot, Avalanche
Powered by GitBook
On this page
  1. Blockchain
  2. Non-Byzantine Computation

Discrepancy Detection - Good Idea Oasis!

In the event of a discrepancy, the computation must be redone by a separate, larger compute committee, which will determine the correct results. Since all commitments are traceable to specific compute nodes, any node(s) responsible for producing incorrect results can be identified. In Oasis this would lead to slashing but for our purposes we can say that their credentials will simply be removed from the accumulator.

PreviousNon-Byzantine ComputationNextRoughtime

Last updated 6 months ago