What the user asked for (formerly Intended outcome)

What the user asked for is the end state a user wants when starting a financial action, such as a set amount of an asset on a given network, rather than the transactions needed to get there. "Intended outcome" is an earlier SODAX term for the same idea.

system conceptintentsexecutionstate transitionscross-network executionsystem constraints

What it refers to

What the user asked for is the end state a user wants to reach when starting a financial action, described in terms of the result rather than the steps.

"Intended outcome" is an earlier SODAX term for this idea. Current SODAX wording says what the user asked for, and describes how a request ends in plain words: a trade completes as requested or reverts and returns the original assets. How a request is carried out is covered under Execution and Cross-network execution, and the path back when it cannot complete under Recoverability.

It is not a transaction. It is not a quote. It is not the submission of a message to a network.

Examples:

  • Holding a set amount of a specific asset on a specific network
  • Opening a borrow position with defined parameters
  • Rebalancing a portfolio to a target allocation
  • Exchanging one asset for another and being able to use it

The request describes the end state, not the steps taken to get there. A structured request that states it, with limits such as a minimum amount received and an expiry, is called an intent.

Why this concept exists

In simpler financial systems, submitting a transaction usually meant the job was done. Sending money, placing an order or making a trade was often indistinguishable from reaching the result the user wanted.

That is no longer true when activity spans many networks.

Today:

  • Assets may arrive on a network without enough liquidity to act
  • Actions may need several coordinated steps
  • One step may succeed while another does not
  • Timing and network conditions may change what is achievable

As a result, a successful transaction does not show that the user has what they asked for. We need the concept because the gap between "action submitted" and "request fulfilled" has widened.

What this changes for system design

If what the user asked for is distinct from any single transaction, systems cannot measure success by technical confirmation alone.

System design must:

  • Define clearly what state counts as complete
  • Distinguish one step succeeding from the whole request being fulfilled
  • Track whether intermediate steps lead to the requested end state
  • Return the original assets when the request cannot be fulfilled
  • Make it visible whether the requested state has been reached

Instead of asking "did the transaction execute?", systems ask "does the user have what they asked for?"

This request-driven model is described as intent-based execution (often searched as intent based swap when applied to token trades): the system's role is to fulfil what the user asked for, not merely process separate instructions.

Related terms

Last updated: 11/11/2026