General questions about OneBalance
OneBalance is a chain abstraction toolkit that enables developers to create seamless blockchain experiences. It provides a set of APIs for managing smart accounts, tracking cross-chain balances, and executing multichain transactions, all through a unified interface.
The platform simplifies complex blockchain operations by abstracting away the technical details, allowing developers to focus on building great user experiences.
Learn more in our What is OneBalance overview.
OneBalance solves several key challenges in blockchain development:
By addressing these issues, OneBalance makes blockchain applications more accessible and user-friendly.
OneBalance supports a growing list of networks, including:
For the most up-to-date list of supported chains, you can check the supported networks page or use our Chains API.
An aggregated asset in OneBalance represents a collection of the same token across multiple blockchains. For example, USDC exists on Ethereum, Arbitrum, Base, and other networks. OneBalance treats these as a single aggregated asset with the identifier ds:usdc
.
This approach allows users to:
You can see the full list of aggregated assets via the Assets API or learn more in our Aggregated Assets guide.
OneBalance offers flexible pricing based on usage and features:
For detailed pricing information and to discuss your specific needs, contact our sales team. Learn more about how fees are calculated in our Fees & Monetization guide.
Account abstraction and 4337 are often associated with Smart Contract Accounts and refer to both the set of UX improvements offered by an SCA (account abstraction) and a specific standard for implementation of these UX improvements (EIP-4337).
The OneBalance account model provides the same UX improvements as SCAs and is backward compatible with using 4337 for the settlement of locks on the chain as user ops.
However, since OneBalance is a general framework for the creation of credible accounts, it is not limited to chains where account abstraction and 4337 are actively being used.
OneBalance is supportive of chains and proxy accounts which opt for using dos resistant user ops like 4337.
Learn more about our account implementations in Account Models.
The account lives in a secure machine that can make credible commitments about what messages it will and won’t sign. On-chain identity can vary depending on the CCM design and the chain itself, overall it is either EOA or SCA.
OneBalance accounts are not opinionated on the type of credible commitment enforcement mechanism used. Crucially, as the sophistication of these architectures evolves over time, the tradeoff space will change and so will user preferences. As such, OneBalance accounts will remain flexible to support different architectures.
For technical details, see our Account Models documentation.
Yes. The system is designed such that nobody can use the funds or, generally, change the state of the account without the user’s permission.
Learn more about account security and Resource Locks that enable this non-custodial model.
The fastest way to get started is to follow our step-by-step Onboarding Checklist, which takes you from zero to production-ready in under an hour.
For a quick overview, here’s the basic flow:
If you need assistance with OneBalance, we offer several support channels:
We’re committed to helping developers successfully implement OneBalance in their applications. You can also check our Glossary for definitions of technical terms.