Independent simulation and pre-sign validation
Most users do not know where your interface ends and the router, liquidity source, or contract begins. They do know what was on screen when they hit confirm. When execution delivers something different, or the transaction fails after they have already paid gas, your product owns the experience, and it's not a good one.
The cost lands in predictable places: fewer completed transactions, less fee-bearing volume, wasted gas and retries, support tickets that turn into engineering tickets, and users who stop coming back.
Enso Quote Simulator moves the check to the last point where you can still act: before the user signs. Verify what the transaction will do, then verify that the user is signing that same transaction.
Verification without replacing your stack
Quoter is a source-agnostic simulation and validation API for transactions you have already built. It works on transactions from Enso, third-party aggregators, protocols, smart accounts, multisigs or your own contracts. Your router, wallet, policy engine and submission flow stay in place.
Current flow: build, review, sign, submit.
With Quoter: build, simulate, apply policy, review, validate, sign, submit.
How it works
POST /api/v1/simulate runs the unsigned transaction against forked current EVM state. It returns a simulation ID, the expected execution status, tracked output, gas consumed, and structured errors if the transaction is likely to revert.
What happens next is your decision. You can accept the transaction, compare the simulated output against the upstream quote, re-route, re-simulate, warn the user, or stop the flow when execution or delivered-value thresholds are not met.
Immediately before signing, POST /api/v1/validate confirms that the final unsigned transaction still matches the cached simulation on chainId, calldata, to, from and native value. Signing and broadcasting stay on your side. Quoter does not custody funds, alter the transaction or submit it onchain.
Simulation is point in time, so teams can set a quote-age limit and re-simulate when the cached result expires or when chain conditions move quickly. The current workflow supports individual and batch simulation, valid EVM calldata from supported sources, and smart-account delegate-call scenarios.
What it protects
Quoter catches likely reverts before you spend gas on them, and it lets you compare the amount advertised upstream against an independent simulation of what will actually settle. When the two diverge, you can stop, re-route or re-simulate instead of sending a transaction you already expect to fail or under-deliver.
Validation covers the payload itself. It confirms that the transaction reaching the signer is the one you evaluated, which reduces exposure to altered calldata, a changed destination or sender, injected native value, or the wrong chain.
Structured simulation errors and field-level mismatches also give your support and engineering teams something concrete to diagnose from. And because Quoter evaluates transactions that already exist, you can add the control around your current stack without committing to a routing migration first.
Execution risk is already measurable
Enso's toxic-liquidity research found production venues that behaved one way during route discovery and another way at execution. Across the cases studied, Enso recorded tens of thousands of reverted transactions and more than 129,000 swaps that settled below the quoted result. One clean subset, routed through a major wallet interface, accounted for roughly $5.88 million in volume.
A route can win on displayed price and still lose on delivered outcome. Simulation is not a guarantee against every market or contract risk, but it is a practical way to catch likely failures, output discrepancies and payload changes before capital is committed.
Where it fits
Wallets and fintechs simulate before the review screen, then validate immediately before the wallet prompt. Aggregators and trading products use it differently: they rank candidate routes on simulated status and expected output rather than advertised output. In institutional and multisig workflows, the simulation happens before a proposal is created and the final unsigned payload is validated before signatures are collected. Protocols and vaults preview deposits, zaps and custom contract interactions before users or operators approve them.
The business case comes from your transaction data rather than a generic benchmark. A controlled execution-quality assessment can compare displayed quotes against independent simulation, simulated results against final settlement, revert and validation-failure rates, failed gas and retries, support events, latency, completed volume and fee revenue.
The assessment can start in shadow mode, with no changes to routing or signing. That establishes your current quote-to-settlement gap and shows whether independent verification catches enough additional risk to justify a guarded production pilot.
Assess your execution quality
Bring a representative transaction flow or a recent transaction sample. Enso will help establish your quote-to-simulation gap, failure profile and latency baseline, then design a controlled pilot around the stack you already run.
Integrate Enso Quoter today: https://docs.enso.build/pages/quoter/overview