INTENT

EXECUTION & MEV

EXPERIMENT 02 — INTENT EXECUTION × MEV

An intent doesn't prescribe an exact execution path. The protocol evaluates candidate execution routes and selects one according to a scoring policy — MEV risk is one input to that decision, not an afterthought.

SYSTEM VISUALIZATION

INTENT→SWAP→SOLVERS→QUOTES→SCORING→MEV CHECK→SELECTED→SETTLEMENT

User intent: “Swap 1,000 USDC for ETH”

INTERACTIVE CONTROLS

EXECUTION PREFERENCE

COST SENSITIVITY1.0×MEV SENSITIVITY1.0×LATENCY SENSITIVITY1.0×

CANDIDATE QUALITY / COST

ADirect AMM RouteQUALITYCOST

BAggregator RouteQUALITYCOST

CPrivate Relay RouteQUALITYCOST

LIVE STATE

A · Direct AMM RouteSELECTED

QUALITY1000

COST0

MEV RISK10MEDIUM

LATENCY0ms

SCORE990

B · Aggregator RouteNOT SELECTED

QUALITY900

COST150

MEV RISK1LOW

LATENCY20ms

SCORE729

C · Private Relay RouteNOT SELECTED

QUALITY850

COST220

MEV RISK0LOW

LATENCY60ms

SCORE570

TECHNICAL DETAILSSIMULATION

This models the Execution Kernel Protocol's design — it does not call a live solver network or the actual protocol implementation. Conceptual mapping: IntentRegistry captures the intent, ModuleRegistry lists candidate executors, ScorePolicy is the weighted function tuned above, and ExecutionEngine applies it to select a route — all computed here, deterministically, in your browser.