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. Onis
  3. 3. Ola Solution: A trust-minimized BTC Cross-Chain Network

3.2 Permissionless Slashable Bridge Paradigm for Bitcoin

Previous3.1 Core Technical ArchitectureNext3.3 Trust Nobody, Bridge Yourself

Last updated 6 months ago

Building upon the 2-way PEG mechanism outlined in the BitVM2 Whitepaper, we designed the Ola BTC cross-chain protocol. This protocol leverages optimistic computation, assuming users are honest unless proven otherwise by challengers through fraud proofs.Users and Operators jointly sign a Peg-In transaction, and pre-sign a series of subsequent transactions required by the protocol. After the user completes a transaction on the Receiver chain and burns the corresponding assets, Ola generates the relevant ZKP for the user. The user can then pay the Take-Out cost and attempt to unlock the BTC on Bitcoin by initiating a transaction and facing potential challenges. If the challenge period ends without successful challenges, the user will successfully unlock the BTC, along with the reimbursement of the Take-Out cost. However, if the challenger succeeds, the Take-Out cost will be forfeited.

  • The Ola Relayer Network synchronizes Bitcoin’s Block Header information in real time to the Receiver chain (such as Ethereum). The Receiver chain confirms the validity of the Bitcoin information by verifying the ZKP provided by Ola.

  • Alice initiates a Peg-In transaction, locking the cross-chain BTC with Ola in a Taproot address, while also pre-signing the KickOff and Take transactions for future unlock.

  • Alice mints wrapped Bitcoin on the Receiver chain, where the contract has the Bitcoin state synchronized by Ola. The Inclusion Proof of the Peg-In transaction verifies the legitimacy of the minting, and wrapped Bitcoin is issued.

  • After Alice completes her business on the Receiver chain and wants to return the BTC assets to Bitcoin, she must burn the wrapped Bitcoin.

  • The Ola service monitors Alice’s Burn transaction and generates a ZKP for the Burn TX.

  • Alice then initiates the KickOff transaction on Bitcoin and awaits potential challenges:

    • If she withstands the challenge, she redeems her locked BTC and the Take-Out cost.

    • If the challenge is successful, the Take-Out cost is forfeited.