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 source of security

At the moment OpenLayer users economic security coming from restaked assets, namely EigenLayer. Long term though, the economic security will also be modular.

OpenLayer will be on all the restaking protocols as well as allow direct staking of alternative assets, so a developer can choose what kind of security bucket they want, to security their own protocol. For example, a protocol built solely for operating and transferring EXAM token cross chains may want to source security based on EXAM token versus having their protocol secured by ETH for better value alignment and cost effectiveness.

The modular security design not only allows each project to define their own security tolerance, reduce cost and better align values, it also makes the entire ecosystem become potentially usable security and thus expanding the security pool.

PreviousModular data sourceNextModular validation

Last updated 8 months ago