OneBalance
OneBalance
  • Chain Abstraction Toolkit
    • Introduction
    • Using OneBalance SCA
      • Getting started with OneBalance and 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
    • What is OneBalance
      • 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
  1. OneBalance vision
  2. Why resource locks?
  3. Technical Details
  4. FAQ

Are OneBalance accounts non-custodial?

Yes. The system is designed such that nobody can use the funds or, generally, change the state of the account without the user's permission.

PreviousWhere does the OneBalance account live?NextCredible Stack Deep Dive

Last updated 1 day ago