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
  2. Get Started with OneBalance SCA
  3. Setup OneBalance Toolkit with Privy

Step 1: Setting up Privy

PreviousSetup OneBalance Toolkit with PrivyNextStep 2: Setting configurations

Last updated 4 months ago

To integrate Privy into your codebase, follow and these considerations:

  1. User EOA Creation: It’s recommended to create the user’s externally owned address (EOA) upon their first login.

  2. Confirmation Prompt: Decide if the user needs to explicitly confirm actions or if they should be automatically processed in the UI.

  3. Authentication Methods: Choose appropriate authentication methods (e.g., social login, browser wallet).

    Note: If the user authenticates with a browser wallet, this is the only point where the wallet will be used. All other EOAs for the Smart Contract Account (SCA) are created independently of the wallet.

Once Privy is set up, ensure you have the following:

  • Privy App ID

  • PrivyProvider configured on your client

  • User login workflow organized and tested on the client side

Privy’s Quickstart documentation