Completes as requested or reverts (formerly Outcome completion)
Completes as requested or reverts describes when a financial action is truly finished: the result is usable, for example the traded asset is available on the destination network, and a SODAX trade that cannot get there reverts and returns the original assets. "Outcome completion" is an earlier SODAX term for this idea.
What it refers to
Completes as requested or reverts describes the point at which a financial action is actually finished and usable, and what happens when it cannot be.
"Outcome completion" is an earlier SODAX term for this idea. Current SODAX wording is plainer: a trade completes as requested or reverts and returns the original assets, with no mid-route substitution of the destination asset. How the action is carried out is covered under Execution and Cross-network execution, and the path back under Recoverability.
Completion is not the same as transaction confirmation. It is not the same as partial progress. It is not the submission of the final step in a sequence. An action is complete when the requested state has been reached and is stable enough to act on.
Examples:
- The traded asset is available and usable on the destination network
- A borrow position is open with the expected parameters
- Value has moved and can be used without additional steps
For a cross-network trade (often searched as swap across chains), this means the destination asset is genuinely available to use, not just recorded somewhere along the way.
Why this concept exists
In single-system environments, confirmation often implied completion. Once a transaction was confirmed, it was reasonable to assume the requested result had occurred.
When activity spans many networks, that assumption no longer holds.
Today:
- A transaction can succeed locally while the overall request is still unmet
- Some steps may complete while others are pending
- Liquidity conditions may change before the requested state is reached
- Value may exist in a technically valid state that is not yet usable
Because execution can span time and networks, confirmation and completion are no longer identical. We need this concept to distinguish "something happened" from "the user has what they asked for, or has the original assets back."
What this changes for system design
If confirmation is not completion, systems must define explicitly what completion means.
System design must:
- Set clear criteria for when an action counts as complete
- Distinguish intermediate states from final, usable states
- Track whether coordinated steps together reach the requested result
- Revert and return the original assets when that result cannot be reached
- Report progress in a way that reflects real state transitions
Completion becomes a question of usability and final state, not of single confirmations.
Related terms
- Execution: how an action is carried out
- Recoverability: the path back when an action cannot complete
- Cross-network execution: actions that span networks
- What the user asked for: the requested end state
- State transitions: moving between defined states
- Asynchronous reality: why steps finish at different times