Transaction Lifecycle
Understanding how transactions flow through the OneBalance API
The numbers shown below are indicative and strongly depend on the use case conditions.
Not sure about the term? Visit Glossary to see all the definitions.
Transaction Types and Properties
Swaps & Transfers
Swap and transfer any token on any supported chain.
Contract calls
Execute any smart contract calls on any chain, spending the aggregated balance while preserving msg.sender
Fast vs Standard Path
Fast Path for cross-chain execution removes source chain txs latency.
Standard Path is for cross-chain is a basic sequential execution
Read more on Fast path and Resource locks here.
Transaction Execution Sequence (Swap example)
Execution Flow Walkthrough
1. Initial Request Phase
- User submits an intent (e.g., swap ETH aggregated across chains for SOL on Solana)
- OneBackend handles the request, performing routing and other optimizations
- Note that spending can happen from multiple chains within the same intent without affecting the flow. Our service determines how many funds are available on each chain and whether they are eligible for Fast or Standard Path execution.
2. Providing the Quote
- The solver system provides a quote that specifies pricing, including gas and swap fees
- The user receives the quote and decides whether to proceed
- The user signs the operation with their session key and sends it back to OneBackend
3. Validation and Security Phase
- OneBackend forwards the signed operation to our RL Service
- The RL Service verifies the user’s request and provides security attestation
- Based on security status, the transaction follows one of these paths:
- Fast Path via same-chain execution
- Fast Path via cross-chain execution (immediate execution with security guarantees)
- Standard Path (execution after the escrow transaction is confirmed)
4. Execution Phase
OneBackend submits operations and security guarantees to the solver. The execution then follows one of three paths:
Same-chain Fast Path is the quickest execution method, completing in seconds.
- Solver executes the operation on the target chain
- OneBackend verifies execution and confirms success to the user
- OneBackend executes the operation on the source chain
Same-chain Fast Path is the quickest execution method, completing in seconds.
- Solver executes the operation on the target chain
- OneBackend verifies execution and confirms success to the user
- OneBackend executes the operation on the source chain
Cross-chain Fast Path provides immediate execution with security guarantees, bypassing source chain finality wait times.
- Solver executes the operation on the target chain
- OneBackend verifies execution and confirms success to the user
- OneBackend executes the operation on the source chain
Standard Path follows traditional sequential execution and is used when Fast Path conditions are not met. This path is usually at least 2x slower than the Fast Path due to waiting for source chain finality.
- OneBackend executes the operation on the source chain
- Solver verifies execution on the source chain
- Solver executes the operation on the target chain
- OneBackend verifies execution and confirms success to the user
Fast Path Execution Criteria
A multichain intent leverages the Fast Path if it’s routed on the same chain OR if all of the following conditions are met:
- User has enough finalized, non-pre-approved on-chain balance (aggregated across chains) that is not yet locked (spent but not yet settled)
- There is no source-chain swap in the execution flow
- RL Service does not exceed the total open (not yet settled) position according to the risk policy