Ola Documentations ₿
Ola Documentations ₿
Ola Documentations ₿
  • Welcome to Ola
  • Ola Introduction
    • Sin7y Labs
    • Our investors
    • Our Ecosystem Partners
    • Important Links
    • Ola Foundation
    • Ola Tokenomics
      • $OLA Total Supply
      • $OLA Utility
      • $OLA Distribution and Vesting Plan
    • Ola Roadmap
    • Ola Important Timeline
  • Bitcoin's Potential with Ola
    • The State of Bitcoin
    • Current Limitations
    • The Future of Bitcoin
    • Ola: A Trust-Minimized Decentralized BTC Infrastructure
    • Bitcoin's Future with Ola
  • Ola Network Core Components: Onis & Massive
    • Onis
      • 1. Introduction
      • 2. Challenges in Cross-Chain Interoperability
      • 3. Ola Solution: A trust-minimized BTC Cross-Chain Network
        • 3.1 Core Technical Architecture
        • 3.2 Permissionless Slashable Bridge Paradigm for Bitcoin
        • 3.3 Trust Nobody, Bridge Yourself
        • 3.4 Customize Bridge Strategies
        • 3.5 Application of ZK Technology
      • 4. Use Cases for Ola
      • 5. Key Advantages of Ola
      • 6. Future Roadmap
        • Technological Development
        • Ecosystem Expansion
        • Feature Updates Timeline
        • Long-Term Vision
      • 7. Conclusion
    • Massive
      • 1. Introduction
      • 2. Modular Design
      • 3. Key Functions of Massive
      • 4. Enhancing User Earnings Benefits for Users
      • 5. Powering Secure Ola Cross-Chain Interoperability
      • 6. How Massive Contributes to the Bitcoin Ecosystem
      • 7. Conclusion
  • How Users Earn Sustainable and Multiple Rewards in Ola Ecosystem
    • Ola: A Comprehensive Earning-Enhancing Layer
      • Massive: ZK Verification and Reward Network
      • Onis: Cross-Chain Interactions and Security
      • Multi-Stream Earning Opportunities for Users
    • Conclusion
  • Ola Community Hub
    • Ola Community Overview
    • Empowering the Community as Verifiers and Supervisors
    • Earnings and Rewards: Building a Sustainable Ecosystem
    • Vote and Propose on Ola
      • How to Vote
        • Who can vote
        • Procedure
        • Voting power
      • How to Propose
        • Who can make proposals
        • Procedure
        • How to edit or delete your proposal
        • Proposal status
      • Decision-making Approach
      • Check results
      • The Importance of Proposals and Voting
    • Community Loyalty Program
      • OVP Program
      • Ambassador Program
      • Builder Program
        • FAQs
        • How to apply for the Community Builders Program?
        • What incentives are included in the Community Builders Program?
        • How will the rewards and incentives be distributed?
        • What types of projects get incentives?
        • Criteria
    • Online Communities
      • Ola X, Discord & TG
    • Local Communities
      • Global Twitter communities
      • Other Resources
Powered by GitBook
On this page
  1. Ola Network Core Components: Onis & Massive
  2. Massive

2. Modular Design

Blockchain networks can be broadly categorized into two types: monolithic and modular.

  • Monolithic blockchains centralize all tasks, including data availability, consensus, settlement, and transaction execution, within a single network. While this structure offers simplicity, it often leads to scalability issues, especially during periods of high transaction volumes. Ethereum, for example, has faced challenges with high fees and slower processing speeds due to its monolithic design.

  • Modular blockchains, on the other hand, separate these layers—execution, settlement, and data availability—allowing each to operate independently. This design results in a more efficient and scalable system, as different tasks can be processed in parallel.

Massive is a decentralized Zero-Knowledge Proof (ZKP) verification network that exemplifies the modular design approach. It is composed of several layers that optimize efficiency and scalability:

  • ZKRollup: Handles off-chain computation to reduce the load on the main blockchain.

  • Data Availability (DA): Manages off-chain transaction storage, ensuring scalability without overloading the main chain.

  • ZKVaaS (Zero-Knowledge Verification as a Service): Conducts off-chain verification of transactions and states, maintaining security while minimizing on-chain activity.

  • L1: Manages state updates and consensus, providing finality for verified transactions and maintaining the integrity of the network.

Previous1. IntroductionNext3. Key Functions of Massive

Last updated 6 months ago