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 vision
  2. Why resource locks?
  3. Credible Stack Deep Dive

SDK providers

PreviousAppsNextWallets / WaaS

Last updated 10 months ago

The SDK layer delivers credible account capabilities to app developers through familiar interfaces.

Our technical collaboration with focuses on promoting ERC-5792 and ERC-7715 for interacting with credible accounts. These new JSON RPC API extensions introduce the wallet_ RPC namespace, aiding applications in interacting with next-generation wallets.

Our technical collaboration with and centers around implementing custom signers and providers in viem, wagmi, and web3js to expose credible account functionality, specifically the use of resource locks.

Learn more about these EIPs: ,

EIP-5792
ERC-7715
WalletConnect
wevm.dev
ChainSafe