onebalance-primary-sources-2026-04-22

OneBalance primary-source snapshot

Fetched: 2026-04-22 UTC

1) Official docs: what OneBalance is

Source: https://docs.onebalance.io/overview/what-is-onebalance

Selected excerpts from the docs:

The OneBalance Toolkit is the simplest and most reliable way to bring your users onchain. We offer an all-in-one API platform that lets you build one-click crypto products.

The Toolkit is ideal for apps that need fast, highly reliable onchain execution: swaps, yield, transfers, and arbitrary calldata are all supported out of the box.

One-click UX - no bridges, chain selection, or gas management.

Additional signals from this page:

• Target users include apps, wallets, fintech products, and AI agents
• Docs emphasize smart accounts, aggregated balances, swaps/transfers/contract calls, and monetization/fees
• Partner integrations named in the docs include Privy, Turnkey, and Fireblocks

2) Resource Locks technical concept

Source: https://docs.onebalance.io/concepts/resource-locks

Selected excerpts from the docs:

Resource Locks are OneBalance’s innovative solution that transforms cross-chain transactions by delivering three critical improvements: speed, reliability, and cost efficiency.

Resource Locks enable cross-chain transactions to execute at the speed of the destination chain while providing cryptographic guarantees and reducing operational costs through optimized settlement patterns.

Execute cross-chain transactions in seconds instead of minutes by eliminating finality wait times and double-spend prevention delays.

Additional implementation notes captured from the page:

• RL Service verifies balances, co-signs operations, issues guarantees to solvers, and tracks positions
• Docs compare classical bridges, intent bridges, and RL-enabled bridges, with RL-enabled critical-path timing shown in the 5-10 second range
• OneBalance says Resource Locks primarily use account-based locks today

3) Integration and API surface

Sources:

• https://docs.onebalance.io/overview/how-onebalance-works
• https://docs.onebalance.io/api-reference/chains/list
• https://docs.onebalance.io/llms.txt

Selected excerpts and signals:

The application does not need to worry about any of these - they are optimized on the Toolkit side.

Applications enable Resource Locks via the Toolkit. Once enabled, all user transactions are co-signed (sequenced) by OneBalance, preventing double-spending during asynchronous multichain executions.

Additional signals from the docs index and API reference:

• Endpoints for smart-account prediction, aggregated assets/balances, quotes, quote execution, transaction status/history, and supported chains
• Docs include references to contract-call flows, EIP-7702, Solana, slippage controls, fees, and troubleshooting
• API reference advertises a public test key for limited usage and identifies https://be.onebalance.io/api as the production API base URL

4) Public example repository

Source: https://github.com/OneBalance-io/onebalance-examples

Selected excerpts from the public repository page:

Examples for integrating with the OneBalance API to enable cross-chain asset management.

Additional signals from the repo page:

• Swap examples
• Transfer examples
• Calldata examples including Hyperliquid bridge deposit and Euler vault flows
• EIP-7702 example
• Solana-specific swap example
• Helper modules for authentication, key management, balance checks, quote building, signing, and monitoring

Notes

• This pass did not locate a classic whitepaper or litepaper from official OneBalance sources.
• The docs portal appears to be the main source of truth; the public example repository provides additional evidence of shipped developer workflows.
• One docs page markets coverage across EVMs, Solana, and Bitcoin, while the same feature table also labels native Bitcoin integration as coming soon; this should be treated as a docs inconsistency rather than a confirmed shipped capability.