OneBalance
OneBalance
  • Welcome to OneBalance
  • OneBalance Toolkit
    • Introduction
    • Get Started with OneBalance SCA
      • Setup OneBalance Toolkit with Privy
        • Step 1: Setting up Privy
        • Step 2: Setting configurations
        • Step 3: Initializing and Depositing onto the OneBalance Smart Account
        • Step 4: Displaying Chain-Aggregated Balances
        • Step 5: Fetch a quote for transaction execution
        • Step 6: Signing transactions with Privy
        • Step 7: Executing transactions
        • Step 8: Getting execution status
      • Contract calls guide
        • Usage code samples
  • OneBalance vision
    • Our vision
      • Mission of OneBalance
      • Use Cases
      • Credible Accounts and Credible Stack
      • Fellowship of OneBalance
      • Glossary
    • Why resource locks?
      • Technical Details
        • Resource lock
        • Permissions
        • Credible accounts
        • Credible Commitment Machine (CCM)
        • FAQ
          • How does this relate to account abstraction and 4337?
          • Where does the OneBalance account live?
          • Are OneBalance accounts non-custodial?
      • Credible Stack Deep Dive
        • Apps
        • SDK providers
        • Wallets / WaaS
        • Solver Networks
        • Oracle Providers
        • Data Providers
  • Other
    • OneBalance Demo App
      • Roadmap
      • Privacy Policy
      • Terms and Conditions
    • OneBalance Brand Assets
Powered by GitBook
On this page
  • Classical Bridge: source chain finality + destination chain inclusion 🐌
  • Intent Bridge: solver eats source chain finality risk 🥷
  • Fast Intent Bridge: lock provider removes double spend and finality risk 🚀
  • Types of Resource Locks
  1. OneBalance vision

Why resource locks?

PreviousGlossaryNextTechnical Details

Last updated 21 days ago

Classical Bridge: source chain finality + destination chain inclusion 🐌

  • Critical Path: Source chain finality + Destination chain inclusion

Intent Bridge: solver eats source chain finality risk 🥷

  • Critical Path: Source chain inclusion + Routing + Destination chain inclusion

Fast Intent Bridge: lock provider removes double spend and finality risk 🚀

  • Critical Path: Lock verification + Routing + Destination chain inclusion

Types of Resource Locks

Resource locks fall into two main categories:

  1. Account-based locks – Locks are implemented at the account level thus allowing compatibility with existing user flows.

  2. Escrow-based locks – Instead of locking accounts, this approach implements an escrow smart contract where users deposit tokens.