OneBalance

• Name: OneBalance
• URL: https://onebalance.io/
• Category: Chain-abstraction and cross-chain execution infrastructure / API toolkit
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: OneBalance is chain-abstraction middleware for apps that want one-click flows and one visible balance. The real product is route selection, execution policy, and backend coordination wrapped around smart accounts and cross-chain settlement.
• What it does:
  • Predicts smart-account addresses and supports account models built around ERC-4337 and EIP-7702 flows
  • Aggregates assets and balances across supported chains so apps can present a unified spendable balance
  • Provides APIs for quotes, execution, status tracking, transaction history, supported chains, and aggregated assets
  • Supports cross-chain transfers, swaps, arbitrary contract calls, and Solana-related flows from the same toolkit surface
  • Integrates with external key-management and wallet infrastructure such as Privy, Turnkey, and Fireblocks, while also exposing fee/monetization controls for applications
• Key claims:
  • Official docs frame OneBalance as the “simplest and most reliable” way to bring users onchain with one-click UX and a single API integration
  • Docs target apps, wallets, fintech products, and AI agents that need reliable execution across chains
  • Resource Locks materials claim faster cross-chain execution by removing finality waits, with RL-enabled bridge paths in the 5-10 second range and up to 40% gas-cost reduction through optimized settlement patterns
  • The docs expose a substantial API surface for balances, quotes, contract calls, transaction history, and supported chains, plus a public test key for limited experimentation
  • Public GitHub examples show working code paths for swaps, transfers, calldata-based actions, EIP-7702 delegation, and Solana-specific flows
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were the docs portal and public example repositories; see ../whitepapers/onebalance-primary-sources-2026-04-22.md.
• Sources:
  • https://docs.onebalance.io/overview/what-is-onebalance
  • https://docs.onebalance.io/overview/how-onebalance-works
  • https://docs.onebalance.io/concepts/resource-locks
  • https://docs.onebalance.io/api-reference/chains/list
  • https://github.com/OneBalance-io/onebalance-examples

Internal linkages

• Keep the linkage budget short.
• Best comparison points: particle-network, across, and privy.

Control surface

• The leverage sits in quote selection, route policy, fallback handling, sponsor defaults, and which balances or chains get touched first.

• So read OneBalance as execution middleware, not as a neutral one balance abstraction.

• Last reviewed: 2026-05-26 UTC