> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Settlement and orchestration

> Distinguish solver-funded fulfillment from same-chain execution using an intent's vaulted funds.

Routes supports different ways to supply the capital needed to fulfill an intent.

| Approach | Capital source | Execution |
| - | - | - |
| Solver-funded fulfillment | The solver supplies destination tokens | The solver fulfills the route, then claims the reward after proof |
| Same-chain flash fulfillment | The intent's funded vault | The Local prover withdraws the reward, fulfills the route, and distributes the remainder within one transaction |

## Solver-funded fulfillment

For a cross-chain transfer, the solver supplies tokens on the destination chain while the source-chain reward remains in its vault. The solver recovers that reward after the configured prover confirms fulfillment.

The route's availability depends on solver participation, liquidity, chain conditions, and the selected proof mechanism.

## Same-chain orchestration

The Local prover's `flashFulfill` function can use the reward from a funded same-chain intent to execute its route. Withdrawal, fulfillment, and payment of remaining reward funds happen atomically. If the transaction reverts, those changes roll back together.

This mechanism applies to same-chain intents. It does not establish an automatic fallback for every cross-chain route or guarantee execution when no participant submits a transaction.

## Next steps

See [Flash Intents](/routes/capabilities/flash-intents) for use cases and [Settlement execution](/routes/architecture/settlement-vs-orchestration) for contract behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.