OpenLayer
  • Introduction
    • About OpenLayer
    • Our Mission
    • Our Approach
      • Foundations
        • OpenNodes
        • Restaking
        • Validation services
          • What is OVC
          • How is it done
          • Why is it better
        • Infrastructure
      • Modular Design
        • Modular data source
        • Modular source of security
        • Modular validation
        • Modular data transformation
        • Modular interoperability
      • Lifecycle of a Request
  • Data Validation Light Paper
  • OpenLayer AVS
    • Why Data Layer
    • How OpenLayer Works
    • Crypto Security
      • Websession proofs
      • Parser execution
    • End User Participation
    • On Demand Security
    • Multi Token Staking
    • Zero Bridging Solutions
  • For Node Operators
  • For Developers
    • Public Data Streams
    • VRF (Verifiable Randomness)
    • User Personal Data Proving
  • Privacy Policy
Powered by GitBook
On this page
  1. Introduction
  2. Our Approach
  3. Modular Design

Modular validation

Validation methods are also modular in OpenLayer’s design. The only principle for all validation methods is that they have to be retroactively, cryptographically provable. And for the same type of proof, multiple different providers could provide the service and it’s up to the developers to choose which provider to use.

For example on attested TLS connection. There could be multiple providers providing notary services, some of them may use TEE to enhance the authenticity of their execution, some of them may use multi-notary solutions or multiple notarizations to enhance secureness, some may combine both approaches. Choosing which provider to use is a decision based on requirement for security, trustlessness and cost.

PreviousModular source of securityNextModular data transformation

Last updated 8 months ago