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
  1. OneBalance Toolkit

Get Started with OneBalance SCA

PreviousIntroductionNextSetup OneBalance Toolkit with Privy

Last updated 11 days ago

Account Overview

This section is about using toolkit with custom OneBalance Smart Contract Account (SCA). We support other SCAs as well as EIP-7702 EOA - docs for these are coming soon, but you can always .

This is a Kernel 4337 account with a custom ECDSA root validator module under ERC-7579 modular account.

OneBalance SCA account includes three main roles:

  1. Admin Role: A single key with on-chain encoded rights to manage all other roles within the account.

  2. User Signing Role: Multiple keys for user signing (often called session keys). For an optimal user experience, it is recommended to create a session key for each user and store this externally owned address (EOA) within Privy.

  3. Co-signer Role: A unique key held by OneBalance that co-signs each transaction. This is essential to ensure transactions are executed at the destination chain's speed.

Read more about .

The core setup for a OneBalance smart account involves storing a user signing key within a secure environment which allows required authorization/signing experience, such as Turnkey or Privy.

Note: The account that holds the balance and performs transactions is the Smart Contract Account (SCA) address, not any of the roles listed above.

reach out directly
Resource Locks here